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

# Other clients

> Connect Cursor, Claude Code, Codex, or another remote MCP client.

For the normal chat apps, use [ChatGPT](/mcp/clients/chatgpt) or
[Claude](/mcp/clients/claude). This page covers developer tools and custom clients.
Use it only with confirmed pre-release access from Nimt.

All clients use `https://api.nimt.ai/mcp` over **Streamable HTTP**. OAuth is the
recommended authentication method. Client setup support is not a guarantee that
every client version has been tested; update your client and check its own docs.

## Cursor

Add the following entry to `~/.cursor/mcp.json`. Merge it into the existing
`mcpServers` object if you already have other servers.

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

Open Cursor's MCP settings, enable Nimt, and follow OAuth sign-in. Select the
workspace you intend to use. See [Cursor's MCP documentation](https://cursor.com/docs/mcp).

## Claude Code

Add Nimt to your personal Claude Code configuration:

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

Run `/mcp` inside Claude Code, select Nimt, and authenticate. Complete the Nimt
sign-in and workspace approval in your browser. See
[Claude Code's MCP documentation](https://code.claude.com/docs/en/mcp).

## Codex

Add the server and sign in from the Codex CLI:

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

Complete Nimt's sign-in and workspace approval. Use `/mcp` in the Codex terminal
UI to inspect the connection. See
[Codex's MCP documentation](https://developers.openai.com/codex/mcp).

### Use a token with Codex

If OAuth is unavailable, [create a PAT](/mcp/authentication/personal-access-tokens)
and make `NIMT_PAT` available to the process launching Codex through your secret
manager or a secure shell prompt. Then add a separate token-based entry:

```bash theme={null}
codex mcp add nimt-pat --url https://api.nimt.ai/mcp --bearer-token-env-var NIMT_PAT
```

This stores the environment variable's name, not the token. Do not run OAuth
login for this entry. Disable an unused duplicate Nimt connection to avoid
ambiguous tools. A desktop app may not inherit terminal environment variables;
the credential must be available to the actual client process.

## Other remote MCP clients

Add a custom server with the Nimt URL and Streamable HTTP transport. Start the
client's OAuth flow and approve a workspace in Nimt.

If it cannot complete OAuth but accepts custom HTTP headers, follow the
[personal access token guide](/mcp/authentication/personal-access-tokens).
Clients that only support local stdio servers cannot connect to this URL directly.
Nimt does not require a proxy for clients with native remote MCP support.

Do not confuse an AI provider's API key or a Nimt organization API key with a
Nimt personal access token. Never store credentials in shared configuration files.

## Verify your connection

> Use Nimt to list the projects in my connected workspace.

Then ask for the metadata of one returned project. See
[available tools](/mcp/tools), [usage limits](/mcp/usage-limits), and
[troubleshooting](/mcp/troubleshooting) for the current contract.