Jitsu

Jitsu MCP is a Model Context Protocol server that lets coding agents in Claude Code, Claude Desktop, Cursor, or VS Code operate a full event data pipeline through natural language. It targets data and platform engineers who already use Jitsu, the open-source Segment alternative that collects event data from websites, apps, and servers and delivers it to warehouses and downstream tools , and now want to configure and debug that plumbing without leaving their editor. A single command registers the remote server at use.jitsu.com/mcp, after which the agent can act against a live workspace. Once connected, the agent can configure destinations and streams, debug pipelines by querying Live Events and function logs in real time, execute JavaScript Functions against test data and iterate on them, and trigger or cancel connector syncs while inspecting sync state . That covers most of the day-to-day surface area of running an event pipeline, from wiring a new ClickHouse or BigQuery destination to fixing a broken transform, and it works against both Jitsu Cloud and self-hosted installs. The launch matters because event pipeline work has historically meant clicking through a console or hand-editing YAML, and this collapses those loops into the same agent session where the tracking code itself is being written. Jitsu was founded by Peter Wysinski and CTO Vladimir Klimontovich , and the MCP release fits a broader push at the company toward agent-driven workflows, alongside a public OpenAPI spec and the jitsu-cli for scripting and CI. For teams already piping events through Jitsu, it removes a context switch. For teams evaluating a Segment replacement, it is a concrete signal that the product is being built for engineers who now expect their infrastructure to be legible to an LLM.