jitbit_search_ticketsLABSCO SUMMARY
Read the whole ticket history; the only thing it writes is a comment.
Everything except adding a comment is read-only — it cannot create, delete or otherwise modify tickets — and a comment it does post is attributed to the token's owner. Calls run under your personal token, so the assistant sees what you see and nothing past it.
What it is
A server for Jitbit Helpdesk that lets an assistant search tickets and knowledge base articles, read a full ticket thread, and post a reply. It works against both the hosted product and a self-hosted installation.
What you get
- Ticket search by keyword or phrase across subjects and bodies
- Ticket lists filtered by mode — unanswered, unclosed, unassigned, handled by you — and by status, with pagination
- One ticket with its whole conversation: subject, body, status, priority, category, tags and every comment
- Knowledge base search across article subjects, bodies and tags, returning only articles you are allowed to see
- A single article with its full text, category, tags and dates
- A reply posted to a ticket, either visible to the customer or as an internal note for technicians only
- Two ways in: the endpoint built into Jitbit over Streamable HTTP, or the npm package for clients that only speak stdio
Requirements
An API token from your Jitbit user profile, and your instance URL. The built-in endpoint needs no install and reaches on-premise installations from v11.21 onward; the local package takes JITBIT_URL and JITBIT_TOKEN.
Setup effort
One command plus a key — claude mcp add --transport http jitbit-helpdesk https://<YOUR_COMPANY>.jitbit.com/api/mcp --header "Authorization: Bearer <YOUR_JITBIT_TOKEN>"
USE CASES
01
Clearing the unanswered queue
List tickets in unanswered mode and summarise them before deciding what to pick up.
02
Answering with something you already documented
Search the knowledge base, read the article, and draft the reply from it in the same conversation.
03
Catching up on one ticket
Pull it by id and get the full thread — status, priority, category, tags and every comment.
04
Checking whether a problem has come up before
Search tickets by phrase across subjects and bodies.
05
Flagging something for another team
Add an internal note visible only to technicians instead of replying to the customer.
6 tools
Listed in project docs. Your client may show a different list.
jitbit_list_ticketsjitbit_get_ticketjitbit_search_kbjitbit_get_kb_articlejitbit_add_commentBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Requires
- A client that can reach a remote MCP server over HTTP
- JITBIT_TOKEN in your environment
- JITBIT_URL in your environment
INSTALLATION
Connect your client
Server setup
claude mcp add
Claude Code — HTTP
TERMINAL
claude mcp add --transport http jitbit-helpdesk https://<YOUR_COMPANY>.jitbit.com/api/mcp --header "Authorization: Bearer <YOUR_JITBIT_TOKEN>"Hosted endpoint
ENDPOINT URL
https://<YOUR_COMPANY>.jitbit.com/api/mcpAdd this hosted endpoint to your MCP client using the credentials listed under Requirements.
MCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"jitbit-helpdesk": {
"type": "http",
"url": "https://<YOUR_COMPANY>.jitbit.com/api/mcp",
"headers": {
"Authorization": "Bearer <YOUR_JITBIT_TOKEN>"
}
}
}
}Windsurf
WINDSURF · JSON
{
"mcpServers": {
"jitbit-helpdesk": {
"type": "http",
"serverUrl": "https://<YOUR_COMPANY>.jitbit.com/api/mcp",
"headers": {
"Authorization": "Bearer <YOUR_JITBIT_TOKEN>"
}
}
}
}Claude Code — npx
CLAUDE CODE — NPX · TERMINAL
claude mcp add jitbit-helpdesk -e JITBIT_URL=https://<YOUR_COMPANY>.jitbit.com -e JITBIT_TOKEN=<YOUR_JITBIT_TOKEN> -- npx -y jitbit-helpdesk-mcpClaude Desktop — npx, Cursor — npx, Windsurf — npx
JSON
{
"mcpServers": {
"jitbit-helpdesk": {
"command": "npx",
"args": [
"-y",
"jitbit-helpdesk-mcp"
],
"env": {
"JITBIT_URL": "https://<YOUR_COMPANY>.jitbit.com",
"JITBIT_TOKEN": "<YOUR_JITBIT_TOKEN>"
}
}
}
}
