{
  "markdown": "# Kaseya BMS MCP Server\n\n[![Release](https://github.com/WYRE-AI/kaseya-bms-mcp/actions/workflows/release.yml/badge.svg)](https://github.com/WYRE-AI/kaseya-bms-mcp/actions/workflows/release.yml)\n[![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)\n\nModel Context Protocol (MCP) server for the Kaseya BMS PSA API.\nExposes tickets, accounts, contacts, contracts, time entries, the service\ncatalog, and the knowledge base to AI assistants.\n\n## Tools\n\n| Tool | Description |\n|------|-------------|\n| `kaseya_bms_list_tickets` | List tickets. Optional `$filter`; status pick if omitted. |\n| `kaseya_bms_get_ticket` | Get a ticket by id. |\n| `kaseya_bms_create_ticket` | Create a new ticket (destructive — confirmation required). |\n| `kaseya_bms_add_ticket_note` | Append a note to a ticket (destructive — confirmation required). |\n| `kaseya_bms_list_time_entries` | Time entries by date range (24h / 7d / 30d / custom / all). |\n| `kaseya_bms_list_accounts` | Accounts (clients). |\n| `kaseya_bms_list_contacts` | Contacts. |\n| `kaseya_bms_list_contracts` | Contracts. |\n| `kaseya_bms_list_service_catalog` | Service catalog items. |\n| `kaseya_bms_search_knowledge_base` | Knowledge base search. |\n\nWhen the user omits required filters or runs a destructive action, the server\nuses MCP elicitation to prompt for choices or confirm.\n\n## Interactive Ticket Card (MCP Apps)\n\n`kaseya_bms_get_ticket` renders as an interactive card in MCP Apps hosts\n(Claude Desktop/web) with an in-card \"Add note\" round-trip via\n`kaseya_bms_add_ticket_note` (always posted internal-only); plain-JSON\nbehavior is unchanged in other hosts. The card is neutral by default and\nbrandable via `window.__BRAND__` injection or `MCP_BRAND_*` env vars\n(`MCP_BRAND_NAME`, `MCP_BRAND_LOGO_URL`, `MCP_BRAND_PRIMARY_COLOR`,\n`MCP_BRAND_ACCENT_COLOR`, `MCP_BRAND_BG`, `MCP_BRAND_TEXT`) — no rebuild\nneeded. After editing `ui/`, regenerate the embedded bundle with\n`npm run build:ui`.\n\n## Configuration\n\n### Environment-variable mode (default)\n\n| Variable | Required | Description |\n|----------|----------|-------------|\n| `KASEYA_BMS_TENANT_SUBDOMAIN` | yes | Tenant subdomain (e.g. `yourcompany`) |\n| `KASEYA_BMS_API_TOKEN` | one of | BMS API token (secret) |\n| `KASEYA_BMS_K1_TOKEN` | one of | Kaseya One SSO token (secret) |\n| `MCP_TRANSPORT` | no | `stdio` (default) or `http` |\n| `MCP_HTTP_PORT` | no | HTTP listen port (default `8080`) |\n| `AUTH_MODE` | no | `env` (default) or `gateway` |\n\nEither `KASEYA_BMS_API_TOKEN` OR `KASEYA_BMS_K1_TOKEN` is required.\n\n### Gateway mode\n\nWhen deployed behind the WYRE MCP Gateway, set `AUTH_MODE=gateway` and the\nserver will read credentials from per-request HTTP headers:\n\n- `X-Kaseya-BMS-Tenant-Subdomain` (required)\n- `X-Kaseya-BMS-API-Token` (or)\n- `X-Kaseya-BMS-K1-Token`\n\nEach request creates a fresh server instance with isolated credentials — no\ncross-tenant `process.env` pollution.\n\n## Local development\n\n```bash\nnpm install\nnpm run build\nKASEYA_BMS_TENANT_SUBDOMAIN=yourcompany \\\n  KASEYA_BMS_API_TOKEN=... \\\n  npm start\n```\n\nRun as HTTP for testing:\n\n```bash\nMCP_TRANSPORT=http npm start\ncurl http://localhost:8080/health\n```\n\n## Docker\n\n```bash\ndocker build -t kaseya-bms-mcp .\ndocker run --rm -p 8080:8080 \\\n  -e KASEYA_BMS_TENANT_SUBDOMAIN=yourcompany \\\n  -e KASEYA_BMS_API_TOKEN=... \\\n  kaseya-bms-mcp\n```\n\n## License\n\nApache-2.0\n",
  "bytes": 3421,
  "sha": "1d83a37ca3efbb570a23867b8fdd1626cfa561f0afc77251a69ecbffa614d028",
  "repo_slug": "wyre-technology/kaseya-bms-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_wyre_technology_kaseya_bms_mcp_cf59ad99/readme"
}