Skip to Content
We are live but in Staging πŸŽ‰
MCP serverOther clients

Other clients

Dodil’s MCP server follows the standard, so any MCP-capable assistant can use it. The only decision is the same one as everywhere else: remote or local.

  • Runs in the cloud (a website or a hosted assistant) β†’ use the remote server, https://mcp.dodil.io.
  • Runs on your machine (an editor or terminal agent) β†’ the local server is usually nicer, because it reuses your CLI login and can use code mode.

Cloud assistants β€” paste the URL

These connect over HTTPS and log you in through a redirect back to their own website. All of their callback addresses are trusted by Dodil’s identity service, so nothing extra is needed from you:

  • Perplexity
  • Google Gemini / Antigravity
  • Microsoft Copilot Studio

In each, find the connectors / integrations / tools screen, choose to add a custom MCP server, and give it:

FieldValue
NameDodil
Server URLhttps://mcp.dodil.io
AuthOAuth (the app will handle it β€” you just log in at id.dodil.io)

Editors β€” Cursor and VS Code / GitHub Copilot

Both support MCP and both work with Dodil either way.

Recommended β€” local. Install the dodil CLI and log in with dodil auth login. The installer writes the standard {"mcpServers": …} configuration that these editors read, so in most cases the Dodil tools simply appear after a restart. To add it yourself, the entry is:

{ "mcpServers": { "dodil": { "command": "dodil", "args": ["mcp"] } } }

Alternative β€” remote. If you’d rather not install anything, point the editor’s MCP configuration at https://mcp.dodil.io over HTTP transport instead. The editor opens a browser for you to log in at id.dodil.io.

Desktop and terminal agents

Agents that log in through a loopback callback β€” a short-lived listener on your own computer at http://localhost/callback or http://127.0.0.1/callback, the standard pattern for desktop apps β€” are trusted by Dodil’s identity service. That includes:

  • Cline
  • Continue
  • Zed
  • Goose
  • Tencent CodeBuddy

For all of these, both routes work. The local server is still the better default on a machine where you already use the dodil CLI.

Anything else

If your assistant lets you add β€œa custom MCP server over HTTP with OAuth”, it will work. Give it https://mcp.dodil.io and let it handle the login. If it only supports API keys or static tokens for MCP, it is not compatible with the remote server β€” use the local server instead.

Stuck? β†’ Troubleshooting.