English Français العربية

Jitbit Helpdesk

Official registry Search and web

MCP server for Jitbit Helpdesk: search, list, read, and reply to support tickets from AI assistants.

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http jitbit-helpdesk 'https://{helpdesk_host}/api/mcp' --header 'Authorization: <Bearer API token from your Jitbit user profile, for example Bearer your-api-token>'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "jitbit-helpdesk": {
            "type": "http",
            "url": "https://{helpdesk_host}/api/mcp",
            "headers": {
                "Authorization": "<Bearer API token from your Jitbit user profile, for example Bearer your-api-token>"
            }
        }
    }
}
NPM package jitbit-helpdesk-mcp
Claude Code 
claude mcp add jitbit-helpdesk -e 'JITBIT_URL=<JITBIT_URL>' -e 'JITBIT_TOKEN=<your jitbit_token>' -- npx -y jitbit-helpdesk-mcp@2.0.0
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "jitbit-helpdesk": {
            "command": "npx",
            "args": [
                "-y",
                "jitbit-helpdesk-mcp@2.0.0"
            ],
            "env": {
                "JITBIT_URL": "<JITBIT_URL>",
                "JITBIT_TOKEN": "<your jitbit_token>"
            }
        }
    }
}

Environment variables

  • JITBIT_URL required Base URL of your Jitbit Helpdesk instance
  • JITBIT_TOKEN required secret API token from your Jitbit user profile

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Jitbit Helpdesk MCP Server
  2. Setup
  3. Tools
  4. Development
  5. License

Jitbit Helpdesk MCP Server

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/mcp on 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 on jitbit-helpdesk-mcp@1.x.

Setup

Two options:

  1. Hosted HTTP endpoint (recommended) — connect your MCP client directly to Jitbit's /api/mcp. Use this whenever your client supports HTTP MCP transport.
  2. Local npm package (stdio proxy) — this repo. Use it when your MCP client only supports stdio transport. It forwards every request to {JITBIT_URL}/api/mcp and adds nothing of its own.
Option 1: Hosted HTTP endpoint
Claude Code
claude mcp add --transport http jitbit-helpdesk https://yourcompany.jitbit.com/api/mcp \
  --header "Authorization: Bearer your-api-token"
Claude Desktop, Cursor, Windsurf
{
  "mcpServers": {
    "jitbit-helpdesk": {
      "type": "http",
      "url": "https://yourcompany.jitbit.com/api/mcp",
      "headers": {
        "Authorization": "Bearer your-api-token"
      }
    }
  }
}
Option 2: Local npm package (stdio proxy)
Claude Code
claude mcp add jitbit-helpdesk \
  -e JITBIT_URL=https://yourcompany.jitbit.com \
  -e JITBIT_TOKEN=your-api-token \
  -- npx -y jitbit-helpdesk-mcp
Claude Desktop, Cursor, Windsurf

Add to your config file:

  • Claude Desktop: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows)
  • Cursor: Settings > MCP Servers
  • Windsurf: Settings > MCP Servers
{
  "mcpServers": {
    "jitbit-helpdesk": {
      "command": "npx",
      "args": ["-y", "jitbit-helpdesk-mcp"],
      "env": {
        "JITBIT_URL": "https://yourcompany.jitbit.com",
        "JITBIT_TOKEN": "your-api-token"
      }
    }
  }
}
Environment Variables
VariableRequiredDescription
JITBIT_URLYesBase URL of your Jitbit instance (SaaS: https://yourcompany.jitbit.com, on-prem: your server URL)
JITBIT_TOKENYesAPI token — see below
Getting your API token
  1. Log in to your Jitbit Helpdesk
  2. Go to your User Profile (click your avatar in the top right)
  3. Click the "API Token" button
  4. Copy the token and use it as the JITBIT_TOKEN value

Tools

The 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.

Development

npm install
npm run build

License

MIT

Frequently asked questions

What is Jitbit Helpdesk?

MCP server for Jitbit Helpdesk: search, list, read, and reply to support tickets from AI assistants.

How do I install Jitbit Helpdesk?

It runs as a remote server. In Claude Code: claude mcp add --transport http jitbit-helpdesk 'https://{helpdesk_host}/api/mcp' --header 'Authorization: <Bearer API token from your Jitbit user profile, for example Bearer your-api-token>'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Jitbit Helpdesk need an API key?

Yes. It expects JITBIT_URL, JITBIT_TOKEN, Authorization, which you set in its configuration.

Is Jitbit Helpdesk open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Jitbit Helpdesk?

It is published by jitbit. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.