Setup
Connect Pulse MCP to Cursor or Claude Desktop: create a personal access token, then paste the config into your client.
Before you begin
- Node.js 18 or later on the machine where your AI client runs (
node --version) - A Pulse account with access to the projects you want to query
Settings → SDK Configuration is the project API key for mobile SDKs. Pulse MCP needs a separate personal access token from Profile menu → Personal Access Tokens. Keys start with pulse_mcp_.
Step 1 — Create a Personal Access Token
- Sign in to the Pulse dashboard.
- Open the profile menu (avatar, bottom-left).
- Under Access, select Personal Access Tokens.
- Click Generate New Key, enter a name (for example
Cursor MCP), and click Generate. - Copy the full key immediately — it is shown only once.
See Team and Settings to manage tokens and roles.
Step 2 — Configure your AI client
Paste the block below into your MCP config. Replace pulse_mcp_YOUR_KEY_HERE with the token from Step 1.
The server runs via npx — no separate install step.
- Cursor
- Claude Desktop
Config file
| Scope | Path |
|---|---|
| All projects | ~/.cursor/mcp.json |
| This project only | .cursor/mcp.json (project root) |
You can also add servers in Cursor Settings → Tools & MCP.
Add this configuration
If the file already exists, add the pulse entry inside mcpServers — do not replace other servers.
{
"mcpServers": {
"pulse": {
"command": "npx",
"args": ["-y", "@dreamhorizonorg/pulse-mcp@beta"],
"env": {
"PULSE_BASE_URL": "https://pulse-server.pulse-ux.com",
"PULSE_API_KEY": "pulse_mcp_YOUR_KEY_HERE"
}
}
}
}
After saving
- Reload MCP servers (Cursor Settings → Tools & MCP), or restart Cursor.
- Use Agent mode in chat — MCP tools are not available in normal chat mode.
- Confirm pulse appears as connected under Tools & MCP.
Config file
| OS | Path |
|---|---|
| macOS | ~/Library/Application Support/Claude/claude_desktop_config.json |
| Windows | %APPDATA%\Claude\claude_desktop_config.json |
| Linux | ~/.config/Claude/claude_desktop_config.json |
Add this configuration
If the file already has other keys (for example preferences), add mcpServers alongside them — do not delete existing content.
{
"mcpServers": {
"pulse": {
"command": "npx",
"args": ["-y", "@dreamhorizonorg/pulse-mcp@beta"],
"env": {
"PULSE_BASE_URL": "https://pulse-server.pulse-ux.com",
"PULSE_API_KEY": "pulse_mcp_YOUR_KEY_HERE"
}
}
}
}
After saving
- Fully quit Claude Desktop (⌘Q on macOS — closing the window is not enough) and reopen.
- Open Settings → Connectors and confirm pulse is listed and connected.
To lock a specific release, replace @beta with a version from the npm registry.
Step 3 — Verify
Ask your assistant a question that uses Pulse data. The examples below assume all tool categories are registered — if a tool is missing, see Overview — tool categories or Troubleshooting.
Projects
- "List my Pulse projects using MCP tools."
- "Show details and team members for my production Android project."
App Vitals (crashes, ANRs, non-fatals)
- "Show the top 10 crash issues for the last 24 hours."
- "List ANR issues on Android over the past week."
- "Pull stack traces for the most frequent crash group."
- "What's the occurrence trend for the top crash group over the last 7 days?"
- "Which screens are most affected by the top crash issue?"
Interactions
- "List all active critical interactions in this project."
- "What's the Apdex score for the
checkoutinteraction over the last 7 days?" - "Show the error rate time series for
login_submitthis week." - "Run root cause analysis on the
payment_failedinteraction." - "Which interactions are suggested but not yet configured?"
Sessions
- "List the 20 most recent session replays from the last 24 hours."
- "Find session replays from the past week where users hit checkout errors."
Events
- "Search for events matching
cart." - "List all event categories in this project."
- "Show the definition for the
add_to_cartevent."
Funnels & journeys
- "List all active funnels."
- "Show the steps and configuration for funnel ID 42."
- "List user journeys tagged
onboarding."
Alerts
- "List all configured alerts for this project."
- "Show evaluation history for the high error rate alert."
- "Which notification channels are set up for alerts?"
Heatmaps
- "Get touch heatmap data for
HomeScreenon Android for the last 7 days."
SDK config
- "Is session replay enabled in the active SDK config?"
- "What feature gates are set in the current SDK configuration?"
On first connect, only five core tools are available until the assistant calls register_tools. Register the categories you need — or all nine at once — before trying domain-specific queries.
Next Steps
- Overview — What you can query and available tool categories
- Troubleshooting — Auth, permissions, and connection issues