Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

Jitsu

by jitsucomversion 1.0.0i★ 5,135iRuns in the cloud
Registry namecom.jitsu/mcp

How to install

What it does

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

  • Connects Runs in the cloud
  • Account or key Sign in to the service when you connect (OAuth)
  • Category Other

Install

Pick the AI app you use, then copy the settings.

Passed 4/4 checks · What you ask goes through the maker’s server (use.jitsu.com) · ✓ Commands checked Nov 13, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude · about 2 min

No key, nothing to install · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it

  1. Open Claude’s Connectors page

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  2. Click “Add” → “Custom” → “Web” and fill in these 2 fields

    Copy each value into the field with the same name in Claude, then click Continue

    Name · NameJitsu
    Remote MCP server URL · Addresshttps://use.jitsu.com/mcp

    Click Continue past the sign-in settings Claude detected · under Authentication choose what the maker says (Sign in now, Sign in when needed or No sign in), then click Add

  3. Turn it on in a chat

    +ConnectorsJitsu

  4. Try it

    Use Jitsu and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Jitsu or shows a Jitsu tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with ChatGPT, depending on your plan

Full MCP: ChatGPT Business, Enterprise or Edu on the web · Pro: connects with read/fetch permissions, so tools that change data may not work · Plus: not confirmed in OpenAI’s docs; if you see an add-custom-MCP option on the Plugins page you can try these steps · web only

  1. Open ChatGPT’s add-MCP page on the web

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. Fill in the name and address

    Enter a name, paste the address under Connection, tick the risk warning and click Create as a plugin

    Name · NameJitsu
    Connection · Addresshttps://use.jitsu.com/mcp
  3. Pick Jitsu in a chat

    Start a new chat and pick Jitsu from your plugins before typing

  4. Try it

    Use Jitsu and tell me what you can do for me, then show me one thing

    ✓ If ChatGPT says it is using Jitsu or shows a Jitsu tool in the answer, you are connected

Menu names checked against OpenAI’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Claude Code · about 2 min

No key, nothing to install

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  2. Paste this command and press Enter

    claude mcp add --transport http --scope user jitsu https://use.jitsu.com/mcp
  3. Type /mcp in Claude Code

    You should see Jitsu listed as connected

  4. Try it

    Use Jitsu and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Jitsu or shows a Jitsu tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor · about 2 min

No key, nothing to install

  1. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  2. Open the AI chat in Cursor in Agent mode

  3. Try it

    Use Jitsu and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Jitsu or shows a Jitsu tool in the answer, you are connected

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code · about 2 min

No key, nothing to install

  1. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  2. Open the AI chat in VS Code in Agent mode

  3. Try it

    Use Jitsu and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Jitsu or shows a Jitsu tool in the answer, you are connected

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

Address for apps that connect over the web

Addresshttps://use.jitsu.com/mcp

JSON settings are under “For developers” below

Stuck? Ask people who use Jitsu💬 Discussion →
For developers: Terminal commands and JSON settings

Over the web

Claude Code

claude mcp add --transport http --scope user jitsu https://use.jitsu.com/mcp

Cursor (~/.cursor/mcp.json)

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

VS Code (mcp.json)

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

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
Not on npm/PyPI
Verified domain
✓ jitsu.com
Connection
Runs in the cloud
Transport
streamable-http
Latest versioni
1.0.0
Categoryi
Other
Published to registryi
Aug 1, 2026
Code last changedi
Nov 13, 2026
Maker
jitsucom
Website
jitsu.com
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Connect over the internet in

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

All apps, with pros and cons →

Related guides

What it can do

The server asks you to sign in before it lists its tools.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 14, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain jitsu.com (the registry checks domain ownership)

  • ✓ Pass

    Still maintained

    Code last changed yesterday

  • – Not applicable

    Has a licence

    Not applicable: a cloud server run by the owner of jitsu.com; you don't run code from the repo

  • ✓ Pass

    Endpoint responds

    Responded in 491 ms (HTTP 401)

  • ✓ Pass

    Sign-in with OAuth

    Declares OAuth sign-in, so your AI app can take you to log in

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in with Google to post

