Kaseya BMS MCP server
MCP server for Kaseya BMS PSA — tickets, accounts, time entries, contracts.
0 stars
Reviews
Write oneNobody has reviewed Kaseya BMS yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Kaseya BMS tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-31 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 2 days ago15/15
- Maintainer identityregistry namespace matches repository owner7/10
How Kaseya BMS compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 70/100
- higher than 35% of 48,255 servers
Release history: 2 versions in the registry since 2026-08-26, latest 2026-10-14, typically one every 49 days.
Install Kaseya BMS in Claude Code, Cursor or VS Code
claude mcp add kaseya-bms-mcp -- docker run -i --rm ghcr.io/wyre-ai/kaseya-bms-mcp:v1.1.6
What the publisher says
From the Kaseya BMS repository's README, as published. We do not edit it. Read it on GitHub
Kaseya BMS MCP Server
Model Context Protocol (MCP) server for the Kaseya BMS PSA API. Exposes tickets, accounts, contacts, contracts, time entries, the service catalog, and the knowledge base to AI assistants.
Tools
When the user omits required filters or runs a destructive action, the server uses MCP elicitation to prompt for choices or confirm.
Interactive Ticket Card (MCP Apps)
kaseyabmsgetticket renders as an interactive card in MCP Apps hosts (Claude Desktop/web) with an in-card "Add note" round-trip via kaseyabmsaddticketnote (always posted internal-only); plain-JSON behavior is unchanged in other hosts. The card is neutral by default and brandable via window.BRAND injection or MCPBRAND env vars (MCPBRANDNAME, MCPBRANDLOGOURL, MCPBRANDPRIMARYCOLOR, MCPBRANDACCENTCOLOR, MCPBRANDBG, MCPBRANDTEXT) — no rebuild needed. After editing ui/, regenerate the embedded bundle with npm run build:ui.
Configuration
Environment-variable mode (default)
Either KASEYABMSAPITOKEN OR KASEYABMSK1TOKEN is required.
Gateway mode
When deployed behind the WYRE MCP Gateway, set AUTH_MODE=gateway and the server will read credentials from per-request HTTP headers:
- X-Kaseya-BMS-Tenant-Subdomain (required)
- X-Kaseya-BMS-API-Token (or)
- X-Kaseya-BMS-K1-Token
Each request creates a fresh server instance with isolated credentials — no cross-tenant process.env pollution.
Local development
npm install
npm run build
KASEYA_BMS_TENANT_SUBDOMAIN=yourcompany \
KASEYA_BMS_API_TOKEN=... \
npm startRun as HTTP for testing:
MCP_TRANSPORT=http npm start
curl http://localhost:8080/healthDocker
docker build -t kaseya-bms-mcp .
docker run --rm -p 8080:8080 \
-e KASEYA_BMS_TENANT_SUBDOMAIN=yourcompany \
-e KASEYA_BMS_API_TOKEN=... \
kaseya-bms-mcpLicense
Apache-2.0
Nothing above is checked by us. What we check is on the safety report.
Kaseya BMS: common questions
- Is Kaseya BMS MCP server safe?
- Mostly: it is graded B (70/100). Read the Kaseya BMS safety report
- How do I install Kaseya BMS?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does Kaseya BMS need an API key?
- Yes. The registry entry asks for
KASEYA_BMS_API_TOKEN,KASEYA_BMS_K1_TOKEN. - Is Kaseya BMS maintained?
- The last commit was 6 days ago (2026-10-29). The latest release is v1.1.6.