Log inSubmit server
Jitsu logo

Jitsu

Manage Jitsu destinations, streams, connections, functions, and live events for application and API data pipelines.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Jitsu

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
Server URL
https://use.jitsu.com/mcp

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Hosted endpointLive · TodayLive Remote EndpointOur automated health check connected to this remote MCP endpoint successfully.Last checked 11/9/2026, 6:00:30 AM

Clients with native remote MCP support can connect directly to this URL.

Remote endpoint
https://use.jitsu.com/mcp

Overview

The Jitsu MCP server manages Jitsu data pipelines, including destinations, streams, connections, functions, and live events. Jitsu collects events generated by applications and pulls data from APIs before sending it to data warehouses.

Use cases

  • Manage Jitsu destinations for warehouse delivery
  • Configure streams for application event collection
  • Update connections used by API ingestion
  • Review live events in a Jitsu pipeline

Key features

  • Destination management
  • Stream management
  • Connection management
  • Function management
  • Live event management
  • Application and API data collection

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

48/49 checks healthy over the last 91d

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars5.1kStargazers on the source repository.
Last commit3d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Jitsu works

What Jitsu MCP server does

The Jitsu MCP server is intended for managing the main objects in a Jitsu data pipeline: destinations, streams, connections, functions, and live events. The available listing identifies these management areas, while Jitsu itself is described as an open-source data collection service.

Jitsu supports two broad data flows. Applications can emit events that Jitsu captures and streams to a data warehouse. Jitsu can also retrieve information from APIs and save the resulting data to a data warehouse. This makes the server relevant to teams operating event collection and API-ingestion workflows through Jitsu.

Treat the listed management areas as the supported scope, rather than assuming a particular tool naming convention.

How it works

Jitsu sits between data producers and warehouse destinations. Application events can enter the collection pipeline, while API-backed sources provide another way to bring data into the system. Pipeline configuration determines how those inputs are handled and where data is sent.

The Jitsu MCP server exposes the management surface described in the listing so an agent can work with pipeline resources. Those details should be confirmed before using it in an automated workflow.

Setup and configuration

Jitsu can be started locally with Docker Compose. The documented flow is to clone the repository, allow write access to the compose-data/ directory where needed, and run docker-compose up. Once the build completes, the configurator is available at http://localhost:8000/configurator.

The project also documents one-click Heroku deployment, deployment on Kubernetes through Plural, and building from source. A hosted Jitsu.Cloud option is available as well. Jitsu configuration is maintained through a YAML file, and the documentation includes separate guidance for deployment, configuration, geo-data enrichment, and scaling.

These instructions cover Jitsu deployment rather than MCP-specific client registration.

Tools and capabilities

The listed management capabilities are:

  • Manage destinations that receive pipeline data.
  • Manage streams used for data movement.
  • Manage connections between Jitsu and external systems.
  • Manage functions used in pipeline processing.
  • Inspect or manage live events.

For broader data collection, Jitsu can capture application-generated events and pull records from APIs, then write the data to a data warehouse.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Jitsu

Jitsu is an MCP server that connects agents to Jitsu data pipelines for managing destinations, streams, connections, functions, and live events. Jitsu collects application-generated events and pulls data from APIs, then streams or saves that data to data warehouses.

Clone the repository, grant write access to `compose-data/` if required, run `docker-compose up`, and open the local configurator at `http://localhost:8000/configurator`.

Yes, Jitsu can be deployed with Docker Compose. The documented local setup starts from a repository clone and uses `docker-compose up`; the project also provides separate Docker deployment documentation.

It therefore does not establish a Cursor integration or provide client-specific configuration for the Jitsu MCP server.

Related MCP servers

All in Data Platforms All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewJitsu AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/jitsu?style=directory)](https://allmcps.com/mcp/jitsu)
HTML Embed
<a href="https://allmcps.com/mcp/jitsu"><img src="https://allmcps.com/api/badge/jitsu?style=directory" alt="Jitsu on AllMCPs" /></a>