Your client is not on the list? No problem. demi speaks standard MCP. Any client that handles MCP over HTTP with OAuth can connect.
The details
- Server URL
https://mcp.godemi.com/mcp- Transport
- Streamable HTTP
- Sign-in
- OAuth 2.1 with PKCE (S256)
- Client registration
- Dynamic: the client registers itself, you need no client ID.
- Scope
demi:mcp:public
In one sentence: add https://mcp.godemi.com/mcp as a custom connector and sign in.
What your client needs
- MCP over HTTP (Streamable HTTP). Clients that only start local servers over stdio need a bridge.
- OAuth 2.1 with PKCE. The client opens the sign-in in the browser and keeps the token itself.
- Discovery through well-known addresses. The server names its sign-in service in the
WWW-Authenticateheader and at these addresses:
URL
https://mcp.godemi.com/.well-known/oauth-protected-resourcehttps://mcp.godemi.com/.well-known/oauth-authorization-server- Reachability. The server is publicly reachable. If your client runs behind a proxy,
mcp.godemi.commust be allowed over HTTPS.
Example of a JSON config
Many clients read their servers from a JSON file. Key names differ per client, the content stays the same:
JSON
{ "mcpServers": { "demi": { "type": "http", "url": "https://mcp.godemi.com/mcp" } }}No token, no key: sign-in happens in the browser.
Check the connection
Without sign-in the server must answer 401. That tells you it is reachable:
Terminal
curl -i -X POST https://mcp.godemi.com/mcpWhen something sticks
- The client asks for a client ID: it does not support dynamic registration. Write to us and we help.
- The sign-in does not open: check whether your client supports remote servers with OAuth or only local ones.
- No tools after sign-in, or the connection drops: disconnect and connect again. If that does not help, write to us.
- Wrong tenant: disconnect, connect again and pick the right tenant when you sign in.
Step-by-step guides exist for Claude, Claude Code, ChatGPT and GitHub Copilot.
