Jitsu MCP server
online · 100% uptimeManage Jitsu data pipelines: destinations, streams, connections, functions, live events.
5.1k stars
Reviews
Write oneNobody has reviewed Jitsu yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Jitsu tools
Tool list not cached yet. `describe` through the gateway fetches it live.
Public scan report
scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 108ms (auth required)20/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityOAuth resource metadata advertised on 40115/15
- Maintenancelast push 0 days ago15/15
- Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace8/10
Install Jitsu in Claude Code, Cursor or VS Code
claude mcp add --transport http mcp https://use.jitsu.com/mcp
What the publisher says
From the Jitsu repository's README, as published. We do not edit it. Read it on GitHub
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:
SDKs, an HTTP API, or a drop-in Segment proxy.
- Event collection from the browser, mobile, or the server, via
dozens of SaaS tools, streamed or micro-batched depending on what the destination prefers. See the destination catalog.
- Delivery to destinations — ClickHouse, BigQuery, Snowflake, Redshift, Postgres, S3, GCS, and
transform, and enrich it before delivery.
- Functions — JavaScript that runs on every event to filter,
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.
- Write them in the browser, or build and deploy them from your own repo with the
connectors).
- Connector syncs — pull data into your warehouse from third-party sources (Airbyte-compatible
destination write as it happens, which makes debugging a pipeline a matter of seconds rather than days.
- A user identity graph and profile builder, built automatically from the event stream.
- Live Events — see every event, function log and
the above.
- An MCP server, so an AI agent can configure and operate all of
Get started with Jitsu Cloud
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Jitsu: common questions
- Is Jitsu MCP server safe?
- Yes, by our scan: it is graded A (97/100). Read the Jitsu safety report
- How do I install Jitsu?
- It runs remotely at use.jitsu.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Jitsu need an API key?
- No key to paste: it signs you in with OAuth when your client connects.
- Is Jitsu maintained?
- The last commit was 4 days ago (2026-09-24). The latest release is v1.0.0.
- Is Jitsu up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.