# Sim MCP (/mcp/overview)





Connect an AI app to Sim to manage workspaces, run and deploy workflows, and work with tables, files, knowledge bases, and logs. Sim MCP exposes JSON API operations through the [Model Context Protocol](https://modelcontextprotocol.io), a standard for connecting AI apps to tools. See [Tools](/mcp/tools) for supported requests and limits.

## Choose the server URL [#choose-the-server-url]

| Deployment | Server URL |
| - | - |
| Sim Cloud | `https://mcp.sim.ai/mcp` |
| Self-hosted | `https://<your-sim-host>/api/mcp`, or your [`SIM_MCP_URL`](/platform/self-hosting/environment-variables) |

The server uses Streamable HTTP. Sign in with OAuth or send an [API key](/mcp/authentication#api-keys). Replace the Cloud URL in every example below when connecting to a self-hosted deployment.

Claude's hosted connectors call from Anthropic's infrastructure, so your server must be reachable from it over the internet. A `localhost` URL works with clients that connect from your machine, such as Claude Code, Codex, Cursor, and VS Code. See [Claude's network requirements](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp).

## Connect an app [#connect-an-app]

<Tabs items="['Claude Code', 'Claude', 'Codex', 'Cursor', 'VS Code']">
  <Tab value="Claude Code">
    ```bash
    claude mcp add --transport http sim https://mcp.sim.ai/mcp
    ```

    Open `/mcp` in Claude Code, select **sim**, and sign in to Sim in the
    browser.
  </Tab>

  <Tab value="Claude">
    Add `https://mcp.sim.ai/mcp` as a custom connector under **Customize →
    Connectors**, then connect it and sign in to Sim. For Team or Enterprise,
    an authorized organization administrator first adds it under **Organization settings → Connectors**. If asked for an OAuth client strategy, choose **Register automatically**. See
    [Claude's custom connector instructions](https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp).
  </Tab>

  <Tab value="Codex">
    ```bash
    codex mcp add sim --url https://mcp.sim.ai/mcp
    ```

    Complete the browser sign-in. To sign in again later, run
    `codex mcp login sim`.
  </Tab>

  <Tab value="Cursor">
    Add `sim` to `mcpServers` in `~/.cursor/mcp.json`, then enable it in
    Cursor and sign in to Sim:

    ```json
    {
      "mcpServers": {
        "sim": { "url": "https://mcp.sim.ai/mcp" }
      }
    }
    ```
  </Tab>

  <Tab value="VS Code">
    Add `sim` to `.vscode/mcp.json`, then start it and sign in to Sim:

    ```json
    {
      "servers": {
        "sim": { "type": "http", "url": "https://mcp.sim.ai/mcp" }
      }
    }
    ```
  </Tab>
</Tabs>

For another app that supports remote MCP servers with OAuth, enter the server URL and choose **Streamable HTTP** if asked. Follow that app's connection and sign-in procedure.

## Try it [#try-it]

Ask your app:

* "List my Sim workspaces and the tables in each."
* "Run the `lead-scoring` workflow with this input and show me the result."
* "Find failed runs from the last day and explain what went wrong."
* "Create a table of our open support tickets and add these rows."

The agent finds the right operation, reads its inputs, and calls it. See
[Tools](/mcp/tools) for how that works.

## Access and approvals [#access-and-approvals]

Access follows the connection credential, workspace role, and operation policy. Each call uses the API's authorization, rate limits, validation, and logging. Personal credentials use your current access; workspace API keys are limited to their workspace. See [Authentication](/mcp/authentication) to choose credential scope or read-only OAuth access.

The server separates read and write tools; your app controls whether it asks for confirmation before a change.

## Other Sim MCP surfaces [#other-sim-mcp-surfaces]

These features have separate purposes:

* [Search MCP](/search/mcp) searches your organization's live provider sources with current access checks.
* [MCP deployment](/workflows/deployment/mcp) exposes your own workflows as
  tools, and [MCP tools](/agents/mcp) connect external servers to Sim agents.

## Related docs [#related-docs]

* [Authentication](/mcp/authentication) for scopes, credentials, and revocation
* [Tools](/mcp/tools) for operation discovery, calls, and result limits
* [API getting started](/api-reference/getting-started) and [CLI](/cli) for other ways to operate Sim