Jitsu MCP
Jitsu MCP configures and debugs data pipelines: destinations, streams, functions, live events and syncs.
- 5,134 ★ on the repository
- Last commit
Extended access
Why this level
- With write access the agent changes destinations, streams and functions that carry user data.
- Live event content goes into the model context.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/jitsuDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- With write access the agent changes destinations, streams and functions that carry user data.
- Live event content goes into the model context.
This is third-party code. Review the repository files before installing.
What it does
Jitsu is an open-source Segment alternative for collecting and delivering events. Its MCP server is part of the console at `https://use.jitsu.com/mcp`, or `<console URL>/mcp` on a self-hosted install. An agent configures and runs data pipelines without clicking through the interface. Per the project description the agent sets up a destination, wires a connection, sends a test event, reads the resulting live events, notices a function error, fixes it and reruns: the full loop without a human. There are 25 tools: read and write workspace configuration (destinations, streams, connections, functions), queries over live events and function logs, running and cancelling connector syncs, discovering streams and inspecting sync state, executing functions and profile builders on test data, and event and sync statistics. Interactive clients sign in with OAuth 2.1 and unattended ones need a personal API key.
Who it is for. Data engineers and analysts running event pipelines in Jitsu who want to configure and debug them from Claude Code, Cursor or VS Code.
Good fit when
- The agent adds a new destination, links it to a stream and sends a test event.
- A function fails in production and the agent reads live events and the log, fixes the code and reruns it.
- A connector sync is started or cancelled on request and stream state is checked from the chat.
- A profile builder is tried on test data before it is switched on.
Not a fit when
- There is no Jitsu workspace: the server needs a console, cloud or self-hosted.
- The configuration must not change without a human: write tools are part of the set.
- CI without a browser has no personal API key: interactive OAuth sign-in will not work there.
Example request
Show the latest live events of the stream, find the error in the function, fix it and send a test event to check.MCP
- Transport
- http
- Authentication
- OAuth
Environment variables
JITSU_API_KEYsecret- Personal API key as `keyId:keySecret` for CI and cron; without it sign-in uses OAuth
Limitations
The MCP server is part of the Jitsu console and works with the user workspace. Interactive clients sign in with OAuth 2.1 through a browser, while unattended runs such as CI and cron need a personal API key in the `Authorization: Bearer <keyId>:<keySecret>` header. Write tools change destinations, streams, connections and functions, so confirm such calls by hand in production. OAuth tokens are scoped and revoked on the user settings page. The full reference for the 25 tools is at `jitsu.com/docs/mcp`.
How to disable. Remove the `jitsu` entry from the client settings and revoke the OAuth token or API key on the user settings page. Pipelines and data stay in the workspace.
FAQ
How do I connect Claude Code?
Run `claude mcp add --transport http jitsu https://use.jitsu.com/mcp`. OAuth 2.1 sign-in opens in the browser on the first tool call.
How do I work from CI?
Create a personal API key on the user settings page and send it in the `Authorization: Bearer <keyId>:<keySecret>` header.
What can the server do?
25 tools: workspace configuration, live events and function logs, connector syncs, running functions and profile builders on test data, and statistics.
Can I connect to a self-hosted install?
Yes, the address is built from the console: `<console URL>/mcp`.
Where is the reference?
At `jitsu.com/docs/mcp`, which also covers setup for Claude Desktop, Cursor and VS Code.
Discussion
No questions or reviews yet.
Related
MCP serversThe Airbyte MCP connects an agent to an Airbyte organization: pipelines, syncs, job logs and direct data reads.
An MCP server that answers questions about CSV, Excel, Parquet and JSONL without pasting rows into context.
One MCP server for SQLite, SQL Server, PostgreSQL and MySQL: read and change data, edit schemas and export to CSV and JSON
An agent queries GreptimeDB metrics, logs and traces with SQL, TQL and RANGE, with write protection and data masking
A DaJet Metadata based MCP server that exposes 1C metadata structure and runs SELECT queries against the database
MCP server and CLI to drive real Microsoft Excel: Power Query, DAX, VBA, PivotTables and charts
README in short
The Jitsu README has a separate MCP server section: the address, the connection command, sign-in methods and a general description of the 25 tools.