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

# Connect to Nimt

> Configure a remote MCP client and check your first connection.

<Warning>
  These instructions are for pre-release access confirmed by Nimt. The endpoint
  and account settings may not be available to you yet. If access has not been
  confirmed, contact [support@nimt.ai](mailto:support@nimt.ai) before
  proceeding.
</Warning>

## Connection details

| Setting        | Value                                     |
| -------------- | ----------------------------------------- |
| Server URL     | `https://api.nimt.ai/mcp`                 |
| Transport      | Streamable HTTP                           |
| Authentication | OAuth or a personal access token          |
| Access         | Your user, within one connected workspace |

You need a Nimt account with workspace membership and a client that supports
remote MCP over Streamable HTTP. Your client's subscription or administrator
settings may also control whether you can add custom servers.

## Choose your client

These examples follow the clients' documented configuration formats. They are
setup guidance, not a claim of completed end-to-end compatibility testing with
the pre-release Nimt service. Update your client before connecting.

<Tabs>
  <Tab title="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
    ```

    Open Claude Code, run `/mcp`, select Nimt, and follow the authentication
    prompt. Sign in to Nimt, choose a workspace, and review the requested access.

    See [Claude Code's MCP documentation](https://code.claude.com/docs/en/mcp)
    for configuration and authentication details.
  </Tab>

  <Tab title="Cursor">
    Add this entry to `~/.cursor/mcp.json`. If the file already contains servers,
    merge the `nimt` entry into its existing `mcpServers` object.

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

    Open Cursor's MCP settings, enable Nimt, and follow the OAuth sign-in prompt.
    Choose the workspace you want the connection to use.

    See [Cursor's MCP documentation](https://cursor.com/docs/mcp) for
    configuration locations and authentication options.
  </Tab>

  <Tab title="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 the Nimt sign-in and workspace approval in your browser. Use `/mcp`
    in the Codex terminal UI to inspect the connection.

    See [Codex's MCP documentation](https://developers.openai.com/codex/mcp)
    for configuration details. For a token-based setup, use the
    [PAT instructions](/mcp/authentication/personal-access-tokens#use-a-token-with-codex)
    instead of OAuth login.
  </Tab>

  <Tab title="Other clients">
    Add a custom remote MCP server with the URL above and choose Streamable HTTP
    if your client asks for a transport. Start its OAuth sign-in flow and approve
    a workspace in Nimt.

    If your client cannot use OAuth but supports custom HTTP headers, configure
    a [personal access token](/mcp/authentication/personal-access-tokens).
    Clients that only support local stdio servers cannot use this URL directly.

    Use your client's custom-server settings and follow its documentation for
    availability and setup.
  </Tab>
</Tabs>

## Check the connection

Ask your assistant:

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

The assistant should call `workspace_list_projects`. An empty result can be
valid if the connected workspace has no projects or a search matches none.

Choose a returned project and ask for its metadata. The assistant should use
that project's ID with `project_get_metadata`. If you need the full project
list, ask the assistant to fetch the remaining pages.

If sign-in succeeds but tools or projects are missing, follow the
[troubleshooting guide](/mcp/troubleshooting).