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

# Nimt MCP

> Bring Nimt project context into your AI assistant.

Nimt helps you understand how your brand appears in AI search. The Nimt MCP
server gives an AI assistant access to a focused set of tools in your workspace,
so you can look up project context without copying it between apps.

[Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/getting-started/intro)
is the standard that lets an assistant discover and call those tools.

<Warning>
  Nimt MCP is still in development. These pages describe the current pre-release
  implementation, not a publicly available service. Only follow the connection
  steps once Nimt has confirmed access for you. Client compatibility and
  available tools may change before launch.
</Warning>

## Start with your project context

The initial customer MCP contains two read-only tools:

| Tool                      | What it does                                                                                                    |
| ------------------------- | --------------------------------------------------------------------------------------------------------------- |
| `workspace_list_projects` | Lists or searches projects in the connected workspace and returns their IDs.                                    |
| `project_get_metadata`    | Looks up a project's brand, tracked and observed models, available data range, tags, intents, and prompt count. |

For example, ask your assistant:

> List the projects in my connected Nimt workspace.

Then choose a project and ask:

> Show this project's tracked models, tags, and available data range.

These tools return project context. The current catalog does not provide
visibility reports, citation analysis, prompt results, or tools that edit your
projects. A project's available data range describes its data coverage; it does
not include the underlying results.

## One connection, one workspace

Connect using OAuth or a personal access token. Both act as your Nimt user and
stay within one workspace. Changing the workspace in the Nimt app does not move
an existing MCP connection.

Only connect clients you trust: tool results are shared with the AI client you
authorize and are subject to that client's data handling settings.

<CardGroup cols={2}>
  <Card title="Connect your client" icon="plug" href="/mcp/setup">
    Set up Claude Code, Cursor, Codex, or another remote MCP client.
  </Card>

  <Card title="Understand access" icon="shield-halved" href="/mcp/authentication/overview">
    Choose authentication and understand workspace permissions.
  </Card>
</CardGroup>