Troubleshooting
Work down this page in order — the first three cover almost everything.
”Unauthorized” / “authentication required”
What it means: your temporary access pass (token) has expired, or was never issued.
- Dodil access tokens are short-lived — roughly 15 minutes — and normally refresh silently in the background. If your assistant was idle for a long time, or your laptop slept, the refresh can be missed.
- Fix: disconnect the Dodil connector and connect it again. You’ll get a fresh browser login at
id.dodil.io. - On the local server: run
dodil auth loginin your terminal, thendodil auth statusto confirm. Your agent cannot complete the browser login for you — a human has to do it.
The connector won’t add
Nine times out of ten it’s the address. It must be exactly:
https://mcp.dodil.ioCheck for:
- A trailing slash —
https://mcp.dodil.io/— remove it. - An added
/mcp— several clients showhttps://mcp.example.com/mcpas the example and people copy the shape. You don’t need the suffix. http://instead ofhttps://— it must be HTTPS.- A stray space pasted before or after the address.
mcp.dodil.iowith no scheme — some clients reject it.
Also check the client’s own requirements: Claude and ChatGPT both need a paid plan for custom connectors.
Connected, but “no tools available”
The connection worked; the permissions didn’t.
- Your Dodil user may not have the roles needed. The MCP server can never give you more access than your account already has — see Roles and Policies. Ask an admin in your organisation to grant you the roles for the products you need.
- You may be in the wrong organisation. If you belong to more than one, log in as the account that owns the resources you’re looking for.
- The assistant may not have enabled the connector for that chat. Some clients require you to switch a connector on per conversation — check the tools/connectors control in the chat window.
ChatGPT: there’s no Connectors section at all
Custom MCP apps are not available on the ChatGPT Free plan. You need an eligible plan or workspace, and Developer Mode enabled. Pro supports read/fetch MCP access; Business, Enterprise and Edu support the full custom-MCP beta subject to workspace permissions. See Connect ChatGPT.
Claude: “Connectors have moved to Customize”
The menu moved. Use Customize → Connectors, not Settings → Connectors. See Connect Claude.
Claude: I picked the wrong OAuth option
Claude does not allow a connector’s authentication settings to be edited after it’s added. Remove the Dodil connector from Customize → Connectors and add it again, choosing “Use your own OAuth client” and entering client ID dodil-mcp with the secret left blank. See Step 4.
”We are sorry… invalid request” on the Dodil login page
You picked “Use Anthropic’s hosted client metadata” (CIMD) or “No client ID — register one automatically” (DCR). Neither works with Dodil today — not because of your account, but because of a known bug in Keycloak, our login service (keycloak#50362 ). Claude marks the first one Detected, which makes it look correct.
Remove the connector and add it again with “Use your own OAuth client” and client ID dodil-mcp. Nothing else changes.
The login window opens and nothing happens
- Check your browser isn’t blocking the pop-up.
- Check you can reach
https://id.dodil.ioin a normal browser tab. A corporate firewall or VPN that blocks it will stall the login. - For desktop and terminal agents, the login comes back to a loopback address on your own machine (
http://localhost/callback/http://127.0.0.1/callback). A local firewall or security tool that blocks loopback listeners will break this.
The assistant does the wrong thing, or invents a result
- Ask it to show the tool it used and the raw JSON it got back. Every Dodil tool returns JSON.
- Be specific with names: “list Ignite apps in my org” beats “what have I deployed”.
- If it claims something changed, verify with the CLI (
dodil ignite app list) before you trust it.
Check the server itself is up
Anyone can run this — no login needed:
curl -s https://mcp.dodil.io/.well-known/oauth-protected-resourceA healthy server returns:
{
"authorization_servers": ["https://id.dodil.io/realms/dodil"],
"resource": "https://mcp.dodil.io"
}If that returns nothing or an error, the problem is on our side rather than in your settings.
Still stuck
Contact Dodil support with:
- Which assistant and which plan you’re on.
- The exact URL you pasted.
- Which authentication option you chose.
- The exact error text (a screenshot of the error is ideal). Never send us a token, a password, or a client secret.