# Jitsu MCP server

> Manage Jitsu data pipelines: destinations, streams, connections, functions and live events from your AI assistant.

- Listing: https://mcp.tc/i/jitsu
- Connect: use the server's own URL `https://use.jitsu.com/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Data & Analytics](https://mcp.tc/c/analytics)
- Vendor: Jitsu
- Homepage: <https://jitsu.com/docs/mcp>
- Repository: <https://github.com/jitsucom/jitsu>
- Package: npm `root`

## About

Connects an assistant to a Jitsu workspace, the open-source event data platform. It can read and edit workspace configuration (destinations, streams, connections, functions), query Live Events and function logs, run and cancel connector syncs, test functions against sample data and pull event and sync statistics.

The server is hosted at https://use.jitsu.com/mcp for Jitsu Cloud, and at /mcp on self-hosted installs. Interactive clients sign in with OAuth 2.1 in the browser. Headless environments can use a personal API key sent as a Bearer token.

## What it can do

- Create and edit destinations, streams and connections
- Edit and run Jitsu Functions against test data
- Inspect Live Events and function logs
- Run and cancel connector syncs and inspect sync state
- Pull event and sync statistics

## Example prompts

- "Add a ClickHouse destination and connect it to my website stream."
- "Show the latest live events for my main stream and flag any errors."
- "Why did my enrichment function throw on the last event? Fix it."
- "Run the Postgres connector sync and report its status."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http jitsu https://use.jitsu.com/mcp
```

2. Start Claude Code, type `/mcp`, pick **jitsu** and choose **Authenticate**. A browser window opens for the Jitsu sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **Jitsu** and paste this URL:

```url
https://use.jitsu.com/mcp
```

3. Click **Add**, then **Connect**, and sign in when Jitsu asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Jitsu&connectorUrl=https%3A%2F%2Fuse.jitsu.com%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://use.jitsu.com/mcp` and click **Add**.

3. Click **Connect** and sign in when Jitsu asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**.

2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server.

3. Paste `https://use.jitsu.com/mcp` as the server URL and choose **OAuth**. ChatGPT sends you to Jitsu to sign in.

Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=jitsu&config=eyJ1cmwiOiJodHRwczovL3VzZS5qaXRzdS5jb20vbWNwIn0%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "jitsu": {
      "url": "https://use.jitsu.com/mcp"
    }
  }
}
```

Cursor shows **Needs authentication** next to the server. Click the button beside it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=jitsu&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fuse.jitsu.com%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"jitsu","type":"http","url":"https://use.jitsu.com/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "jitsu": {
      "type": "http",
      "url": "https://use.jitsu.com/mcp"
    }
  }
}
```

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "jitsu": {
      "serverUrl": "https://use.jitsu.com/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add jitsu --url https://use.jitsu.com/mcp
codex mcp login jitsu
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.jitsu]
url = "https://use.jitsu.com/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http jitsu https://use.jitsu.com/mcp
```

Then, inside Gemini CLI, run `/mcp auth jitsu` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "jitsu": {
      "type": "http",
      "url": "https://use.jitsu.com/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://use.jitsu.com/mcp`.

## Details

- Server version: 1.0.0
- Last checked: 2026-10-07 (reachable, asks for credentials)
- Listed: 2026-10-05
- Updated: 2026-10-05

---
Source: https://mcp.tc/i/jitsu (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report