Connects Claude to Jitbit Helpdesk to search and read support tickets directly from the AI assistant. Jitbit ships a native HTTP MCP endpoint at `/api/mcp` starting with version 11.21, and that's the recommended way to connect. This npm package is a stdio proxy for clients that don't yet support HTTP transport. It forwards requests to your Jitbit instance with your API token. You'll typically use it to let Claude pull ticket details, search by keyword or ticket number, and list recent issues without switching to the helpdesk UI. Works with both SaaS and on-premise installations running 11.21 or later.
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.claude mcp add --transport http jitbit-helpdesk https://yourcompany.jitbit.com/api/mcp \
--header "Authorization: Bearer your-api-token"
{
"mcpServers": {
"jitbit-helpdesk": {
"type": "http",
"url": "https://yourcompany.jitbit.com/api/mcp",
"headers": {
"Authorization": "Bearer your-api-token"
}
}
}
}
claude mcp add jitbit-helpdesk \
-e JITBIT_URL=https://yourcompany.jitbit.com \
-e JITBIT_TOKEN=your-api-token \
-- npx -y jitbit-helpdesk-mcp
Add to your config file:
~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows){
"mcpServers": {
"jitbit-helpdesk": {
"command": "npx",
"args": ["-y", "jitbit-helpdesk-mcp"],
"env": {
"JITBIT_URL": "https://yourcompany.jitbit.com",
"JITBIT_TOKEN": "your-api-token"
}
}
}
}
| 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.
npm install
npm run build
MIT
JITBIT_URL*Base URL of your Jitbit Helpdesk instance
JITBIT_TOKEN*secretAPI token from your Jitbit user profile
com.mcparmory/google-search
io.github.pipeworx-io/brave-search
marcopesani/mcp-server-serper
brave/brave-search-mcp-server
com.mcparmory/google-search-console
acamolese/google-search-console-mcp