User reviews

No reviews yet

Sign in with Google to write a review

Compared with others in Otheri

  • More stars than 99% of the other 19738 servers in this category
  • Published to the registry more recently than 16% of the other 19738 servers in this category
  • Basic checks equal to or better than 100% of the other 19738 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Jitsu safe?

It passed 4 of 4 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed yesterday, and the latest version (1.0.0) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).

What can I use instead?

In the same category: World Monitor, Claude Flow, Windmill

Others in the same category

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 97 tools.

by koala73Widely used★ 90.6KUpdated yesterday

Runs in the cloud✓ service owner · worldmonitor.app

Claude Flow

AI orchestration with hive-mind swarms, neural networks, and 87 MCP tools for enterprise dev.

by ruvnetWidely used↓ 13.5K/wk★ 81.6KUpdated 14 months ago

Runs on your computer

Windmill

Run Windmill scripts and flows and manage jobs, schedules, resources and variables.

by windmill-labsWidely used★ 18.6KUpdated 2 days ago

Runs in the cloud

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Open-source event data platform. An alternative to Segment.

Website · Docs · MCP Server · Jitsu Cloud · Self-hosting · Slack · MIT License


What is Jitsu?

Jitsu collects event data from your websites, apps and servers, and delivers it to your data warehouse and to whatever other tools you use. It covers the same ground as Segment, but it's MIT-licensed and self-hostable, so the whole pipeline can run inside your own infrastructure — or on Jitsu Cloud, same software, hosted.

Data lands in minutes, not hours: Segment loads warehouses once or twice a day (hourly at best), while Jitsu delivers per destination in batches as frequent as a minute, or row-by-row where that suits the destination. And where Segment bills by Monthly Tracked User, Jitsu Cloud bills by event volume, so the bill tracks data rather than audience size — while self-hosting has no usage billing at all.

