Jitsu

by jitsucom

Not rated
GitHub

About

Manage Jitsu data pipelines from your agent: create destinations and streams, inspect live events, and edit transformation functions.

Details

Author
jitsucom
Categories
Marketing, Other, Automation, Database

Setup

Install Jitsu in your MCP client (Claude Desktop, Cursor, Windsurf, and others).

Repository: https://github.com/jitsucom/jitsu

Follow the installation instructions in the repository README, then restart your MCP client.

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

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

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 onJitsu 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.

- Event collectionfrom the browser, mobile, or the server, viaSDKs, 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— 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 theJitsu CLI—jitsu-cli initscaffolds a TypeScript project with tests, andjitsu-cli deployships it to your workspace. Use whatever tooling you like: TypeScript, npm libraries, your own test suite, and your normal CI.

The fastest way to run Jitsu isJitsu Cloud— 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.
- Afree ClickHouse instanceis 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.

Seepricingfor the full breakdown, or jump straight into theQuick Start guide.
- Create a site(a stream) and grab your write key.
- Add a destination— ClickHouse, BigQuery, Snowflake, Postgres, S3, or anything from the
catalog.
- Start sending eventsusing one of the methods below.

Everything the UI does is also available through theManagement APIand theJitsu CLI.

Jitsu ships aModel Context Protocolserver, 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<your-console-url>/mcpwhen self-hosting).

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

Other clients (Claude Desktop, Cursor, VS Code) take the same URL — seejitsu.com/docs/mcpfor their setup.

Interactive clients useOAuth 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 asAuthorization: Bearer <keyId>:<keySecret>:

claude mcp add --transport http jitsu https://use.jitsu.com/mcp \ --header "Authorization: Bearer $JITSU_API_KEY"

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.

Jitsu is a handful of independently scalable services:

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

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

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.

The development Helm chart is the recommended way to get a complete stack running locally. You'll needMinikube(a single-node Kubernetes cluster on your machine) andHelm 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 tunnelrunsminikube tunnel, which routes the cluster's LoadBalancer services tolocalhostso 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 forsudo(it binds privileged ports) and has to keep running in its own terminal for the whole session.

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

For real deployments, read theProduction Deployment guideand theConfiguration Reference. It covers scaling each service, Kafka sizing, and the environment variables every component reads.

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

- Slack— the fastest way to reach the team and other users
-
GitHub Issues— bugs and feature requests
-
Docs— guides and reference

Jitsu is licensed under theMIT License.

Free MCP that drives an audit of your marketing. Your AI connects, adsOS digs through your ads, email and site, and hands back a growth plan you can run today.

Build robust data workflows, integrations, and analytics on a single intuitive platform.

Official MCP server for dbt (data build tool) providing integration with dbt Core/Cloud CLI, project metadata discovery, model information, and semantic layer querying capabilities.

Bring Kubit into your AI workflow - query your warehouse with natural language

Query and analyze data with MotherDuck and local DuckDB

Skyvia MCP Endpoint is a no-code gateway that makes your business data accessible to AI assistants in real time.

Connect your business data to any MCP client. AgenticBI agents find the right data, join across systems, run queries, build dashboards, generate reports, and automate analytics workflows. No SQL required.

Apify-hosted MCP server for Airtable with 15 tools. Full CRUD for records, tables, fields, search, and schema inspection. No local setup needed.

Production-grade MCP server for Databricks: SQL Warehouses, Jobs API, multi-workspace support.

Visual no-code generator that turns any database into multiple scoped MCP servers — one per access group, with PII masking and fail-closed query scoping built in.

A Model Context Protocol server for CData Sync, enabling data replication and transformation.

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.