Pulse MCP
Pulse MCP connects external AI assistants — such as Cursor and Claude Desktop — to your Pulse observability data. Ask questions about crashes, interactions, sessions, alerts, and more from your IDE without switching to the dashboard.
How It Works
Pulse MCP is a Model Context Protocol server that wraps Pulse HTTP APIs as tools your assistant can call:
- You configure an MCP client (Cursor, Claude Desktop, etc.) with a personal access token.
- The client launches the Pulse MCP server locally over stdio.
- The assistant calls Pulse tools to fetch live data from your projects.
All MCP tools are read-only — they query Pulse data but do not change dashboard configuration, alerts, or SDK settings.
What You Can Query
Once connected, your assistant can access data across these areas:
| Area | Examples |
|---|---|
| App Vitals | Crash, ANR, and non-fatal issue lists; issue trends; stack traces |
| Interactions | Critical interaction list, Apdex, error rate, response time, root-cause analysis |
| Sessions | Session replay listing with cursor pagination |
| Events | Event catalog, categories, search |
| Funnels & Journeys | Funnel and journey definitions and metadata |
| Alerts | Alert rules, evaluation history, notification channels |
| Heatmaps | Touch heatmap data for a screen |
| SDK config | Active SDK configuration and feature gates |
On connect, only five core tools are available: list_projects, get_project, list_project_members, register_tools, and reset_tools. Domain tools are unlocked per session when the assistant calls register_tools.
Tool categories
Pass these values to register_tools before using domain-specific tools:
| Category | Unlocks |
|---|---|
crashes | App Vitals — crash, ANR, and non-fatal lists; issue detail, trends, stack traces |
sessions | Session replay listing |
interactions | Critical interactions, RCA, Apdex, error rate, response time |
events | Event catalog, categories, search |
funnels | Funnel list, detail, tags, builder events |
journeys | User journey flows |
alerts | Alert rules, evaluation history, notification channels |
heatmap | Touch heatmap data for a screen |
sdk | SDK configuration and feature rules |
You can register multiple categories in one call, for example categories: ["crashes", "interactions"]. Use reset_tools to drop unlocked categories and start fresh.
Requirements
- A Pulse account with access to the projects you want to query
- Node.js 18+ on the machine running the MCP client
- A personal MCP access token (
pulse_mcp_*) — not the project SDK API key from Settings → SDK Configuration
The Pulse MCP server is available on npm in beta. Pin a specific version in your MCP client config if you need reproducible behavior.
Next Steps
- Setup — Create a token, install the server, and configure Cursor or Claude Desktop
- Troubleshooting — Common setup and permission issues
- Team and Settings — Personal access tokens and team roles