# jitbit-helpdesk [Health: Active]

**Category:** 🎧 Support & Service Management  
**Repository:** https://github.com/jitbit/jitbit-helpdesk-mcp  
**GitHub Stars:** 3  
**npm Downloads (last month):** 154  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/jitbit-helpdesk

## Description
MCP server for Jitbit Helpdesk — search and read support tickets from AI assistants

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "jitbit-helpdesk": {
    "command": "npx",
    "args": ["-y","jitbit-helpdesk-mcp"],
    "env": {
      "JITBIT_URL": "",
      "JITBIT_TOKEN": ""
    }
  }
}
```

**Requires environment variables:** `JITBIT_URL`, `JITBIT_TOKEN` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

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

_Full upstream README: https://allmcps.com/mcp/jitbit-helpdesk/readme_