Allows AI agents to query analytics data such as revenue, MRR, ad spend, LTV, and CAC via a local MCP server.
Also known as Pulse-Circle-Studio/pulse-sdk, pulse-sdk, @pulse-circle/mcp
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.1.2
- Last commit
- Sep 4, 2026
- License
- MIT
What is Pulse MCP?
Pulse allows AI agents to query analytics data such as revenue, MRR, ad spend, LTV, and CAC via a local MCP server.
Summary generated from the project's README
About Pulse MCP server
Pulse provides a local MCP server designed to help AI agents access analytics data. Developers can connect their agents to this service using a stdio setup by running the command claude mcp add pulse -- npx -y @pulse-circle/mcp. This allows an LLM to query specific business metrics such as revenue, MRR, ad spend, LTV, and CAC directly through the local environment.
The underlying SDK architecture supports web, React Native, iOS, and Android platforms with a unified wire protocol. It focuses on a privacy-first approach by avoiding auto-capture, fingerprinting, or third-party ad SDKs. The system uses a persistent, ordered event queue that ensures data reliability during offline periods or process crashes through idempotent delivery and exponential backoff retries.
What you can do with it
- 1Monitor event tracking reliabilityUse the agent to verify that events are being queued and sent correctly even when the network is unstable.
Written from the project's README. Every use case is checked against a quote from it.
How to install Pulse MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Pulse MCP in Claude Code
$ claude mcp add pulse-sdk -- npx -y @pulse-circle/mcpInstall Pulse MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"pulse-sdk": {
"command": "npx",
"args": [
"-y",
"@pulse-circle/mcp"
]
}
}
}Install Pulse MCP in VS Code
.vscode/mcp.json
{
"servers": {
"pulse-sdk": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@pulse-circle/mcp"
]
}
}
}Install Pulse MCP in VS Code CLI
$ code --add-mcp '{"name":"pulse-sdk","type":"stdio","command":"npx","args":["-y","@pulse-circle/mcp"]}'Install Pulse MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"pulse-sdk": {
"command": "npx",
"args": [
"-y",
"@pulse-circle/mcp"
]
}
}
}Install Pulse MCP in Codex
$ codex mcp add pulse-sdk -- npx -y @pulse-circle/mcpInstall Pulse MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.pulse-sdk] command = "npx" args = ["-y", "@pulse-circle/mcp"]
Install Pulse MCP in Gemini CLI
$ gemini mcp add -s user pulse-sdk npx -- -y @pulse-circle/mcpInstall Pulse MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"pulse-sdk": {
"command": "npx",
"args": [
"-y",
"@pulse-circle/mcp"
]
}
}
}Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablepulse-circle-studio/pulse-sdk is public and reachablegithub.com/pulse-circle-studio/pulse-sdk ↗Pass
- Package names this repository as its source@pulse-circle/mcp names pulse-circle-studio/pulse-sdk as sourcenpmjs.com/package/@pulse-circle/mcp ↗Pass
- Build provenance (Sigstore attestation)Sigstore attestation for @pulse-circle/mcpnpmjs.com/package/@pulse-circle/mcp/v/0.1.2#provenance ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-09-04github.com/pulse-circle-studio/pulse-sdk ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from @pulse-circle/mcpPass
- No critical advisory in the package or its dependencies99 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeHTTPS endpoint answered 401 (sign-in required)Pass
README
View on GitHubPulse SDK
Open-source analytics SDKs for web, React Native, iOS, and Android. Add analytics to your app with a reliable, offline-first event queue and clean identity — and nothing else.
- Tiny. The web SDK is ≤ 10 KB gzipped with zero dependencies.
- Reliable. A persistent, ordered queue survives offline periods and process death. Delivery is idempotent: retries never duplicate events.
- Honest about privacy. No auto-capture, no fingerprinting, no IDFA/GAID, no ad SDKs. The SDK sends only the events you send it.
- One protocol, four platforms. Every SDK implements the same wire protocol and passes the same conformance fixtures in CI. The Pulse ingestion server replays those same fixtures — the contract is verified from both ends.
This repository holds the TypeScript packages. The Swift and Kotlin SDKs live
in pulse-sdk-native.
For AI agents
Install: npm i @pulse-circle/web, then Pulse.init('pk_...') and
Pulse.track('event', {...}). The package is self-contained (zero deps, default
endpoint baked in) and ships llms.txt inside it. Installing needs only npm; event
delivery happens in the end-user's browser at runtime.
Packages
| Package | What it's for | Install |
|---|---|---|
@pulse-circle/web |
Browser / any web app | npm i @pulse-circle/web |
@pulse-circle/react-native |
React Native & Expo | npm i @pulse-circle/react-native |
@pulse-circle/core |
Platform-agnostic engine (used by the above) | npm i @pulse-circle/core |
@pulse-circle/mcp |
Local (stdio) MCP server — offline setup/connect guides for AI agents | claude mcp add pulse -- npx -y @pulse-circle/mcp |
Quickstart (web)
npm install @pulse-circle/web
import { Pulse } from '@pulse-circle/web';
Pulse.init('pk_your_api_key');
// Track product events — the SDK batches, persists, and retries for you.
Pulse.track('subscription_started', { plan: 'pro' });
// Tie events to a user after login.
Pulse.identify('user_42');
// On logout, start a fresh anonymous identity.
Pulse.reset();
That's the whole API. See each package's README for the platform-specific install (script tag, Expo, etc.) and the full reference.
The API, everywhere
The five methods are identical across all four platforms, in each language's idiomatic syntax:
init(apiKey, options?) // configure once
track(event, properties?) // queue an event
identify(userId) // associate the current identity with a user id
reset() // logout: new anonymous identity
flush() // force-send the queue (tests, critical moments)
There are deliberately no screen/page auto-tracking and no revenue methods: revenue comes from server-side connectors, so there is exactly one source of truth per number.
The reliability contract
- Every event gets an
idempotency_keyand atimestampat the moment you calltrack— never at send time. Retries resend both byte-identical, and the server's primary key includes both, so a flaky network can never create a duplicate. - The queue is persistent (localStorage on web, files on mobile) and ordered. It survives reloads, crashes, and offline periods up to a per-platform cap, then evicts oldest-first with a debug warning rather than growing without bound.
- Retries use exponential backoff with jitter. A batch the server keeps rejecting (a "poison" batch) is moved aside after 10 attempts so it can never block everything behind it.
The normative details are in protocol/PROTOCOL.md.
Development
npm install
npm test # conformance fixtures + unit tests (vitest)
npm run lint
npm run typecheck
npm run build # tsup builds for every package
npm run size -w @pulse-circle/web # enforce the 10 KB budget
Conformance fixtures
protocol/fixtures is the source of truth for
cross-platform behaviour. Each JSON file is a scenario ("these API calls
produce these HTTP requests"); every SDK runs them through a shared
fixture runner, and the server replays them against
real ingestion. Change behaviour by changing a fixture, and every platform's
CI tells you who's out of contract.
Releasing
Versions are independent per package. Bump the version in the package's
package.json, then push a tag:
core-v0.1.0 | web-v0.1.0 | react-native-v0.1.0
The publish workflow verifies the tag
matches package.json, runs the full test + build + size gate, and publishes
to npm with provenance.
License
MIT © Pulse Circle Studio
Pulse MCP questions
How do I add Pulse MCP to Claude Code?
Run claude mcp add pulse-sdk -- npx -y @pulse-circle/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Pulse MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How do I install the Pulse MCP server for an AI agent?
You can add it to Claude using the command: claude mcp add pulse -- npx -y @pulse-circle/mcp
Does the SDK automatically track user screens or pages?
No, the SDK does not include auto-tracking for screens or pages to ensure data honesty.