A typical Jitsu setup gives you:

  • Event collection from the browser, mobile, or the server, via SDKs, an HTTP API, or a drop-in Segment proxy.
  • Delivery to destinations — ClickHouse, BigQuery, Snowflake, Redshift, Postgres, S3, GCS, and dozens of SaaS tools, streamed or micro-batched depending on what the destination prefers. See the destination catalog.
  • [Functions](https://jitsu.com/docs/functions) — JavaScript that runs on every event to filter, transform, and enrich it before delivery.
  • Write them in the browser, or build and deploy them from your own repo with the Jitsu CLI — jitsu-cli init scaffolds a TypeScript project with tests, and jitsu-cli deploy ships it to your workspace. Use whatever tooling you like: TypeScript, npm libraries, your own test suite, and your normal CI.
  • Connector syncs — pull data *into* your warehouse from third-party sources (Airbyte-compatible connectors).
  • A user identity graph and profile builder, built automatically from the event stream.
  • [Live Events](https://jitsu.com/docs/features/live-events) — see every event, function log and destination write as it happens, which makes debugging a pipeline a matter of seconds rather than days.
  • An [MCP server](https://jitsu.com/docs/mcp), so an AI agent can configure and operate all of the above.

Get started with Jitsu Cloud

The fastest way to run Jitsu is [Jitsu Cloud](https://use.jitsu.com) — we host and scale it for you.

  • Free tier: 200k events/month, no credit card required.
  • Unlimited destinations and unlimited captured events on every plan.
  • A free ClickHouse instance is included, so you can go from zero to queryable event data without provisioning a warehouse first.
  • Custom domains, events debugger, and the Configuration API on the free tier too.

See pricing for the full breakdown, or jump straight into the Quick Start guide.

Once you have a workspace:

  1. Create a site (a stream) and grab your write key.
  2. Add a destination — ClickHouse, BigQuery, Snowflake, Postgres, S3, or anything from the catalog.
  3. Start sending events using one of the methods below.
Sending events
MethodUse it for
HTML snippetAny website, no build step
@jitsu/jsIsomorphic — works in the browser and in Node.js
@jitsu/jitsu-reactReact and Next.js apps
HTTP APIAny language, backend services
Segment proxyMigrating off Segment without touching client code

Everything the UI does is also available through the Management API and the Jitsu CLI.

Jitsu MCP Server

Jitsu ships a Model Context Protocol server, so coding agents and AI assistants can build and operate your data pipelines directly — no clicking through the UI.

An agent connected to Jitsu can set up a destination, wire a connection, send a test event, read the resulting Live Events, notice that a function threw, fix the function, and re-run it — the full loop, without a human in the middle.

Endpoint: https://use.jitsu.com/mcp (or /mcp when self-hosting).

Connect your client

Claude Code

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

Other clients (Claude Desktop, Cursor, VS Code) take the same URL — see jitsu.com/docs/mcp for their setup.

Authentication

Interactive clients use OAuth 2.1 — no API key to manage. The first tool call opens a browser tab asking you to approve the connection; tokens are scoped, listed, and revocable from your account settings page.

Headless environments (CI, cron, servers) use a personal API key instead — generate one on the user settings page and pass it as Authorization: Bearer : :

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

--header "Authorization: Bearer $JITSU_API_KEY"

What the agent can do

25 tools, covering everything the console does: read and write workspace configuration (destinations, streams, connections, functions), query Live Events and function logs, run and cancel connector syncs, discover source streams and inspect sync state, execute functions and profile builders against test data, and pull event and sync statistics. Full reference: jitsu.com/docs/mcp.

Architecture

Jitsu is a handful of independently scalable services:

ServiceStackWhat it does
ingestGoHTTP endpoint that accepts events and writes them to Kafka
rotorTypeScriptRoutes events, runs Functions, applies destination-specific transforms
bulkerGoHigh-throughput warehouse ingestion — batching, schema management, retries
sync-controllerGoOrchestrates connector syncs (pulling data from third-party sources)
consoleNext.jsAdmin UI, Management API, and the MCP server

Backed by Postgres (configuration), Kafka/Redpanda (event bus), ClickHouse (live events and metrics), and MongoDB (profiles).

Bulker is also usable standalone if you just want a warehouse ingestion engine and are comfortable with low-level APIs.

Self-hosting

Jitsu is MIT-licensed and fully self-hostable, with no usage limits and no feature gating. Cloud is the path of least resistance; self-hosting is for when you need the data to stay inside your own infrastructure.

Quick start (Kubernetes / Minikube)

The development Helm chart is the recommended way to get a complete stack running locally. You'll need Minikube (a single-node Kubernetes cluster on your machine) and Helm v3+:

git clone -b newjitsu --single-branch https://github.com/jitsucom/jitsu

cd jitsu/helm

minikube start # give the VM at least 8GB RAM ./dev-deploy.sh deploy ./dev-deploy.sh tunnel # in a second terminal

./dev-deploy.sh tunnel runs minikube tunnel, which routes the cluster's LoadBalancer services to localhost so you can reach them from your browser — console on :3000, ingest on :3049, bulker on :3042, rotor on :3401, plus Postgres, ClickHouse, MongoDB and Kafka. It asks for sudo (it binds privileged ports) and has to keep running in its own terminal for the whole session.

The console will be at http://localhost:3000. Full instructions: Self-hosting Quick Start.

Production

For real deployments, read the Production Deployment guide and the Configuration Reference. It covers scaling each service, Kafka sizing, and the environment variables every component reads.

Contributing

Contributions are welcome. CONTRIBUTING.md covers the repository layout, how to set up a development environment and run the test suites, and the branch, commit and pull request conventions.

Community & support

  • [Slack](https://jitsu.com/slack) — the fastest way to reach the team and other users
  • [GitHub Issues](https://github.com/jitsucom/jitsu/issues) — bugs and feature requests
  • [Docs](https://jitsu.com/docs) — guides and reference

License

Jitsu is licensed under the MIT License.