Server data from the Official MCP Registry
MCP server for Jitbit Helpdesk: search, list, read, and reply to support tickets from AI assistants.
MCP server for Jitbit Helpdesk: search, list, read, and reply to support tickets from AI assistants.
Remote endpoints: streamable-http: https://{helpdesk_host}/api/mcp
This is a well-designed stdio proxy server that forwards MCP requests to a remote Jitbit Helpdesk endpoint. Authentication is properly required via environment variables, credentials are not hardcoded, and the code is clean with minimal attack surface. The server performs no independent operations—it purely proxies requests—which significantly reduces security concerns. Minor code quality observations exist but do not materially affect security posture. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 3 high severity). Package verification found 1 issue.
3 files analyzed · 7 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: JITBIT_URL
Environment variable: JITBIT_TOKEN
Available as Local & Remote
This plugin can run on your machine or connect to a hosted endpoint. during install.
From the project's GitHub README.
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/mcpon 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 onjitbit-helpdesk-mcp@1.x.
Two options:
/api/mcp. Use this whenever your client supports HTTP MCP transport.{JITBIT_URL}/api/mcp and adds nothing of its own.claude mcp add --transport http jitbit-helpdesk https://yourcompany.jitbit.com/api/mcp \
--header "Authorization: Bearer your-api-token"
{
"mcpServers": {
"jitbit-helpdesk": {
"type": "http",
"url": "https://yourcompany.jitbit.com/api/mcp",
"headers": {
"Authorization": "Bearer your-api-token"
}
}
}
}
claude mcp add jitbit-helpdesk \
-e JITBIT_URL=https://yourcompany.jitbit.com \
-e JITBIT_TOKEN=your-api-token \
-- npx -y jitbit-helpdesk-mcp
Add to your config file:
~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows){
"mcpServers": {
"jitbit-helpdesk": {
"command": "npx",
"args": ["-y", "jitbit-helpdesk-mcp"],
"env": {
"JITBIT_URL": "https://yourcompany.jitbit.com",
"JITBIT_TOKEN": "your-api-token"
}
}
}
}
| 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 |
JITBIT_TOKEN valueThe 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.
npm install
npm run build
MIT
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.