{ "markdown": "

\n\n\n

\n\n

\nOpen-source event data platform. An alternative to Segment.\n

\n\n

\nWebsite ·\nDocs ·\nMCP Server ·\nJitsu Cloud ·\nSelf-hosting ·\nSlack ·\nMIT License\n

\n\n

\n\n \n\n\"Jitsu\n

\n\n---\n\n## What is Jitsu?\n\nJitsu collects event data from your websites, apps and servers, and delivers it to your data\nwarehouse and to whatever other tools you use. It covers the same ground as Segment, but it's\nMIT-licensed and self-hostable, so the whole pipeline can run inside your own infrastructure —\nor on [Jitsu Cloud](https://use.jitsu.com), same software, hosted.\n\nData lands in minutes, not hours: Segment loads warehouses once or twice a day (hourly at best),\nwhile Jitsu delivers per destination in batches as frequent as a minute, or row-by-row where that\nsuits the destination. And where Segment bills by Monthly Tracked User, Jitsu Cloud bills by event\nvolume, so the bill tracks data rather than audience size — while self-hosting has no usage billing\nat all.\n\nA typical Jitsu setup gives you:\n\n- **Event collection** from the browser, mobile, or the server, via\n [SDKs, an HTTP API, or a drop-in Segment proxy](https://jitsu.com/docs/sending-data).\n- **Delivery to destinations** — ClickHouse, BigQuery, Snowflake, Redshift, Postgres, S3, GCS, and\n dozens of SaaS tools, streamed or micro-batched depending on what the destination prefers. See the\n [destination catalog](https://jitsu.com/docs/destinations/catalog).\n- **[Functions](https://jitsu.com/docs/functions)** — JavaScript that runs on every event to filter,\n transform, and enrich it before delivery.\n - Write them in the browser, or build and deploy them from your own repo with the\n [Jitsu CLI](https://jitsu.com/docs/jitsu-cli) — `jitsu-cli init` scaffolds a TypeScript project\n with tests, and `jitsu-cli deploy` ships it to your workspace. Use whatever tooling you like:\n TypeScript, npm libraries, your own test suite, and your normal CI.\n- **Connector syncs** — pull data *into* your warehouse from third-party sources (Airbyte-compatible\n connectors).\n- **A user identity graph and profile builder**, built automatically from the event stream.\n- **[Live Events](https://jitsu.com/docs/features/live-events)** — see every event, function log and\n destination write as it happens, which makes debugging a pipeline a matter of seconds rather than\n days.\n- **An [MCP server](https://jitsu.com/docs/mcp)**, so an AI agent can configure and operate all of\n the above.\n\n

\n\n

\n\n## Get started with Jitsu Cloud\n\nThe fastest way to run Jitsu is **[Jitsu Cloud](https://use.jitsu.com)** — we host and scale it for\nyou.\n\n- **Free tier: 200k events/month**, no credit card required.\n- Unlimited destinations and unlimited captured events on every plan.\n- A **free ClickHouse instance** is included, so you can go from zero to queryable event data\n without provisioning a warehouse first.\n- Custom domains, events debugger, and the Configuration API on the free tier too.\n\nSee [pricing](https://jitsu.com/pricing) for the full breakdown, or jump straight into the\n[Quick Start guide](https://jitsu.com/docs).\n\nOnce you have a workspace:\n\n1. **Create a site** (a stream) and grab your write key.\n2. **Add a destination** — ClickHouse, BigQuery, Snowflake, Postgres, S3, or anything from the\n [catalog](https://jitsu.com/docs/destinations/catalog).\n3. **Start sending events** using one of the methods below.\n\n### Sending events\n\n| Method | Use it for |\n| ----------------------------------------------------------------------- | ------------------------------------------------- |\n| [HTML snippet](https://jitsu.com/docs/sending-data/html) | Any website, no build step |\n| [`@jitsu/js`](https://jitsu.com/docs/sending-data/npm) | Isomorphic — works in the browser and in Node.js |\n| [`@jitsu/jitsu-react`](https://jitsu.com/docs/sending-data/react) | React and Next.js apps |\n| [HTTP API](https://jitsu.com/docs/sending-data/http) | Any language, backend services |\n| [Segment proxy](https://jitsu.com/docs/sending-data/segment-proxy) | Migrating off Segment without touching client code |\n\nEverything the UI does is also available through the\n[Management API](https://jitsu.com/docs/management-api) and the\n[Jitsu CLI](https://jitsu.com/docs/jitsu-cli).\n\n## Jitsu MCP Server\n\nJitsu ships a [Model Context Protocol](https://modelcontextprotocol.io) server, so coding agents and\nAI assistants can build and operate your data pipelines directly — no clicking through the UI.\n\nAn agent connected to Jitsu can set up a destination, wire a connection, send a test event, read the\nresulting Live Events, notice that a function threw, fix the function, and re-run it — the full\nloop, without a human in the middle.\n\n**Endpoint:** `https://use.jitsu.com/mcp` (or `/mcp` when self-hosting).\n\n### Connect your client\n\n**Claude Code**\n\n```bash\nclaude mcp add --transport http jitsu https://use.jitsu.com/mcp\n```\n\nOther clients (Claude Desktop, Cursor, VS Code) take the same URL — see\n[jitsu.com/docs/mcp](https://jitsu.com/docs/mcp) for their setup.\n\n### Authentication\n\nInteractive clients use **OAuth 2.1** — no API key to manage. The first tool call opens a browser\ntab asking you to approve the connection; tokens are scoped, listed, and revocable from your account\nsettings page.\n\nHeadless environments (CI, cron, servers) use a personal API key instead — generate one on the user\nsettings page and pass it as `Authorization: Bearer :`:\n\n```bash\nclaude mcp add --transport http jitsu https://use.jitsu.com/mcp \\\n --header \"Authorization: Bearer $JITSU_API_KEY\"\n```\n\n### What the agent can do\n\n25 tools, covering everything the console does: read and write workspace configuration\n(destinations, streams, connections, functions), query Live Events and function logs, run and cancel\nconnector syncs, discover source streams and inspect sync state, execute functions and profile\nbuilders against test data, and pull event and sync statistics. Full reference:\n[jitsu.com/docs/mcp](https://jitsu.com/docs/mcp).\n\n## Architecture\n\nJitsu is a handful of independently scalable services:\n\n| Service | Stack | What it does |\n| ------------------ | ----------- | ------------------------------------------------------------------------- |\n| **ingest** | Go | HTTP endpoint that accepts events and writes them to Kafka |\n| **rotor** | TypeScript | Routes events, runs Functions, applies destination-specific transforms |\n| **bulker** | Go | High-throughput warehouse ingestion — batching, schema management, retries |\n| **sync-controller**| Go | Orchestrates connector syncs (pulling data from third-party sources) |\n| **console** | Next.js | Admin UI, Management API, and the MCP server |\n\nBacked by Postgres (configuration), Kafka/Redpanda (event bus), ClickHouse (live events and\nmetrics), and MongoDB (profiles).\n\n[Bulker](./bulker) is also usable standalone if you just want a warehouse\ningestion engine and are comfortable with low-level APIs.\n\n## Self-hosting\n\nJitsu is MIT-licensed and fully self-hostable, with no usage limits and no feature gating. Cloud is\nthe path of least resistance; self-hosting is for when you need the data to stay inside your own\ninfrastructure.\n\n### Quick start (Kubernetes / Minikube)\n\nThe development Helm chart is the recommended way to get a complete stack running locally. You'll\nneed [Minikube](https://minikube.sigs.k8s.io/docs/start/) (a single-node Kubernetes cluster on your\nmachine) and [Helm v3+](https://helm.sh/docs/intro/install/):\n\n```bash\ngit clone -b newjitsu --single-branch https://github.com/jitsucom/jitsu\ncd jitsu/helm\n\nminikube start # give the VM at least 8GB RAM\n./dev-deploy.sh deploy\n./dev-deploy.sh tunnel # in a second terminal\n```\n\n`./dev-deploy.sh tunnel` runs `minikube tunnel`, which routes the cluster's LoadBalancer services to\n`localhost` so you can reach them from your browser — console on `:3000`, ingest on `:3049`, bulker\non `:3042`, rotor on `:3401`, plus Postgres, ClickHouse, MongoDB and Kafka. It asks for `sudo` (it\nbinds privileged ports) and has to keep running in its own terminal for the whole session.\n\nThe console will be at http://localhost:3000. Full instructions:\n[Self-hosting Quick Start](https://jitsu.com/docs/self-hosting/quick-start).\n\n### Production\n\nFor real deployments, read the\n[Production Deployment guide](https://jitsu.com/docs/self-hosting/production-deployment) and the\n[Configuration Reference](https://jitsu.com/docs/self-hosting). It covers scaling each service,\nKafka sizing, and the environment variables every component reads.\n\n## Contributing\n\nContributions are welcome. [CONTRIBUTING.md](CONTRIBUTING.md) covers the repository layout, how to\nset up a development environment and run the test suites, and the branch, commit and pull request\nconventions.\n\n## Community & support\n\n- **[Slack](https://jitsu.com/slack)** — the fastest way to reach the team and other users\n- **[GitHub Issues](https://github.com/jitsucom/jitsu/issues)** — bugs and feature requests\n- **[Docs](https://jitsu.com/docs)** — guides and reference\n\n## License\n\nJitsu is licensed under the [MIT License](LICENSE).\n", "bytes": 10949, "sha": "abec9e613e1e0999d9319e6551b82d7f8866cc62af90cd014301b3fe67031fd5", "repo_slug": "jitsucom/jitsu", "fonte": "repo", "truncated": false, "api": "https://agentalog.com/api/listings/mcp_com_jitsu_mcp_2b9191ea/readme" }