The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Jitbit Helpdesk listing page.
An MCP (Model Context Protocol) server that lets AI assistants search and read support tickets from Jitbit Helpdesk. Works with both SaaS and on-premise installations.
⚠️ Use the hosted HTTP endpoint when possible. Jitbit ships a built-in HTTP MCP endpoint at
/api/mcpon all SaaS and on-premise installs running version 11.21 or later. That is the preferred way to connect AI assistants to Jitbit — no local install, always in sync with Jitbit releases. See the Jitbit MCP docs. Starting with 2.x, this npm package is a thin stdio proxy to that same endpoint, for clients that don't yet support remote HTTP MCP servers. Jitbit 11.21 or later is required. If you're on an older on-premise version, stay onjitbit-helpdesk-mcp@1.x.
Two options:
/api/mcp. Use this whenever your client supports HTTP MCP transport.{JITBIT_URL}/api/mcp and adds nothing of its own.Add to your config file:
~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows)| Variable | Required | Description |
|---|---|---|
JITBIT_URL | Yes | Base URL of your Jitbit instance (SaaS: https://yourcompany.jitbit.com, on-prem: your server URL) |
JITBIT_TOKEN | Yes | API token — see below |
JITBIT_TOKEN valueThe proxy exposes whatever tools the connected Jitbit instance advertises at /api/mcp — typically ticket search, list, and read, plus anything Jitbit adds in later releases. Use your MCP client's tool listing (or the Jitbit MCP docs) for the up-to-date catalog.
MIT