Connecting from other tools (Cursor, VS Code…)

The duelgo connector works in any tool that can handle remote MCP servers (Streamable HTTP transport) with OAuth sign-in. You only ever need one piece of information: the address https://www.duelgo.fun/mcp. Client registration and sign-in happen automatically — the tool sends you to your browser to sign in to duelgo.

Cursor

Settings → MCP → Add new MCP server, or add this to the ~/.cursor/mcp.json file: {"mcpServers": {"duelgo": {"url": "https://www.duelgo.fun/mcp"}}}. After saving, click the sign-in next to the server.

VS Code (GitHub Copilot)

Open the command palette (Cmd/Ctrl+Shift+P) → MCP: Add Server → type HTTP → paste the connector address. VS Code takes care of the sign-in.

Gemini CLI and others

Add a server with the connector's httpUrl address to the configuration (for Gemini CLI that's ~/.gemini/settings.json). It works much the same in Windsurf and other tools with MCP support.

The exact shape of the configuration differs from tool to tool — search their documentation for “MCP server” or “custom connector”. Once the tool knows the address, the rest (registration, sign-in, consent) is always the same.

Not working?

Check that the address is exactly https://www.duelgo.fun/mcp (including the www, with no trailing slash).

The tool must support remote MCP servers with OAuth — purely local MCP clients without sign-in support won't work.

If the AI is “acting under someone else's account”, you're signed in to the tool with a shared account — the connector is tied to the AI tool's account. Disconnect it and connect again under your own.