Ask about revenue, MRR, ad spend, LTV and CAC; install the Pulse SDK. Read-only.
Connect Remote server
claude mcp add --transport http pulse https://mcp.pulse.pulsecircle.studio/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
{
"mcpServers": {
"pulse": {
"url": "https://mcp.pulse.pulsecircle.studio/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
{
"servers": {
"pulse": {
"type": "http",
"url": "https://mcp.pulse.pulsecircle.studio/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://mcp.pulse.pulsecircle.studio/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
This server asks for a key before it lists its tools. Connect it with your own key to see them.
Headers
| Name | Description |
|---|---|
AuthorizationOptional, secret | Bearer <your Pulse API key> — from Settings in the Pulse web app. Clients that speak OAuth 2.1 can omit this and authorize instead. |
Details
| Endpoint | https://mcp.pulse.pulsecircle.studio/mcp (Streamable HTTP) |
| Package | @pulse-circle/[email protected] (NPM, stdio) |
| First published | 2 Sep 2026 |
| Last updated | 2 Sep 2026 |
| Registry name | studio.pulsecircle/pulse |
More developer tools servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
