> ## Documentation Index
> Fetch the complete documentation index at: https://docs.montra.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect your agent

> Add the Montra MCP connector to Claude, Claude Code, ChatGPT, Codex, Cursor, or any other MCP client.

The connector is a remote MCP server at:

```text theme={null}
https://montra.com/api/mcp
```

It uses the Streamable HTTP transport and OAuth 2.1 sign-in. No API key is involved — every client below opens a browser window where you sign in with your Montra account and pick a workspace. See [Authentication](/authentication) for how that works.

Montra is also listed in two directories, which is the quickest way in for most people:

* [Montra in the Claude directory](https://claude.ai/directory/montra)
* [Montra in the ChatGPT plugin directory](https://chatgpt.com/plugins/plugin_asdk_app_6a7f37e662988191af8714ea2c247a3e)

## Claude

Open [Montra in the Claude directory](https://claude.ai/directory/montra), click **Connect**, sign in with your Montra account, and choose the workspace this connection should act in. The connector lives on your claude.ai account, so one connect covers:

* Claude on the web, desktop, and mobile,
* Claude Code, whenever it is signed in with the same claude.ai account (`/mcp` lists it as **claude.ai Montra**).

### Claude Code on an API key, Amazon Bedrock, or another account

Those never receive claude.ai's connectors, so give Claude Code its own sign-in:

```bash theme={null}
claude mcp add --scope user --transport http montra https://montra.com/api/mcp
claude mcp login montra
```

Follow the browser sign-in. After the consent screen the tools are available as `mcp__montra__*`.

## ChatGPT and Codex

Install [Montra from the ChatGPT plugin directory](https://chatgpt.com/plugins/plugin_asdk_app_6a7f37e662988191af8714ea2c247a3e) and connect it when asked, signing in with your Montra account and choosing a workspace. The plugin is an account-level grant on your ChatGPT account, so one install covers:

* ChatGPT on the web, desktop, and mobile,
* Codex inside the ChatGPT desktop app,
* the Codex CLI, whenever it is signed in with the same ChatGPT account (`/apps` lists it as `$montra`).

### Codex CLI on an API key, another account, or in the IDE extension

Plugins need a ChatGPT sign-in, and the IDE extension does not support plugins at all. For those cases add the server directly:

```bash theme={null}
codex mcp add montra --url https://montra.com/api/mcp
codex mcp login montra
```

Follow the browser sign-in and choose the workspace this connection should act in. This writes to `~/.codex/config.toml`, which the ChatGPT desktop app, CLI, and IDE extension share. Run `/mcp` in Codex to verify the connection.

<Note>
  Pick one path per machine. The plugin and a `codex mcp add` entry both expose Montra's tools, so a Codex session with both configured sees them twice. If you installed the plugin, you can remove the direct entry with `codex mcp remove montra`; the plugin itself is managed from ChatGPT's plugin settings, not from the CLI.
</Note>

## Cursor

Add the server to `~/.cursor/mcp.json` (or the project's `.cursor/mcp.json`):

```json theme={null}
{
  "mcpServers": {
    "montra": {
      "url": "https://montra.com/api/mcp"
    }
  }
}
```

Cursor prompts you to authenticate the first time it connects.

## Other MCP clients

Any client that supports remote MCP servers with the Streamable HTTP transport and OAuth 2.1 authorization can connect. Point it at `https://montra.com/api/mcp`; the server advertises its authorization server through the standard protected-resource metadata at:

```text theme={null}
https://montra.com/.well-known/oauth-protected-resource
```

Clients that implement the MCP authorization spec (PKCE + dynamic client registration) will discover everything else from there.

## Verify the connection

Ask your agent to call [`get_workspace`](/tools/get-workspace). It returns the name and id of the workspace the connection is bound to — a quick confirmation that sign-in and workspace binding both worked.

<Note>
  Requests without a valid token get a `401` with a `WWW-Authenticate` challenge pointing at the metadata URL above. That is the protocol working as intended — it is how clients discover where to send you for sign-in, not an outage.
</Note>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.