Orchestrate your MCP: Armature SDK.

The SDK wraps your MCP server for Armature analytics. Your product owns the tools; Armature gets signal to improve the agent-facing interface.

01What it does

The SDK wraps your MCP server without taking over your business logic.

You own the tools and deployment. Armature gets analytics to help improve the agent-facing interface.

Back-end logs show which calls happened. Armature shows the end-user intent, the agent intent, and how agents work through the interface: which paths succeed, where they get stuck, and what should improve.

02One-prompt setup

For agent-assisted setup, give your coding agent one prompt.

Install the Armature skill using `npx skills add armature-tech/mcp-analytics --global`, then use it to install Armature analytics on this MCP server.

If you are wiring it manually, install the package directly and pass the Armature analytics secret in your server environment.

npm install @armature-tech/mcp-analytics
ARMATURE_ANALYTICS_SECRET=amt_...

03What you get

The SDK lets Armature turn product behavior into interface improvements without publishing implementation details in your docs.

Visibility
What your users use your MCP for (the key use cases), full session recordings, and whether each one succeeds or fails.
Patterns
Repeated workflow breaks, rough edges, and surfaces that need attention.
Repairs
Reviewed suggestions for skill files, docs, workflows, schemas, or code changes.

04Security

Product secrets stay in your environment. Armature uses scoped workspace configuration, and access can be rotated without changing your tool implementation.

Previous Docs overview Next Interface builds

Want help wiring the SDK?

Send us the MCP framework and deployment target. We will point you at the smallest setup path.

Back to docs