Jitsu

MCP server by Jitsu

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

OAuth sign-in (You sign in with the vendor the first time you connect)Streamable HTTP

Connect to Jitsu

Jitsu needs sign-in. Connect with its own URL:

https://use.jitsu.com/mcp

Your client opens Jitsu’s sign-in the first time you use it. The token stays between your client and Jitsu.

Share this server

Opens this page, with the URL and setup steps.

mcp.tc/i/jitsu

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 you 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

Tools

Jitsu lists its tools only after you sign in, so we can’t show them here. Your client lists them once you’re connected.

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.

Set up

Every client connects to use.jitsu.com, and Jitsu asks you to sign in the first time. Pick yours; the page remembers your choice.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport http jitsu https://use.jitsu.com/mcp
  1. 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:
https://use.jitsu.com/mcp
  1. 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:
  1. Check that the URL reads https://use.jitsu.com/mcp and click Add.
  2. 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

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

mcp.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

Or from a terminal:

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
{
  "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
{
  "mcpServers": {
    "jitsu": {
      "serverUrl": "https://use.jitsu.com/mcp"
    }
  }
}
  1. 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

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

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

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

Gemini CLI

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.

{
  "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.

Embed

Show Jitsu in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work

The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.

README badge

Badge preview, lightBadge preview, dark
Markdown
[![Jitsu on mcp.tc](https://mcp.tc/i/jitsu/badge.svg)](https://mcp.tc/i/jitsu)
HTML
<a href="https://mcp.tc/i/jitsu"><img src="https://mcp.tc/i/jitsu/badge.svg" alt="Jitsu on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML
<script src="https://mcp.tc/w/jitsu.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML
<iframe src="https://mcp.tc/embed/jitsu" title="Jitsu on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/jitsu.json

What each field means

AI prompt

Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the Jitsu card to your site.

Markdown
Add the mcp.tc card for Jitsu, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.

Put this tag where the card should appear. The card renders right before it:

```html
<script src="https://mcp.tc/w/jitsu.js" async></script>
```

To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.

```html
<div data-mcptc="jitsu"><a href="https://mcp.tc/i/jitsu">Jitsu on mcp.tc</a></div>
```

Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.

If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).

For a README or other Markdown docs, use the badge instead:

```markdown
[![Jitsu on mcp.tc](https://mcp.tc/i/jitsu/badge.svg)](https://mcp.tc/i/jitsu)
```

Reference: https://mcp.tc/embed

Change history

Its tools are behind a sign-in, so we can’t read them. Edits by its owner show up here.

Follow Jitsu and we’ll email you when something changes.

Nothing recorded yet. Edits by the server’s owner will show up here.

FAQ

Can I paste mcp.tc/i/jitsu into my MCP client?

No. mcp.tc links are pages, not server addresses. Connect with https://use.jitsu.com/mcp, so your client talks to Jitsu directly. The sign-in token only works there anyway. The quick link is for sharing: it opens this page, with setup steps for every client.

Does Jitsu need an API key or a sign-in?

Yes, you need a Jitsu account. The first time your client connects, it opens Jitsu’s sign-in page. The token goes straight to the server’s own URL, never through mcp.tc.

Is Jitsu a remote or a local server?

Remote. Jitsu hosts it at https://use.jitsu.com/mcp, and it speaks Streamable HTTP. There’s nothing to install.

What can Jitsu do?

You can create and edit destinations, streams and connections, edit and run Jitsu Functions against test data and inspect Live Events and function logs.

Which clients can use it?

Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT in developer mode, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.

Does mcp.tc track changes to Jitsu?

Partly. Jitsu’s tools are behind a sign-in, so its History tab shows only edits by its owner. Follow the listing to get an email when it changes.

Who wrote this page?

mcp.tc’s robot read Jitsu’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

mcp.tc isn’t affiliated with Jitsu. This page was built from Jitsu’s public metadata, last checked on 7 Oct 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.