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

> ## Agent Instructions
> Use a clmt_test_ key while developing. It never touches live data. Send a UUID Idempotency-Key on every POST, PUT and DELETE, generated once per operation and reused on retries. Pin Clemta-Version: 2026-08-13 on every request. Branch on the error code field, never on detail. Retry only timeouts, 5xx and 429, and honor Retry-After. Test companies never advance on their own. Drive them with POST /sandbox/companies/{id}/simulate. OpenAPI: https://api.clemta.com/v1/openapi.json. Skills: npx skills add https://docs.clemta.com. Docs search MCP: https://docs.clemta.com/mcp. Guide: https://docs.clemta.com/partner/ai-agents.md.

# Partner MCP server

> Ask about your companies, orders, billing and webhooks from Claude, Cursor, or any MCP client.

The partner MCP server lets an agent read your partner account. Your team asks
in plain words, and the agent answers from the same objects the
[Partner API](/partner/introduction) serves:

* Which companies are still waiting on a document?
* What stage is the EIN order for Acme LLC at?
* What would a Delaware LLC with an EIN and a registered agent cost us?
* Why did our endpoint never get `company.incorporated` yesterday?
* What does the March statement come to, and which companies are behind it?

The server only reads. It cannot form a company, place an order, or submit a
filing. See [What it cannot do](#what-it-cannot-do).

This is not the [docs search server](/ai/coding-agents#docs-search-mcp), which
searches these pages and calls nothing.

## Connect

The server is at:

```text theme={null}
https://mcp.clemta.partners
```

Add it to your client. There is no key to paste: the first time the client
connects, it opens the [partner dashboard](/partner/dashboard) in your
browser, and you approve the connection there.

<div className="client-tabs">
  <Tabs>
    <Tab title="Claude" icon="https://mintcdn.com/clemta/oJAi34Rm7sWWUksj/images/clients/claude.svg?fit=max&auto=format&n=oJAi34Rm7sWWUksj&q=85&s=30ea8cbf347b47df889b3a5bfacd6ed5" width="24" height="24" data-path="images/clients/claude.svg">
      For Claude.ai, Claude Desktop and the Claude mobile apps, add a custom
      connector with this address:

      ```text theme={null}
      https://mcp.clemta.partners
      ```

      1. Open **Settings > Connectors** and choose **Add custom connector**.
      2. Name it `Clemta Partner` and paste the address.
      3. Choose **Connect**.

      On a Team or Enterprise plan, an owner adds the connector under
      **Organization settings > Connectors** first. Each member then connects
      it with their own partner dashboard login.
    </Tab>

    <Tab title="Claude Code" icon="https://mintcdn.com/clemta/oJAi34Rm7sWWUksj/images/clients/claude.svg?fit=max&auto=format&n=oJAi34Rm7sWWUksj&q=85&s=30ea8cbf347b47df889b3a5bfacd6ed5" width="24" height="24" data-path="images/clients/claude.svg">
      ```bash theme={null}
      claude mcp add --transport http clemta-partner https://mcp.clemta.partners
      ```

      Then run `/mcp` inside Claude Code and choose **Authenticate**.
    </Tab>

    <Tab title="ChatGPT" icon="comments">
      Create a connector in developer mode with this address:

      ```text theme={null}
      https://mcp.clemta.partners
      ```

      1. Open **Settings > Apps & Connectors > Advanced settings** and turn on
         **Developer mode**.
      2. Back in **Apps & Connectors**, choose **Create**.
      3. Paste the address, set authentication to **OAuth**, and create it.
    </Tab>

    <Tab title="Codex" icon="terminal">
      ```bash theme={null}
      codex mcp add clemta-partner --url https://mcp.clemta.partners
      codex mcp login clemta-partner
      ```
    </Tab>

    <Tab title="Cursor" icon="https://mintcdn.com/clemta/oJAi34Rm7sWWUksj/images/clients/cursor.svg?fit=max&auto=format&n=oJAi34Rm7sWWUksj&q=85&s=77c15ea58cbf2e7fe17c41f6240f61af" width="24" height="24" data-path="images/clients/cursor.svg">
      In `.cursor/mcp.json`, or `~/.cursor/mcp.json` for every project:

      ```json theme={null}
      {
        "mcpServers": {
          "clemta-partner": { "url": "https://mcp.clemta.partners" }
        }
      }
      ```
    </Tab>

    <Tab title="VS Code" icon="https://mintcdn.com/clemta/oJAi34Rm7sWWUksj/images/clients/githubcopilot.svg?fit=max&auto=format&n=oJAi34Rm7sWWUksj&q=85&s=33f0f48c4ff07befd1e4e181859275c6" width="24" height="24" data-path="images/clients/githubcopilot.svg">
      For GitHub Copilot in VS Code, in `.vscode/mcp.json`:

      ```json theme={null}
      {
        "servers": {
          "clemta-partner": { "type": "http", "url": "https://mcp.clemta.partners" }
        }
      }
      ```

      Or from a terminal:

      ```bash theme={null}
      code --add-mcp '{"name":"clemta-partner","type":"http","url":"https://mcp.clemta.partners"}'
      ```
    </Tab>

    <Tab title="Windsurf" icon="https://mintcdn.com/clemta/oJAi34Rm7sWWUksj/images/clients/windsurf.svg?fit=max&auto=format&n=oJAi34Rm7sWWUksj&q=85&s=9595d8fb6cfc6e76f550cc36f8d4e37e" width="24" height="24" data-path="images/clients/windsurf.svg">
      In `~/.codeium/windsurf/mcp_config.json`:

      ```json theme={null}
      {
        "mcpServers": {
          "clemta-partner": { "serverUrl": "https://mcp.clemta.partners" }
        }
      }
      ```
    </Tab>

    <Tab title="Gemini CLI" icon="https://mintcdn.com/clemta/oJAi34Rm7sWWUksj/images/clients/googlegemini.svg?fit=max&auto=format&n=oJAi34Rm7sWWUksj&q=85&s=0099994106ae985e5e2a664299a457d0" width="24" height="24" data-path="images/clients/googlegemini.svg">
      ```bash theme={null}
      gemini mcp add --transport http clemta-partner https://mcp.clemta.partners
      ```

      Then run `/mcp auth clemta-partner` inside Gemini CLI.
    </Tab>

    <Tab title="Zed" icon="https://mintcdn.com/clemta/oJAi34Rm7sWWUksj/images/clients/zedindustries.svg?fit=max&auto=format&n=oJAi34Rm7sWWUksj&q=85&s=3abdac5aa4399833ed66d9957bc9ebdb" width="24" height="24" data-path="images/clients/zedindustries.svg">
      In Zed's `settings.json`:

      ```json theme={null}
      {
        "context_servers": {
          "clemta-partner": { "url": "https://mcp.clemta.partners" }
        }
      }
      ```
    </Tab>

    <Tab title="Cline" icon="https://mintcdn.com/clemta/oJAi34Rm7sWWUksj/images/clients/cline.svg?fit=max&auto=format&n=oJAi34Rm7sWWUksj&q=85&s=adf92ef478cc1c008b0c881331e3cc0f" width="24" height="24" data-path="images/clients/cline.svg">
      In `cline_mcp_settings.json`, opened from **MCP Servers > Configure**:

      ```json theme={null}
      {
        "mcpServers": {
          "clemta-partner": { "type": "streamableHttp", "url": "https://mcp.clemta.partners" }
        }
      }
      ```
    </Tab>

    <Tab title="Other" icon="plug">
      Any client that speaks Streamable HTTP and OAuth connects with the address
      alone. For a client that only runs local servers, bridge it with
      `mcp-remote`:

      ```json theme={null}
      {
        "mcpServers": {
          "clemta-partner": {
            "command": "npx",
            "args": ["-y", "mcp-remote", "https://mcp.clemta.partners"]
          }
        }
      }
      ```
    </Tab>
  </Tabs>
</div>

<Steps>
  <Step title="Add the server">
    Use the instructions for your client above.
  </Step>

  <Step title="Sign in and approve">
    Your client opens the partner dashboard. Sign in if you are not already,
    check which agent is asking, and approve. A connection is either test or
    live, never both.
  </Step>

  <Step title="Ask">
    Start with "which mode am I in?". The agent tells you whether it is
    reading the sandbox or real data.
  </Step>
</Steps>

## What a connection is

Approving creates an **MCP connection** in the partner dashboard: which
agent, approved when, in which mode, last used when.

* **Read-only.** The agent can look things up. It cannot change anything.
* **Sees what your account sees.** A connection covers all your companies.
  Use a test connection while you try things out.
* **Logged.** Every lookup shows in the dashboard's
  [Logs](/partner/dashboard#logs), next to your integration's requests.

There is no API key to copy or keep safe. Clemta creates one for the
connection, and it does not appear in your API key list.

## Revoke a connection

Delete the connection in the partner dashboard. The agent loses access on its
next question and tells you the connection is no longer valid.

Removing the server from your MCP client does not delete the connection.
Delete it in the dashboard too if you are done with it.

## What it cannot do

The agent cannot:

* create or update an account or a company
* place, cancel or pay for a service order
* submit or sign a tax filing, or fulfill a requirement
* create, re-enable or delete a webhook endpoint
* move a test company with the sandbox

Do these with the API or in the partner dashboard.

## Next

<CardGroup cols={2}>
  <Card title="Tools" icon="wrench" href="/ai/partner-mcp-tools">
    What the agent can look up, and what to ask.
  </Card>

  <Card title="Build with an AI agent" icon="code" href="/partner/ai-agents">
    Skills and docs search for the coding agent that writes your integration.
  </Card>
</CardGroup>


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