Skip to main content
@mcpulse/sdk is how data gets out of your MCP server. It is installed inside your own process, not in front of it.

​
Install

​
Requirements

The package ships ESM and CJS builds and its own types.
There are no runtime dependencies on purpose. @mcpulse/schemas was going to be the one exception and is not: it brings Zod with it, which would mean validating our own output inside every customer’s server when the API already validates it on arrival. The payload types are restated in the SDK’s own types.ts, and a contract test pins every field name so the two cannot drift.

​
Wrap your server

watch instruments the server in place and returns the same object, so the call can be dropped around an existing one without moving anything else. Two things matter about placement:
  • After your tools are registered. McpServer does not create its tools/call handler until the first tool exists. The SDK re-applies its wrapper after each later registration too, so both orders work — but registering first is the shape to write.
  • Once per server. Watching the same server twice is a no-op, guarded by a WeakSet. Left unguarded it would open a second session and report every call under both, doubling your numbers.

​
Which shape do you have?

stdio

One long-lived server. Wrap it once, at the top level.

Streamable HTTP

A fresh server per request. Wrap inside the factory.

​
Other languages

/m/:id/install in the dashboard opens on a card per language — the ten official MCP SDKs — and nine of them say Coming soon. Showing the nine is the point. The question a Python author opens that page with is is there one for me, and an empty page answers it with “this product is not for you” rather than “not yet”. Each card names the SDK an MCPulse package would wrap, so you can tell whether it is the one you are using. Any language can post to the ingest endpoint today. The package exists to save you writing that, not to gate it: it is one authenticated POST with a batch of JSON objects, and both payload shapes are documented in What is sent. See Ingest for the endpoint, the batch limits and the outcome vocabulary. There are no dates on the cards. A promise with a month on it is a promise to be wrong about.

​
Get a key

An ingest key is minted per MCP in the dashboard and shown once. The install page creates keys itself, so setup never bounces between pages. See Create a key. Without a key, watch() is a silent no-op — a server started without its key configured should be quiet, not a source of 401s on every flush.

​
Next