Docs / SDK

Orchestrate your MCP: Armature SDK.

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

Package @armature-tech/mcp-analytics Runtime Node MCP servers Outcome Sessions, workflows, fixes

01What it does

The SDK connects your MCP server to Armature without taking over your product.

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

Roughly

Think of it as product analytics for agent sessions: lighter than tracing every internal function, richer than counting HTTP requests.

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

02One-prompt setup

For agent-assisted setup, install the Armature integration playbook once, then give Claude Code, Cursor, or Codex one prompt.

npx skills add armature-tech/mcp-analytics --global
Install Armature analytics on this MCP server.

If you are wiring it manually, install the package directly. Armature will provide the workspace configuration values separately.

npm install @armature-tech/mcp-analytics

The exact setup depends on the MCP framework. Armature can also stage a reviewed PR with the SDK connected.

03What you get

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

Visibility
A clearer picture of whether agents can use the interface successfully.
Patterns
Repeated workflow breaks, rough edges, and surfaces that need attention.
Repairs
Reviewed suggestions for docs, workflows, schemas, or code changes.
Previous Synthetic tests 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