install-mcp-analytics

Integrate Armature MCP Analytics into TypeScript MCP servers.

Updated Jul 15, 2026
One-click install
npx skills add https://github.com/armature-tech/mcp-analytics --skill install-mcp-analytics
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: install-mcp-analytics
Source: https://github.com/armature-tech/mcp-analytics/tree/main
Command: npx skills add https://github.com/armature-tech/mcp-analytics --skill install-mcp-analytics

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill integrates Armature MCP Analytics into an existing MCP server so teams can understand tool usage, user intent, latency, failures, retries, and session activity without building a custom observability pipeline.

Core Features & Use Cases

  • Integration Detection: Identifies whether the server uses a standard MCP server, registry-style tools, a custom dispatcher, Mastra, fastmcp, Vercel mcp-handler, or MCP SDK v2.
  • Telemetry Instrumentation: Adds the appropriate SDK wrapper or recorder, advertises telemetry fields when supported, strips telemetry before business handlers run, and records tool-call outcomes and previews.
  • Production Configuration: Configures regional ingest credentials, delivery behavior, privacy controls, actor identification, redaction, session handling, and capability requests.
  • Verification: Checks tool schemas, runs the local doctor where applicable, and confirms that a real tool call produces an authenticated analytics batch.
  • Use Case: Add Armature analytics to a TypeScript MCP server, preserve its existing tool definitions, configure US or EU ingestion, and verify that tool calls are visible in the Armature dashboard.

Quick Start

Use the install-mcp-analytics skill to detect the MCP server integration shape, instrument the server, configure analytics delivery, and verify a telemetry-producing tool call.

Frequently Asked Questions about install-mcp-analytics

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I add analytics to an MCP server?

Instrumenting MCP servers with telemetry involves selecting a compatible SDK adapter to wrap tool dispatchers, capturing usage, latency, and failures without building a custom observability pipeline. The integration detects your server shape and records authenticated analytics batches for dashboard visibility.

Can I use MCP telemetry with Mastra or fastmcp?

Yes, telemetry instrumentation works with Mastra, fastmcp, Vercel mcp-handler, and MCP SDK v2. The integration detects whether the server uses standard McpServer factories, registry-style tools, or custom dispatchers, then applies the appropriate adapter to capture tool usage and latency.

How do I configure regional ingest credentials for server telemetry?

Configuring regional ingest credentials involves selecting US or EU ingestion endpoints, setting delivery mode, and applying privacy controls like redaction. You must configure actor identification and session handling to ensure tool-call outcomes produce authenticated analytics batches.

How do I verify MCP analytics instrumentation is working?

You verify MCP analytics instrumentation by checking tool schemas, running the local doctor command, and confirming a real tool call produces an authenticated analytics batch. This ensures telemetry fields are properly decorated, stripped before business handlers run, and visible in the dashboard.

Does MCP observability preserve existing privacy controls?

Yes, MCP observability preserves privacy controls by configuring redaction, actor identification, and session handling. The instrumentation advertises telemetry fields when supported, strips them before business handlers run, and records tool-call outcomes and previews according to configured privacy settings.