# Overview (/docs/mcp/connect)

> 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/mcp
```

Paste 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 [#pick-your-client]

  " title="Claude Code" href="/docs/mcp/connect/claude-code" description="One terminal command." />

  " title="Claude Desktop" href="/docs/mcp/connect/claude-desktop" description="Settings, then Connectors. Same flow on Claude.ai." />

  " title="Cursor" href="/docs/mcp/connect/cursor" description="Edit one JSON file." />

  " title="VS Code" href="/docs/mcp/connect/vscode" description="User settings, HTTP transport." />

  " title="Windsurf" href="/docs/mcp/connect/windsurf" description="Codeium MCP config." />

  " title="Any other MCP client" href="#other-clients" description="Zed, Cline, Continue, Codex, and anything else that speaks the protocol." />

## How the OAuth flow works [#how-the-oauth-flow-works]

The hosted server implements the standard MCP authorization spec ([OAuth 2.1](https://oauth.net/2.1/) + PKCE + [Dynamic Client Registration](https://datatracker.ietf.org/doc/html/rfc7591)). 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:

1. Your client redirects you to `omnidim.io/oauth/consent` in your browser.
2. You sign in (or sign up) to your OmniDimension account.
3. You see the consent screen with the client name. You approve.
4. The browser hands a one-time code back to the client.
5. The client exchanges the code for an access token and stores it locally.
6. 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 [#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](/docs/mcp/local-server) with an API key instead.

## Revoking access [#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](https://omnidim.io/api-management) by removing the corresponding API credential.

Either path revokes the access token immediately. Subsequent tool calls return `401`.

## Troubleshooting [#troubleshooting]

  
    Double-check the URL ends with `/mcp`. The bare host returns 404. The exact URL is `https://mcp.omnidim.io/mcp`.
  

  
    Make sure your client supports OAuth 2.1 with PKCE and Dynamic Client Registration. Most clients added in 2025 or later do. If yours does not, use the [local stdio server](/docs/mcp/local-server) with an API key instead.
  

  
    Your token may have been revoked. Open [omnidim.io/api-management](https://omnidim.io/api-management) to confirm the credential is present, or remove and re-add the server in your client to start a fresh OAuth flow.
  

  
    The tool catalogue is generated from the public [OpenAPI spec](/openapi.yaml). If an endpoint is in the API reference but not in the MCP tool list, open an issue at [omnidim-mcp-cloud](https://github.com/Omnidim/omnidim-mcp-cloud/issues).