Skip to main content
@waniwani/sdk plugs into an existing MCP server and ships two things:
  • Event tracking. Automatic tool.called events (name, duration, status, input, output, client info) plus custom events, batched and forwarded to the WaniWani dashboard.
  • Flows. A typed state machine compiled into a single MCP tool that can pause on interrupt, branch on conditions, and persist state across turns, all keyed by the MCP session.

​
Who this is for

You already run an MCP server (via @modelcontextprotocol/sdk, @vercel/mcp-handler, Skybridge, or similar) and you want analytics, multi-turn conversations, or both without rewriting your transport or auth layer.

​
What it is not

This is not an MCP runtime. It sits on top of the server you already deploy. Zero runtime dependencies, sub-5KB core bundle.

​
Next step

Head to the Quickstart to wire up an existing server in under 5 minutes.