Jitbit MCP Server

The Jitbit Helpdesk MCP (Model Context Protocol) server lets AI assistants search and read support tickets directly from your helpdesk. It works with both SaaS and self-hosted installations.

There are two ways to connect:

• Hosted HTTP endpoint — built into Jitbit Helpdesk. Nothing to install. Recommended for most users.
• Local npm package — jitbit-helpdesk-mcp runs on your machine over stdio. Use this with clients that don't yet support the Streamable HTTP transport.

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

Option 1: Hosted HTTP endpoint

Your Jitbit Helpdesk exposes an MCP endpoint at /api/mcp over HTTPS. Any MCP client that speaks the Streamable HTTP transport can connect directly.

• URL: https://yourcompany.jitbit.com/api/mcp
• Auth header: Authorization: Bearer <your-api-token>
• Transport: Streamable HTTP (stateless)

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

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": {
      "type": "http",
      "url": "https://yourcompany.jitbit.com/api/mcp",
      "headers": {
        "Authorization": "Bearer your-api-token"
      }
    }
  }
}

Option 2: Local npm package (stdio)

Use this if your MCP client doesn't support HTTP transport yet, or if you prefer running the server locally.

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

{
  "mcpServers": {
    "jitbit-helpdesk": {
      "command": "npx",
      "args": ["-y", "jitbit-helpdesk-mcp"],
      "env": {
        "JITBIT_URL": "https://yourcompany.jitbit.com",
        "JITBIT_TOKEN": "your-api-token"
      }
    }
  }
}

Environment Variables

Available Tools

Once configured, the MCP server exposes three read-only tools that the AI assistant can call automatically.

Search Tickets

Tool name: jitbit_search_tickets

Search tickets by keyword or phrase. Matches against ticket subjects and bodies.

Parameters:

• query (string, required) — search query (minimum 3 characters)
• limit (number, default 25) — max results (1-100)

Example use: "Search for tickets about password reset" — the AI calls jitbit_search_tickets with query "password reset" and returns matching tickets.

List Tickets

Tool name: jitbit_list_tickets

List and filter tickets by mode and status.

Parameters:

• mode (string, optional) — "all", "unanswered", "unclosed", "unassigned", or "handledbyme"
• status (string, optional) — filter by ticket status name
• limit (number, default 25) — max results (1-100)
• offset (number, default 0) — pagination offset

Example use: "Show me unanswered tickets" — the AI calls jitbit_list_tickets with mode "unanswered".

Get Ticket

Tool name: jitbit_get_ticket

Get a single ticket with its full conversation thread, including subject, body, status, priority, category, tags, and all comments.

Parameters:

• ticketId (number, required) — the ticket ID

Example use: "Show me ticket #4521" — the AI calls jitbit_get_ticket with ticketId 4521 and returns the full ticket details and conversation history.

What You Can Do With It

Once connected, you can ask your AI assistant things like:

• "Search for tickets about SSO login issues"
• "Show me all unanswered tickets"
• "Get the details of ticket #1234"
• "Find tickets related to billing"
• "List unclosed tickets and summarize them"

The AI assistant handles tool selection automatically — just ask in natural language.

Security

• The MCP server is read-only — it cannot create, modify, or delete tickets
• All calls use your personal API token, so the AI sees only what you have access to
• For the hosted endpoint, the token is sent as a Bearer header over HTTPS
• For the npm package, the token is stored locally in your MCP configuration and is never sent to third parties