# Jitsu

Hands your agent the Jitsu platform: create a destination, wire a stream, fire a test event, read the result. Useful when a pipeline needs fixing without the web UI.

- MCP server · `type=mcp` · Claude Code, Codex, Cursor, GitHub Copilot, Windsurf (Devin Desktop), Cline, Zed, Gemini CLI · ★ 5112
- Author: jitsucom
- License: MIT · policy=link-only · description only; the file stays with the author
- Source: https://github.com/jitsucom/jitsu
- Updated: 2026-10-23
- HTML: https://affpapa.org/en/nevibecode/mcp/jitsu

## What it does

Jitsu is an open-source event data platform, positioned as a Segment alternative. Its MCP server exposes the platform to a coding agent, which can add a destination, connect a stream, push a test event, inspect Live Events, spot a function that threw, patch it and run again. The whole loop closes without a human in the middle.

The endpoint is `https://use.jitsu.com/mcp`, or `<your-console-url>/mcp` if you self-host. Interactive clients authenticate over OAuth 2.1, so there is no API key to store: the first tool call pops a browser tab for approval, and the scoped tokens can be reviewed or revoked from account settings. Headless setups — CI, cron, servers — fall back to a personal API key, since no browser is available there.

In Claude the server goes in with one command. Cursor, VS Code and Claude Desktop take the same URL. One thing to line up first: an agent with no Jitsu workspace and write key connects fine but has nothing to configure.

## Requirements
- Remote server: `https://use.jitsu.com/mcp`

## Install

### Claude Code (native platform)

**Platform CLI: remote server**
```bash
claude mcp add --transport http mcp https://use.jitsu.com/mcp
```

### Codex

**Platform CLI: remote server**
```bash
codex mcp add jitsu --url https://use.jitsu.com/mcp
```

### Cursor

**Config file**
File `.cursor/mcp.json`:
```json
{
    "mcpServers": {
        "jitsu": {
            "url": "https://use.jitsu.com/mcp"
        }
    }
}
```

### GitHub Copilot

**Config file**
File `.vscode/mcp.json`:
```json
{
    "servers": {
        "jitsu": {
            "type": "http",
            "url": "https://use.jitsu.com/mcp"
        }
    }
}
```

### Gemini CLI

**Platform CLI: remote server**
```bash
gemini mcp add -t http jitsu https://use.jitsu.com/mcp
```

## When to use it
- stand up a destination and attach it to an event stream
- send a test event and confirm it landed
- track down a function that fails on every event and fix it
- read Live Events without leaving the agent session
- rework a pipeline config without clicking through the UI

## Example prompts
- Connect to Jitsu and create a ClickHouse destination for the `web` stream
- Send a test event to the `web` stream and show me what shows up in Live Events
- A function on the `web` stream keeps throwing — find it in the logs and fix it

## Similar
- [World Monitor](https://affpapa.org/en/nevibecode/mcp/world-monitor.md) — MCP server · ★ 89408
- [Scrapling MCP Server](https://affpapa.org/en/nevibecode/mcp/scrapling-mcp-server.md) — MCP server · ★ 89433
- [apify-mcp-server](https://affpapa.org/en/nevibecode/mcp/apify-mcp-server.md) — MCP server · ★ 12927
- [Nhost](https://affpapa.org/en/nevibecode/mcp/nhost.md) — MCP server · ★ 9366
- [Finance Toolkit](https://affpapa.org/en/nevibecode/mcp/finance-toolkit.md) — MCP server · ★ 5458
- [JobSpy](https://affpapa.org/en/nevibecode/mcp/jobspy.md) — MCP server · ★ 4552

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md