Jitsu

Jitsu is an open-source event data platform, an MIT-licensed alternative to Segment: it collects events from your websites, apps and servers and delivers them to your data warehouse and other tools, on Jitsu Cloud or self-hosted. Its MCP server lets your agent configure and operate those pipelines directly, with tools that mirror Jitsu's Management API. What you can do with it - Create, update and delete destinations, streams, connections, functions, domains and notifications, after reading each type's schema - Read Live Events: incoming events, function logs, warehouse write statuses and the dead-letter queue, filtered by source, log level, time range and text - Test destination credentials, and run a function against a sample event without saving anything - Run, cancel and inspect connector syncs, discover a source's streams and reset a sync's saved cursor - Pull event and sync statistics, and read the workspace audit log How it connects - One hosted address: https://use.jitsu.com/mcp. If you self-host Jitsu, use /mcp on your own console host instead. - Interactive agents sign in with OAuth: a browser tab opens the first time and you approve the connection once. Connected agents are listed under API Keys in your Jitsu account, where you can revoke them. - For CI and other headless setups, pass a personal API key from your Jitsu user settings in an Authorization: Bearer header. - Jitsu documents setup for Claude Code, Claude, Cursor and VS Code. Good to know - Every tool carries MCP annotations, so your agent can approve read-only tools on its own; update_resource, delete_resource and reset_sync_state are the destructive ones. - Changes made through MCP land in the workspace audit log with an MCP origin. - An API key acts as you, with all your workspace access.