Pulse MCP server

Pulse 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.

process death. Delivery is idempotent: retries never duplicate events.

• Tiny. The web SDK is ≤ 10 KB gzipped with zero dependencies.
• Reliable. A persistent, ordered queue survives offline periods and

no ad SDKs. The SDK sends only the events you send it.

• Honest about privacy. No auto-capture, no fingerprinting, no IDFA/GAID,

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.

• One protocol, four platforms. Every SDK implements the same

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

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

call track — 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.

• Every event gets an idempotencykey and a timestamp at the moment you

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.

• The queue is persistent (localStorage on web, files on mobile) and ordered.

rejecting (a "poison" batch) is moved aside after 10 attempts so it can never block everything behind it.

• Retries use exponential backoff with jitter. A batch the server keeps

The normative details are in protocol/PROTOCOL.md.

Development

Shortened. The full README is on GitHub.