Does Jitsu have an MCP server?

Yes Official

Jitsu maintains an official MCP server.

Verified 2026-09-29 against vendor docs
Access
Remote server
Endpoint
https://use.jitsu.com/mcp
Repository
jitsucom/jitsu
Maintainer
Jitsu
License
MIT
Language
TypeScript
Stars
5.1k
Last commit
today
What it does
Jitsu is an open-source Segment alternative. Fully-scriptable data ingestion engine for modern data teams. Set-up a real-time data pipeline in minutes, not days
— how jitsucom/jitsu describes itself

Project site: jitsu.com

The receipts
Vendor-hosted https://use.jitsu.com/mcp

A remote server run by Jitsu itself — nothing to install. Documented at jitsu.com.

Official repository jitsucom/jitsu

Jitsu is an open-source Segment alternative. Fully-scriptable data ingestion engine for modern data teams. Set-up a real-time data pipeline in minutes, not days

★ 5.1k pushed 2026-09-29 MIT Active
Connect it

Hosted by the vendor — no install, connect over HTTP with OAuth or a token.

Add it from the terminal, then restart your session:

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

Add --scope user to make it available in every project.

Setup sponsor · open Put your product right here, under the setup steps of all 645 verdict pages. One sponsor at a time. $149 first month, then $399/mo →
Questions
Does Jitsu have an official MCP server?

Yes. Jitsu maintains an official MCP server, hosted at https://use.jitsu.com/mcp. The source lives at jitsucom/jitsu on GitHub.

How do I connect Jitsu to Claude?

Add https://use.jitsu.com/mcp as a custom connector under Settings → Connectors in Claude Desktop or claude.ai, or run "claude mcp add --transport http jitsu https://use.jitsu.com/mcp" in Claude Code.

Do I need to install anything to use the Jitsu MCP server?

No. It is a remote server hosted by Jitsu, so your MCP client connects to it over HTTP. You authenticate with the vendor rather than installing a package.

How is this verdict verified?

Published to the MCP Registry under Jitsu's verified namespace com.jitsu; the OAuth endpoint use.jitsu.com/mcp answers MCP initialize (401) and is documented at jitsu.com/docs/mcp, with the server code in the jitsucom/jitsu repo (webapps/console/lib/server/mcp-server). GitHub metadata is refreshed every six hours.

How we know

Published to the MCP Registry under Jitsu's verified namespace com.jitsu; the OAuth endpoint use.jitsu.com/mcp answers MCP initialize (401) and is documented at jitsu.com/docs/mcp, with the server code in the jitsucom/jitsu repo (webapps/console/lib/server/mcp-server).

  • github data refreshed 2026-09-29, then every 6 hours
  • vendor docs verified on 2026-09-29

Spotted something out of date? Tell us — corrections ship same-day.

Also in Data Platforms

See all Data Platforms servers →