Quickstart

Three steps: create an ingest key, wire in the SDK, deploy.

Create your ingest key

Click Add MCP server and register your server.
On the server’s card, click Connect SDK analytics to mint an ingest key. The key is shown once, together with your region’s ingest URL — copy both.
Add them to your server’s deployment secrets:

ANALYTICS_INGEST_API_KEY=<your ingest key>
ANALYTICS_INGEST_URL=<your region's ingest URL>

US workspaces can omit ANALYTICS_INGEST_URL (the SDK defaults to the US endpoint); EU workspaces must set it. Each MCP server gets its own key. You can rotate or revoke keys from the same card at any time.

Wire in the SDK

The fastest path: paste this prompt into your coding agent and let it do the wiring.

Prompt for your coding agent

Add Armature session analytics to my MCP server.
Follow the docs at https://docs.armature.tech/sdks/typescript
(Python: /sdks/python, Go: /sdks/go, PHP: /sdks/php). The ingest
key and URL are already set as ANALYTICS_INGEST_API_KEY and
ANALYTICS_INGEST_URL in the deployment environment.

Or do it by hand — it’s one wrapper around your server:

import { createMcpAnalyticsServer } from "@armature-tech/mcp-analytics";

const server = createMcpAnalyticsServer(() => {
  const mcp = new McpServer({ name: "customer-mcp", version: "1.0.0" });
  // ...register your tools exactly as before
  return mcp;
});

from fastmcp import FastMCP
from armature_mcp_analytics import instrument_fastmcp

mcp = FastMCP("Customer MCP")
instrument_fastmcp(mcp)

# ...register your tools exactly as before

s, shutdown := armatureanalytics.NewMCPServer("Customer MCP", "1.0.0")
defer shutdown(context.Background())

armatureanalytics.InstrumentTool(s, tool, handler)

$builder = Server::builder()->setServerInfo('Customer MCP', '1.0.0');

$analytics = Analytics::instrument(
    builder: $builder,
    config: Config::fromEnvironment(),
);

// ...add your tools exactly as before
$server = $builder->build();

Install commands and full options are on the per-language pages: TypeScript, Python, Go, PHP.

Deploying to serverless? Set delivery to await and add the one-line session helper — see Stateless & serverless servers.

Deploy and watch sessions flow in

Deploy your server. As soon as an agent talks to it, sessions appear in the dashboard — the Overview fills with live sessions, use cases, and issues.To sanity-check locally first, point a client at your dev server (for example claude mcp add with the local command) and run one conversation. You should see it under Sessions within a minute or two.

Next steps

Replay your first session

Read the ask, the agent’s thinking, and every call.

Understand what's captured

Telemetry fields, events, size limits, and delivery.

Identify your users

Attribute sessions to real accounts, privacy-preserved.

Connect the Armature MCP

Query your analytics from your coding agent.

⌘I

Getting started

Analytics

Evaluation

SDKs

Armature MCP

Privacy & security

Next steps

Replay your first session

Understand what's captured

Identify your users

Connect the Armature MCP

​Next steps

Replay your first session

Understand what's captured

Identify your users

Connect the Armature MCP

Next steps