Documentation

Get started with ContextPulse

ContextPulse is the observability and analytics layer purpose-built for Model Context Protocol servers. Add it at the server boundary, keep your tools unchanged, and turn protocol traffic into usage, reliability, and outcome signals.

TypeScript SDK

Node.js, Bun, Deno, and Stdio / SSE protocol implementations.

Python SDK

FastMCP, async servers, and Python MCP protocol drivers.

2-Minute Quickstart

Install the SDK, configure your workspace key, wrap your server, and deploy.

1Install the package

Add the ContextPulse SDK to your existing server repository dependencies:

# For Node.js / TypeScript:

npm install @contextpulse/sdk

# For Python:

pip install contextpulse

2Wrap your MCP server instance

Pass your server instance into withContextPulse. Your underlying tools remain 100% unchanged:

import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { withContextPulse } from "@contextpulse/sdk";

const server = new McpServer({
  name: "acme-mcp-server",
  version: "1.0.0"
});

// Wrap server at export boundary
export default withContextPulse(server, {
  apiKey: process.env.CONTEXTPULSE_KEY,
  service: "acme-mcp-server",
  environment: "production"
});

Fail-open: If telemetry is unreachable, agent execution continues uninterrupted.Async batching

3Verify telemetry in your dashboard

Connect any MCP client (Claude Desktop, Cursor, etc.) and run a tool call. Live connection metrics will immediately populate on your ContextPulse dashboard.