Skip to content
Agents tracked: 502 Releases (7d): 762 Agent status: no reported issuesSince last limit reset: Claude 11d · Codex 9d For AI agents: Markdown Updated Nov 22, 2026

Jitsu

by jitsucom

set up and fix your event data pipeline by chat.

Data and analyticsOfficialRemote

GitHubWebsite

1. Made by

“Admin UI, Management API, and the MCP server”

The server is part of Jitsu's own console code in github.com/jitsucom/jitsu, it runs on use.jitsu.com, the docs are on jitsu.com, and the registry name com.jitsu is on Jitsu's domain.

github.com/jitsucom/jitsu/blob/e74ffe2bfcabca86d07aaa8384febe6b225898bc/README.md

Checked against its repository at one commit, on Nov 10, 2026. Tap a verdict to see its source.How we checkedReport an error

What Jitsu does

Jitsu collects events from your site or app, such as page views and sign-ups, and delivers them to your database or other tools. This server lets an AI assistant run that pipeline for you. It can add a destination, connect a source, watch events arrive live and fix a broken transform, without clicking through the Jitsu screens.

What people use it for

Send your events to a new database

Ask the assistant to add your Postgres or ClickHouse database as a destination and connect your site's events to it. It checks the login details first and then confirms that a test event landed.

Fix a transform that throws errors

When Live Events shows a function failing, the assistant reads its code, tries a fix on a sample event and only then saves it.

Re-run a data import from scratch

When a connector import from another service went wrong, the assistant can look at its logs, clear the saved position and start a full re-import.

Check how many events arrive

Ask how many events each source sent this week and which destinations failed. The assistant reads the counts without changing anything.

See what an assistant changed

Owners can read the change log filtered to changes made through this server, to review what an assistant did before.

Pipeline changes from your build server Idea

Keep your Jitsu setup in step with your releases by letting a scheduled job's agent apply the same configuration each time, with a personal key.

Jitsu popularity

5,135
GitHub stars, jitsucom/jitsu
0
public agent projects connect it
Jitsu: GitHub starsjitsucom/jitsu 5,135

Tools it gives your agent (26)

What it sends and its license

Sends

every tool call with its arguments, including destination credentials and function code the agent writes

To use.jitsu.com (or your self-hosted console); on each tool call. Opt out: self-host Jitsu.

Sends

connection checks and test runs

To your own data sources and destinations, and whatever your function code calls; on test_connection, check_source_credentials, discover_streams, run_function and run_profile_builder. Opt out: do not call those tools.

The Jitsu code, this server included, is free under the MIT license and can be run on your own servers. Jitsu Cloud has a free plan with 200,000 delivered events a month and paid plans above that.

In a paid app
Yes

The code is MIT, free for commercial use and self-hosting; Jitsu Cloud bills by delivered events beyond the free 200k a month.

“Permission is hereby granted, free of charge, to any person obtaining a copy of this software” source

Pass on its files
With conditions

Copies and changed versions are allowed under MIT with the copyright and permission notice kept.

“The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.” source

client-work
Yes

Allowed; the assistant works with the permissions of the person who connected it.

“The key maps to your user and inherits your workspace access, so an agent running with it can do anything you can.” source

Is it alive

Latest version

1.0.0 in the registry, updated Jul 31, 2026

Last release

registry entry 1.0.0, published 2026-07-31; code last changed 2026-11-06

Remote endpoint
yes: https://use.jitsu.com/mcp answered an unauthenticated GET with 401 (sign-in required, server reachable) on 2026-11-10

Alternatives

Jitsu This page

5,135 starsRemote

twilio-segment

Pick it if you want a hosted customer data platform rather than an open-source pipeline

Local

airbyte

Pick it if you mainly import data from other services into a warehouse

Local

All data and analytics servers

Get started

Tell your AI assistant

“Connect the Jitsu MCP server at https://use.jitsu.com/mcp in Claude Code; after I approve it in the browser, list my workspaces and the destinations in the first one. Ask me before update_resource, delete_resource, run_sync or reset_sync_state.”

Connect it

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

Mistakes to avoid

Guess the destination payload and call create_resource directly
Call get_resource_schema for the type (and subtype, e.g. postgres) first, then create_resource with matching data

data must match the schema for the type.

Treat the first discover_streams or check_source_credentials answer as the result
Poll (get_source_check_result for credentials) until the result is ready

Operations that talk to the real source are asynchronous.

Fix a function by calling update_resource straight away
Try the fix with run_function on a sample event first, then save with update_resource

update_resource overwrites the live function; run_function persists nothing.

Commit the API key in .cursor/mcp.json or paste it in chat
Read it from an environment variable (${JITSU_API_KEY}) in the headers block

The key carries your whole workspace access and does not have to expire.

Expect OAuth sign-in to work in CI
Use a personal API key in an Authorization Bearer header for headless runs

The browser flow cannot run there.

Questions

Do I need an API key?

Not in Claude Code, Claude Desktop, Cursor or VS Code; they sign in through the browser. Only CI and other headless setups use a personal key.

Does it work with a self-hosted Jitsu?

Yes. Use your own console host; the server is at /mcp on it.

How do I disconnect an assistant?

Open the API Keys section of your account and revoke its token; it is cut off at once.

Can the assistant test a function without breaking live data?

Yes. run_function runs the code on a sample event and saves nothing.