Jitbit Helpdesk

Name: Jitbit Helpdesk
Author: jitbit

by jitbitversion 2.0.0i★ –iComputer or cloud

Registry nameio.github.jitbit/jitbit-helpdesk

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Computer or cloud
Transport: stdio, Streamable HTTP
Category: Search & AI memory
You need to fill in: JITBIT_URL, JITBIT_TOKEN, Authorization

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on the maker’s server: what you ask it goes through their server.
You fill in yourself: JITBIT_URL, JITBIT_TOKEN, Authorization

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

Runs in the cloudNothing to install; it connects over the internet
npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Or run it on your computer

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

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

Run this in your terminal

claude mcp add --transport http jitbit-helpdesk 'https://{helpdesk_host}/api/mcp' --header 'Authorization: your-value'

Or run it on your computer

claude mcp add jitbit-helpdesk --env JITBIT_URL=your-value --env JITBIT_TOKEN=your-value -- npx -y jitbit-helpdesk-mcp

Fill in the empty values before running it.

The address contains {…} parts that only you know (such as your account), so copy it and fill them in.

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "jitbit-helpdesk": {
      "url": "https://{helpdesk_host}/api/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Or run it on your computer

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

The address contains {…} parts that only you know (such as your account), so copy it and fill them in.

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "jitbit-helpdesk": {
      "type": "http",
      "url": "https://{helpdesk_host}/api/mcp",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

Or run it on your computer

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "jitbit-helpdesk": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "jitbit-helpdesk-mcp"
      ],
      "env": {
        "JITBIT_URL": "your-value",
        "JITBIT_TOKEN": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

JITBIT_URL required env
Base URL of your Jitbit Helpdesk instance
JITBIT_TOKEN secret required env
API token from your Jitbit user profile
Authorization secret required HTTP header
Bearer API token from your Jitbit user profile, for example Bearer your-api-token

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account jitbit, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
The address needs your own account values, so we cannot check it for you
– Not applicable
Sign-in with OAuth
The address needs your own account values, so we cannot check it for you
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Search & AI memoryi

More stars than 0% of the other 7229 servers in this category
Published to the registry more recently than 15% of the other 7229 servers in this category
Basic checks equal to or better than 100% of the other 7229 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Jitbit Helpdesk safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: JITBIT_URL, JITBIT_TOKEN, Authorization

Does it run on my computer or in the cloud?

Either way works: install it on your computer or connect to the cloud version.

Is it still maintained?

The GitHub repo last changed –, and the latest version (2.0.0) reached the registry 5 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated 3 days ago

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 20 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated 44 days ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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:

Hosted HTTP endpoint (recommended) — connect your MCP client directly to Jitbit's /api/mcp. Use this whenever your client supports HTTP MCP transport.
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

Variable	Required	Description
`JITBIT_URL`	Yes	Base URL of your Jitbit instance (SaaS: `https://yourcompany.jitbit.com`, on-prem: your server URL)
`JITBIT_TOKEN`	Yes	API token — see below

Getting your API token

Log in to your Jitbit Helpdesk
Go to your User Profile (click your avatar in the top right)
Click the "API Token" button
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

Jitbit Helpdesk

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Or run it on your computer

Or run it on your computer

Or run it on your computer

Or run it on your computer

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

Jitbit Helpdesk MCP Server

Setup

Option 1: Hosted HTTP endpoint

Claude Code

Claude Desktop, Cursor, Windsurf

Option 2: Local npm package (stdio proxy)

Claude Code

Claude Desktop, Cursor, Windsurf

Environment Variables

Getting your API token

Tools

Development

License