Jitbit Helpdesk

io.github.jitbitPublished by GitHub account jitbitv2.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableCommunication & CollaborationBusiness & Commerce

Overview

AI-generated overview

MCP server for Jitbit Helpdesk that lets an AI assistant search, list and read support tickets, and reply to them, from the assistant.

What you can do
Search and list support tickets in a Jitbit Helpdesk instance, with filtering by the instance's own tool set. Read individual tickets and their details. Reply to tickets from the assistant. The tool catalog is whatever the connected Jitbit instance advertises at its MCP endpoint, so it can grow with Jitbit releases.
When to use it
Useful when support agents or helpdesk staff want an assistant to look up, summarize or answer tickets without switching to the Jitbit web interface. Prefer the hosted HTTP endpoint for clients that support remote MCP; the npm package is for stdio-only clients.
Requirements
A Jitbit Helpdesk instance (SaaS or on-premise) running version 11.21 or later. Either a remote HTTP endpoint at the instance's /api/mcp path with an Authorization bearer header, or the npm package jitbit-helpdesk-mcp run locally via npx with JITBIT_URL and JITBIT_TOKEN set. An API token from the user's Jitbit profile. Network access to the instance.
Before you install
Requires an API token (JITBIT_TOKEN or the Authorization bearer header) that grants access to helpdesk data; treat it as a secret. The assistant can reply to tickets, which sends messages to customers, so review before allowing writes. Ticket content is sent to the AI assistant and its model provider. Older on-premise versions below 11.21 need the 1.x package.

Installation

In SourceWeft

  1. Open Jitbit Helpdesk in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Follow the launch instructions in the repository.

README

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.

[npm version]

⚠️ 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 [email protected].

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
bash
claude mcp add --transport http jitbit-helpdesk https://yourcompany.jitbit.com/api/mcp \  --header "Authorization: Bearer your-api-token"
Claude Desktop, Cursor, Windsurf
json
{  "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
bash
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
json
{  "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

bash
npm installnpm run build

License

MIT

Source: README.md at commit b3dfa22

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v2.0.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts