Jitsu

com.jitsuPublished by jitsu.comOfficial publisherv1.0.0Updated Oct 27, 2026

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureDeveloper ToolsData & Analytics

Overview

AI-generated overview

Remote Jitsu MCP server that lets an assistant configure and operate event data pipelines: destinations, streams, connections, functions and live events.

What you can do
  • Read and write workspace configuration: destinations, streams, connections and functions
  • Query Live Events and function logs to debug a pipeline
  • Run and cancel connector syncs, discover source streams and inspect sync state
  • Execute functions and profile builders against test data
  • Pull event and sync statistics
When to use it
Useful when you run Jitsu (Cloud or self-hosted) and want an agent to set up destinations, wire connections, send test events, read Live Events, fix a failing function and re-run it without clicking through the console.
Requirements
A remote MCP endpoint (Jitsu Cloud at use.jitsu.com, or your own console URL when self-hosting) and a Jitsu workspace. Interactive clients authenticate with OAuth 2.1; headless setups need a personal API key sent as an Authorization Bearer header.
Before you install
The tools write workspace configuration and can run or cancel connector syncs, so changes affect a live pipeline. Headless use requires a personal API key (key ID and secret) in the Authorization header. Jitsu Cloud bills by event volume, and self-hosting needs a full stack of services.

Installation

In SourceWeft

  1. Open Jitsu in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.jitsu%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "jitsu": {
      "type": "http",
      "url": "https://use.jitsu.com/mcp"
    }
  }
}

README

[Image] [Image]

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

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

[Featured on Hacker News] [Jitsu - Open-source real-time data collection platform | Product Hunt]

What is Jitsu?

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 on Jitsu 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.

A typical Jitsu setup gives you:

  • Event collection from the browser, mobile, or the server, via SDKs, 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 the Jitsu CLI — jitsu-cli init scaffolds a TypeScript project with tests, and jitsu-cli deploy ships it to your workspace. Use whatever tooling you like: TypeScript, npm libraries, your own test suite, and your normal CI.
  • Connector syncs — pull data into your warehouse from third-party sources (Airbyte-compatible connectors).
  • A user identity graph and profile builder, built automatically from the event stream.
  • Live Events — see every event, function log and destination write as it happens, which makes debugging a pipeline a matter of seconds rather than days.
  • An MCP server, so an AI agent can configure and operate all of the above.

[Image]

Get started with Jitsu Cloud

The fastest way to run Jitsu is Jitsu 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.
  • A free ClickHouse instance is 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.

See pricing for the full breakdown, or jump straight into the Quick Start guide.

Once you have a workspace:

  1. Create a site (a stream) and grab your write key.
  2. Add a destination — ClickHouse, BigQuery, Snowflake, Postgres, S3, or anything from the catalog.
  3. Start sending events using one of the methods below.

Sending events

MethodUse it for
HTML snippetAny website, no build step
@jitsu/jsIsomorphic — works in the browser and in Node.js
@jitsu/jitsu-reactReact and Next.js apps
HTTP APIAny language, backend services
Segment proxyMigrating off Segment without touching client code

Everything the UI does is also available through the Management API and the Jitsu CLI.

Jitsu MCP Server

Jitsu ships a Model Context Protocol server, 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>/mcp when self-hosting).

Connect your client

Claude Code

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

Other clients (Claude Desktop, Cursor, VS Code) take the same URL — see jitsu.com/docs/mcp for their setup.

Authentication

Interactive clients use OAuth 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 as Authorization: Bearer <keyId>:<keySecret>:

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

What the agent can do

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.

Architecture

Jitsu is a handful of independently scalable services:

ServiceStackWhat it does
ingestGoHTTP endpoint that accepts events and writes them to Kafka
rotorTypeScriptRoutes events, runs Functions, applies destination-specific transforms
bulkerGoHigh-throughput warehouse ingestion — batching, schema management, retries
sync-controllerGoOrchestrates connector syncs (pulling data from third-party sources)
consoleNext.jsAdmin UI, Management API, and the MCP server

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

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

Self-hosting

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.

Quick start (Kubernetes / Minikube)

The development Helm chart is the recommended way to get a complete stack running locally. You'll need Minikube (a single-node Kubernetes cluster on your machine) and Helm v3+:

bash
git clone -b newjitsu --single-branch https://github.com/jitsucom/jitsucd 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 tunnel runs minikube tunnel, which routes the cluster's LoadBalancer services to localhost so 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 for sudo (it binds privileged ports) and has to keep running in its own terminal for the whole session.

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

Production

For real deployments, read the Production Deployment guide and the Configuration Reference. It covers scaling each service, Kafka sizing, and the environment variables every component reads.

Contributing

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

Community & support

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

License

Jitsu is licensed under the MIT License.

Source: README.md at commit c93a581

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Jitsu integrations

Gracie Barra Jiu-Jitsu

Published by GitHub account junoventures

Remote MCP endpoint for a neighborhood business directory that lets an assistant search places, events, menus, bookings, tickets and store products.

Streamable HTTPWeb executable
Location & Lifestyle26 toolsOct 27, 2026