Skip to content
EmitKitDocs
Esc
↑↓navigate↵open⌘Jpreview

MCP server

Give agents EmitKit's API operations as MCP tools, and new events as they happen.

EmitKit’s MCP server lives at:

https://api.emitkit.com/mcp

It speaks stateless Streamable HTTP with JSON responses and offers one tool for each API operation:

Tool Does Required arguments
createEvent Sends an event (source defaults to mcp); with buttons or fields it asks for a decision channelName, title
getEvent Reads an event and its answer id
listEvents Lists recent events, newest first (filter by channel, since, before) none
listChannels Lists the Project’s channels none
cancelEvent Stops an event from waiting for an answer id
identifyUser Creates or updates an identity userId
deleteIdentity Erases an identity user_id

Tool calls run the same code as the REST API: the same validation, rate limit, idempotency (idempotencyKey on createEvent), and Organization and Project scope. The result carries the API’s JSON response. A read-only key only sees getEvent, listEvents and listChannels. A missing, invalid or rate-limited key gets an HTTP 401 or 429 for every request, before any tool runs.

Clients sign in with OAuth or send an API key in a request header: see Connect a client for the steps in each client. It supports MCP protocol versions 2026-07-28 (per-request metadata, server/discover), 2025-11-25, 2025-06-18, 2025-03-26, and 2024-11-05 (initialize).

On every version, agents can also subscribe to new events with MCP Events: EmitKit posts each matching event to the agent as a signed webhook.

Was this page helpful?