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

# Introduction

> Product analytics for agent sessions

Your users reach your product through Claude, ChatGPT, and coding agents — and those sessions live inside their AI client, not your UI. Armature captures every session on your MCP server, Claude Connector, or ChatGPT App, and shows you what users ask, what agents think, and how they use your product.

Add the SDK, deploy, and sessions start flowing in minutes:

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Create an ingest key, wire in the SDK, and watch your first sessions arrive.
  </Card>

  <Card title="How Armature works" icon="lightbulb" href="/how-it-works">
    How scattered tool calls become replayable, scored sessions with user intent.
  </Card>
</CardGroup>

## What you get

<CardGroup cols={2}>
  <Card title="Sessions & replay" icon="play" href="/dashboard/sessions">
    Every conversation your MCP sees, scored on whether the user got what they asked for. Replay the full trace: the ask, the agent's thinking, and every call.
  </Card>

  <Card title="Use cases" icon="shapes" href="/dashboard/use-cases">
    Models read every session and identify what the user came to do — grouped, ranked by volume and success rate, including the use cases you don't support yet.
  </Card>

  <Card title="Issues" icon="triangle-alert" href="/dashboard/issues">
    Failures, loops, and dead ends grouped by root cause and ranked by how many users hit them — even when every API response was 200 OK.
  </Card>

  <Card title="Overview" icon="layout-dashboard" href="/dashboard/overview">
    Sessions, pass rate, and issues at a glance, with trends against the previous period.
  </Card>
</CardGroup>

## Evaluate changes before you ship

Armature also runs evals against your MCP server. You write eval cases, a real agent plays the user, and a judge scores every run against your criteria. If you use the analytics above, Armature drafts the cases for you from real use cases and issues.

<Card title="Evaluation" icon="flask-conical" href="/evaluation/overview" horizontal>
  Run real agent sessions against your server, by hand, on a schedule, or from CI.
</Card>

## Works with your stack

The SDK wraps your server and changes nothing about how it behaves. If an AI client can reach your server, Armature can capture the session — Claude, ChatGPT, Cursor, Codex, Gemini CLI, and the rest.

<CardGroup cols={2}>
  <Card title="TypeScript" icon="square-code" href="/sdks/typescript">
    Official MCP SDK (1.x and 2.x), Mastra, fastmcp, and mcp-handler
  </Card>

  <Card title="Python" icon="square-code" href="/sdks/python">
    FastMCP and the official MCP SDK
  </Card>

  <Card title="Go" icon="square-code" href="/sdks/go">
    mark3labs/mcp-go and the official go-sdk
  </Card>

  <Card title="PHP" icon="square-code" href="/sdks/php">
    The official PHP MCP SDK (mcp/sdk)
  </Card>
</CardGroup>

## Bring the answers to your agent

Armature is also an MCP server. Connect it to Claude Code, Cursor, or any MCP client and ask questions like *"what are my top issues this week?"* — the agent reads your live analytics.

<Card title="Connect the Armature MCP" icon="plug" href="/armature-mcp/connect" horizontal>
  One command adds your analytics to your coding agent.
</Card>


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