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

# Connect your agent

> Query your Armature analytics from Claude Code, Cursor, or any MCP client

Armature is itself an MCP server. Connect it to your coding agent and ask things like *"what are my top issues this week?"*, *"show me a failed session for bulk refunds"*, or *"which use cases have the worst pass rate?"* — the agent reads your live analytics through read-only tools.

## Endpoint

```
https://mcp.armature.tech/mcp
```

## Authentication

Two options:

* **OAuth (recommended)** — connect without copying a key: your client is challenged on first contact and walks you through authorization in the browser. Active grants are listed and revocable on the **Connect Armature MCP** page in the dashboard.
* **API key** — mint a workspace key at **Settings → API keys** and send it as a bearer token. Keys are shown once at creation.

## Set up your client

The dashboard's **Connect Armature MCP** page generates ready-to-paste, pre-authenticated snippets for your client. The shapes:

<Tabs>
  <Tab title="Claude Code">
    ```bash theme={null}
    claude mcp add --transport http armature https://mcp.armature.tech/mcp \
      --header "Authorization: Bearer <YOUR_API_KEY>"
    ```

    With OAuth, omit the header — Claude Code runs the authorization flow on first use:

    ```bash theme={null}
    claude mcp add --transport http armature https://mcp.armature.tech/mcp
    ```
  </Tab>

  <Tab title="Cursor">
    Add to `.cursor/mcp.json` (or use the one-click install link from the dashboard):

    ```json theme={null}
    {
      "mcpServers": {
        "armature": {
          "url": "https://mcp.armature.tech/mcp",
          "headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
        }
      }
    }
    ```
  </Tab>

  <Tab title="VS Code">
    ```bash theme={null}
    code --add-mcp '{"name":"armature","type":"http","url":"https://mcp.armature.tech/mcp","headers":{"Authorization":"Bearer <YOUR_API_KEY>"}}'
    ```
  </Tab>

  <Tab title="Codex">
    ```bash theme={null}
    codex mcp add armature \
      --url https://mcp.armature.tech/mcp \
      --header "Authorization: Bearer <YOUR_API_KEY>"
    ```
  </Tab>

  <Tab title="Claude / ChatGPT apps">
    * **Claude**: Settings → Connectors → **Add custom connector**, with the endpoint URL. OAuth is handled in the flow.
    * **ChatGPT**: Settings → Connectors → Advanced → add the endpoint as a connector.
  </Tab>
</Tabs>

<Warning>
  Treat API keys like passwords. The server rejects secret-shaped values in tool arguments, but the bearer token itself belongs in your client's MCP configuration — never in a prompt.
</Warning>

## Try it

Once connected, ask your agent:

> Rank this workspace's issues by blast radius, open the worst one, and show me a session that hits it.

That prompt ships with the server as `triage_issues` — it exercises the whole read surface. The full tool list is on the [next page](/armature-mcp/tools).