trackmcp
MCP analytics quickstart

Send your first MCP analytics event

Go from an existing server to a verified event in four small steps. Keep your tools unchanged and see the result in the dashboard.

Create a workspaceOpen full docs
01

Create a key

02

Install the SDK

03

Wrap the server

04

Verify one call

01 · Create a key

Start with a workspace.

Sign in to TrackMCP, create a workspace key, and keep it in the environment of the process that runs your server.

Never commit the key or put it in a tool argument.

.env
TRACKMCP_KEY=tmcp_...
02–03 · Install and wrap

One line at the boundary.

Install the SDK and wrap the existing server object. Your tool definitions and client-facing responses stay the same.

TypeScriptPython SDK
server.ts
// observe the server you already ship
$ npm install @trackmcp/sdk
 
import { withTrackMCP } from "@trackmcp/sdk"
import { server } from "./mcp"
 
export default withTrackMCP(server, {
  apiKey: process.env.TRACKMCP_KEY,
  service: "acme-mcp-server",
});
04 · Verify

Make one real tool call.

Restart the server, connect from an MCP client, and call one tool. The dashboard should show the client, session, call, timing, and result state.

Success looks like a live event

Errors returned inside a successful HTTP response remain visible as application errors.

First event received

acme-mcp-server · just now

clientClaude
methodtools/call
toolsearch_docs
resultcompleted
Before you debug

Check the simple things first.

No event

Confirm the process has the right key and make a real tool call after restarting the server.

Wrong workspace

Check that the key belongs to the workspace you are viewing.

Sensitive data

Redact arguments and results locally. Send only the metadata your team needs.

Ready to observe your server?

Start with one real workflow.

Create a workspace, wrap the server, and make the first call.

Get startedSee analytics