Overview
One connector for every MCP client. Add OmniDimension as a custom server in Claude Desktop, Claude Code, Cursor, VS Code, or Windsurf. Browser sign-in on the first call.
The hosted MCP server lives at:
https://mcp.omnidim.io/mcpPaste that anywhere a client asks for a custom MCP server. The first time you connect, the client opens a sign-in in your browser. Approve, and you're done.
Pick your client
Claude Code
One terminal command.
Claude Desktop
Settings, then Connectors. Same flow on Claude.ai.
Cursor
Edit one JSON file.
VS Code
User settings, HTTP transport.
Windsurf
Codeium MCP config.
Any other MCP client
Zed, Cline, Continue, Codex, and anything else that speaks the protocol.
How the OAuth flow works
The hosted server implements the standard MCP authorization spec (OAuth 2.1 + PKCE + Dynamic Client Registration). Clients discover the rest from https://mcp.omnidim.io/.well-known/oauth-authorization-server. You never paste or copy a client secret.
On the first tool call:
- Your client redirects you to
omnidim.io/oauth/consentin your browser. - You sign in (or sign up) to your OmniDimension account.
- You see the consent screen with the client name. You approve.
- The browser hands a one-time code back to the client.
- The client exchanges the code for an access token and stores it locally.
- From here, every tool call sends the token as a Bearer header.
Tokens are scoped to your OmniDimension account. The server stores upstream credentials encrypted at rest.
Other clients
Most MCP clients added in 2025 or later support HTTP transport with OAuth. The shape is consistent across them:
| Client | Config key | Field |
|---|---|---|
| Claude Code | (CLI flag) | --transport http |
| Claude Desktop, Claude.ai | (Settings UI) | custom connector URL |
| Cursor | mcpServers.<name>.url | URL string |
| VS Code | mcp.servers.<name> | type: "http", url |
| Windsurf | mcpServers.<name>.serverUrl | URL string |
| Zed | context_servers.<name>.url | URL string |
| Cline | mcpServers.<name>.url | URL string |
| Continue | mcpServers.<name> | type: streamable-http, url |
If your client only supports stdio transport, use the local server with an API key instead.
Revoking access
You can disconnect at any time:
- From inside the client (most clients surface a Disconnect or Remove server option).
- From your OmniDimension account at omnidim.io/api-management by removing the corresponding API credential.
Either path revokes the access token immediately. Subsequent tool calls return 401.
Troubleshooting
Overview
Connect Claude, ChatGPT, Cursor, and any MCP-compatible client to your OmniDimension account. Hosted OAuth at mcp.omnidim.io, or local stdio via the npm package.
Claude Code
Connect OmniDimension to Claude Code in one terminal command. OAuth sign-in via the browser, then use OmniDimension tools from any Claude Code session.