Skip to main content
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. On workspaces with Evaluation, the same connection also lets the agent run your eval suites and read the verdicts.

​
Endpoint

Connect to the region your workspace lives in. The snippets below use the US endpoint — EU workspaces swap in the EU URL.

​
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:
With OAuth, omit the header — Claude Code runs the authorization flow on first use:
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.

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