# Overview (/docs/mcp)

> 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.

The [Model Context Protocol](https://modelcontextprotocol.io) lets AI clients call tools on your behalf. OmniDimension ships two MCP entry points to the same set of tools (agents, calls, bulk calls, phone numbers, knowledge base, providers):

  " title="Hosted (cloud, OAuth)" href="/docs/mcp/connect" description="https://mcp.omnidim.io/mcp. Add as a custom MCP server in Claude Desktop, Claude.ai, Cursor, VS Code. OAuth 2.1 sign-in, no API key handling on your side." />

  " title="Local (npm, stdio)" href="/docs/mcp/local-server" description="@omnidim-ai/mcp-server runs as a stdio child process from your editor. Bearer API key in the env block. Use for CI, automation, or stdio-only clients." />

## Which one should I use? [#which-one-should-i-use]

| You're using...                      | Use this                                                            |
| ------------------------------------ | ------------------------------------------------------------------- |
| Claude Desktop, Claude.ai web        | [Hosted](/docs/mcp/connect)                                         |
| Claude Code                          | [Hosted](/docs/mcp/connect/claude-code) (one command)               |
| Cursor, VS Code, Windsurf            | [Hosted](/docs/mcp/connect). These clients speak HTTP MCP natively. |
| ChatGPT custom connectors            | [Hosted](/docs/mcp/connect)                                         |
| CI, scripts, headless automation     | [Local](/docs/mcp/local-server)                                     |
| An MCP client that only speaks stdio | [Local](/docs/mcp/local-server)                                     |

If you are not sure, start with the hosted option. It is the path we recommend for everyone shipping interactive AI experiences.

## What you can do over MCP [#what-you-can-do-over-mcp]

Every endpoint in the [API reference](/docs/api-reference) is exposed as an MCP tool, generated from the same OpenAPI spec. The main categories:

* **Agents.** List, create, update, delete, get.
* **Calls.** Dispatch outbound calls, fetch call logs and transcripts.
* **Bulk calls.** Create campaigns, monitor live status, cancel.
* **Phone numbers.** List, attach to agents, import from Twilio, Exotel, SIP.
* **Knowledge base.** Upload files, attach to agents.
* **Providers.** List available LLMs, voices, STT, and TTS engines.

## How sign-in works [#how-sign-in-works]

The hosted entry point uses a standard browser sign-in. Click connect in your MCP client, approve OmniDimension in the browser, and you're done. Tokens are scoped to your account and can be revoked any time from [omnidim.io/api-management](https://omnidim.io/api-management).

The local entry point uses an API key from your account. Drop it in the env block of your client config and the server uses it for every call.

See [privacy and telemetry](/docs/mcp/privacy) for what each server sees, what we log, and what we never store.

## Open source [#open-source]

Both servers are public on GitHub:

* [`omnidim-mcp-cloud`](https://github.com/Omnidim/omnidim-mcp-cloud) (Apache 2.0). Hosted OAuth + HTTP server (FastAPI, Python).
* [`omnidim-mcp-server`](https://github.com/Omnidim/omnidim-mcp-server) (MIT). Local stdio server, npm-distributed (TypeScript).

Issues and PRs welcome on both.