Log inSubmit server
Jitbit Helpdesk logo

Jitbit Helpdesk

Search and read Jitbit Helpdesk tickets through hosted HTTP MCP or a local stdio proxy.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Jitbit Helpdesk

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "jitbit-helpdesk": {
      "command": "npx",
      "args": [
        "-y",
        "jitbit-helpdesk-mcp"
      ],
      "env": {
        "JITBIT_URL": "YOUR_VALUE_HERE",
        "JITBIT_TOKEN": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

We couldn’t confirm it starts correctly

We ran the install command but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.

npx -y jitbit-helpdesk-mcp

No response to initialize.

This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 12d ago.

Overview

The jitbit-helpdesk MCP server connects AI assistants to Jitbit Helpdesk installations and exposes the tools advertised by the instance. It supports both SaaS and on-premise deployments through Jitbit's `/api/mcp` endpoint. Use the hosted HTTP endpoint with clients that support remote MCP; the npm package provides a stdio proxy for clients that do not. Jitbit version 11.21 or later is required for the current endpoint and 2.x package.

Use cases

  • Search support tickets from an AI assistant
  • List tickets in a Jitbit Helpdesk instance
  • Read ticket details during support analysis
  • Connect an stdio-only MCP client to Jitbit

Key features

  • Searches Jitbit support tickets
  • Lists tickets
  • Reads ticket details
  • Supports SaaS and on-premise Jitbit
  • Provides HTTP MCP and stdio proxy options
  • Uses Jitbit API token authentication

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

10/10 checks healthy over the last 51d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 6d ago via OSV.dev · jitbit-helpdesk-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars3Stargazers on the source repository.
npm downloads154Package downloads in the last 30 days.
Last commit6mo agoMost recent push to the default branch.
Install checkInconclusiveDidn't respond in our test window — often a slow first install.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Jitbit Helpdesk works

What jitbit-helpdesk does

The jitbit-helpdesk MCP server gives AI assistants access to Jitbit Helpdesk ticket data. It is intended for searching, listing, and reading support tickets rather than for adding a separate ticket-management API. The available tool set comes from the connected Jitbit instance, so the exact catalog can change as Jitbit adds capabilities.

Both Jitbit SaaS and on-premise installations are supported. The current setup requires Jitbit 11.21 or later, which includes the built-in MCP endpoint at /api/mcp.

How it works

The preferred connection method is direct HTTP MCP. An MCP client sends requests to the Jitbit instance's /api/mcp endpoint and authenticates with an API token in the Authorization header.

For clients that only support stdio transport, the npm package acts as a local forwarding process. The jitbit-helpdesk package sends each request to {JITBIT_URL}/api/mcp; it does not implement an independent ticket API or add tools beyond those provided by Jitbit. In version 2.x, this package is therefore a thin stdio proxy to the same endpoint used by the hosted option.

This architecture keeps the tool catalog tied to the connected Jitbit installation. Check the MCP client's tool listing or Jitbit's MCP documentation for the current set of advertised tools.

Setup and configuration

Choose the hosted endpoint when the MCP client supports HTTP transport. Set the endpoint to your Jitbit base URL followed by /api/mcp, and provide an API token as a bearer token. Claude Code, Claude Desktop, Cursor, and Windsurf are shown in the project instructions with hosted HTTP configuration examples.

Use the local npm package when the client requires stdio. Install or run it with npx -y jitbit-helpdesk-mcp, and provide these environment variables:

  • JITBIT_URL: the base URL of the SaaS or on-premise Jitbit installation.
  • JITBIT_TOKEN: an API token from the Jitbit user profile.

To create the token, sign in to Jitbit Helpdesk, open the user profile, select the API Token control, and copy the resulting value. The package also requires Jitbit 11.21 or later. Older on-premise installations should remain on jitbit-helpdesk-mcp@1.x, according to the project instructions.

Tools and capabilities

The connected instance typically advertises tools for:

  • Searching support tickets
  • Listing tickets
  • Reading ticket details

These are the documented typical capabilities, not a fixed local implementation. Later Jitbit releases may expose additional tools through /api/mcp, and the MCP client should be used to inspect what is available for a particular installation.

Limitations and notes

The local package does not provide a separate implementation of Jitbit operations; it forwards MCP traffic to the remote endpoint. Direct HTTP is preferred when available because it avoids the local proxy and follows the endpoint shipped with Jitbit.

No ticket creation, update, deletion, or other write operation is documented here, so those capabilities should not be assumed. Authentication depends on a valid Jitbit API token and the permissions associated with that token.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Jitbit Helpdesk

jitbit-helpdesk is an MCP server that connects AI assistants to Jitbit Helpdesk SaaS or on-premise installations. Its typical tools search, list, and read support tickets, while the connected Jitbit instance controls the available catalog. It uses Jitbit’s `/api/mcp` endpoint and requires Jitbit 11.21 or later.

Use the hosted `/api/mcp` endpoint when your client supports HTTP, or run `npx -y jitbit-helpdesk-mcp` for a stdio-only client. The local option requires `JITBIT_URL` and `JITBIT_TOKEN`.

Yes, jitbit-helpdesk works with Cursor through either the hosted HTTP configuration or the local stdio configuration. The README provides setup examples for both options in Cursor's MCP server settings.

The current endpoint and 2.x package require Jitbit 11.21 or later. Older on-premise installations should use `jitbit-helpdesk-mcp@1.x` according to the project instructions.

Related MCP servers

All in Support & Service Management All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewJitbit Helpdesk AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/jitbit-helpdesk?style=directory)](https://allmcps.com/mcp/jitbit-helpdesk)
HTML Embed
<a href="https://allmcps.com/mcp/jitbit-helpdesk"><img src="https://allmcps.com/api/badge/jitbit-helpdesk?style=directory" alt="Jitbit Helpdesk on AllMCPs" /></a>