{
  "markdown": "# Jitbit Helpdesk MCP Server\n\nAn MCP (Model Context Protocol) server that lets AI assistants search and read support tickets from [Jitbit Helpdesk](https://www.jitbit.com/helpdesk/). Works with both SaaS and on-premise installations.\n\n[![npm version](https://img.shields.io/npm/v/jitbit-helpdesk-mcp.svg)](https://www.npmjs.com/package/jitbit-helpdesk-mcp)\n\n> ⚠️ **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](https://www.jitbit.com/docs/mcp/). 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`.\n\n## Setup\n\nTwo options:\n\n1. **Hosted HTTP endpoint** (recommended) — connect your MCP client directly to Jitbit's `/api/mcp`. Use this whenever your client supports HTTP MCP transport.\n2. **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.\n\n### Option 1: Hosted HTTP endpoint\n\n#### Claude Code\n\n```bash\nclaude mcp add --transport http jitbit-helpdesk https://yourcompany.jitbit.com/api/mcp \\\n  --header \"Authorization: Bearer your-api-token\"\n```\n\n#### Claude Desktop, Cursor, Windsurf\n\n```json\n{\n  \"mcpServers\": {\n    \"jitbit-helpdesk\": {\n      \"type\": \"http\",\n      \"url\": \"https://yourcompany.jitbit.com/api/mcp\",\n      \"headers\": {\n        \"Authorization\": \"Bearer your-api-token\"\n      }\n    }\n  }\n}\n```\n\n### Option 2: Local npm package (stdio proxy)\n\n#### Claude Code\n\n```bash\nclaude mcp add jitbit-helpdesk \\\n  -e JITBIT_URL=https://yourcompany.jitbit.com \\\n  -e JITBIT_TOKEN=your-api-token \\\n  -- npx -y jitbit-helpdesk-mcp\n```\n\n#### Claude Desktop, Cursor, Windsurf\n\nAdd to your config file:\n- Claude Desktop: `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) or `%APPDATA%\\Claude\\claude_desktop_config.json` (Windows)\n- Cursor: Settings > MCP Servers\n- Windsurf: Settings > MCP Servers\n\n```json\n{\n  \"mcpServers\": {\n    \"jitbit-helpdesk\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"jitbit-helpdesk-mcp\"],\n      \"env\": {\n        \"JITBIT_URL\": \"https://yourcompany.jitbit.com\",\n        \"JITBIT_TOKEN\": \"your-api-token\"\n      }\n    }\n  }\n}\n```\n\n### Environment Variables\n\n| Variable | Required | Description |\n|----------|----------|-------------|\n| `JITBIT_URL` | Yes | Base URL of your Jitbit instance (SaaS: `https://yourcompany.jitbit.com`, on-prem: your server URL) |\n| `JITBIT_TOKEN` | Yes | API token — see below |\n\n### Getting your API token\n\n1. Log in to your Jitbit Helpdesk\n2. Go to your **User Profile** (click your avatar in the top right)\n3. Click the **\"API Token\"** button\n4. Copy the token and use it as the `JITBIT_TOKEN` value\n\n## Tools\n\nThe 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](https://www.jitbit.com/docs/mcp/)) for the up-to-date catalog.\n\n## Development\n\n```bash\nnpm install\nnpm run build\n```\n\n## License\n\nMIT\n",
  "bytes": 3475,
  "sha": "eb64aade4f0e0f6198439f57d019315509d4796ff5b61dc094ec05997b699cd5",
  "repo_slug": "jitbit/jitbit-helpdesk-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_jitbit_jitbit_helpdesk_cf4a374c/readme"
}