---
title: MCP server
description: Give agents EmitKit's API operations as MCP tools.
sidebar:
  order: 0
---

EmitKit's MCP server lives at:

```text
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`) | `channelName`, `title` |
| `identifyUser` | Creates or updates an identity | `user_id` |
| `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.

The server authenticates with an [API key](/api/api-keys) sent in a request
header. It supports MCP protocol versions `2025-11-25`, `2025-06-18`,
`2025-03-26`, and `2024-11-05`.

**[Connect a client](/mcp/clients)**

Claude Code and other clients that send a fixed header.

**[Authenticate with an API key](/mcp/api-key)**

Which headers to send, and how to keep the key safe.

:::warning
Never add a key to the MCP URL. EmitKit only reads credentials from headers,
and URLs end up in logs and browser history.
:::