Kaseya BMS MCP Server
by wyre-aiio.github.WYRE-AI/kaseya-bms-mcpv1.1.5
MCP server for Kaseya BMS PSA — tickets, accounts, time entries, contracts.
context tax
queued
security
queued
cold start
queued
freshness
Active4d ago
Install Kaseya BMS MCP server
Install in Claude Code
claude mcp add kaseya-bms-wyre-ai -e KASEYA_BMS_TENANT_SUBDOMAIN='<kaseya-bms-tenant-subdomain>' -e KASEYA_BMS_API_TOKEN='<kaseya-bms-api-token>' -e KASEYA_BMS_K1_TOKEN='<kaseya-bms-k1-token>' -- docker run -i --rm -e KASEYA_BMS_TENANT_SUBDOMAIN -e KASEYA_BMS_API_TOKEN -e KASEYA_BMS_K1_TOKEN ghcr.io/wyre-ai/kaseya-bms-mcp:v1.1.5Install in Cursor
{
"mcpServers": {
"kaseya-bms-wyre-ai": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"KASEYA_BMS_TENANT_SUBDOMAIN",
"-e",
"KASEYA_BMS_API_TOKEN",
"-e",
"KASEYA_BMS_K1_TOKEN",
"ghcr.io/wyre-ai/kaseya-bms-mcp:v1.1.5"
],
"env": {
"KASEYA_BMS_TENANT_SUBDOMAIN": "<kaseya-bms-tenant-subdomain>",
"KASEYA_BMS_API_TOKEN": "<kaseya-bms-api-token>",
"KASEYA_BMS_K1_TOKEN": "<kaseya-bms-k1-token>"
}
}
}
}Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project).
Install in Claude Desktop
{
"mcpServers": {
"kaseya-bms-wyre-ai": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"KASEYA_BMS_TENANT_SUBDOMAIN",
"-e",
"KASEYA_BMS_API_TOKEN",
"-e",
"KASEYA_BMS_K1_TOKEN",
"ghcr.io/wyre-ai/kaseya-bms-mcp:v1.1.5"
],
"env": {
"KASEYA_BMS_TENANT_SUBDOMAIN": "<kaseya-bms-tenant-subdomain>",
"KASEYA_BMS_API_TOKEN": "<kaseya-bms-api-token>",
"KASEYA_BMS_K1_TOKEN": "<kaseya-bms-k1-token>"
}
}
}
}Settings → Developer → Edit Config (claude_desktop_config.json), then restart.
Install in VS Code
{
"servers": {
"kaseya-bms-wyre-ai": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"KASEYA_BMS_TENANT_SUBDOMAIN",
"-e",
"KASEYA_BMS_API_TOKEN",
"-e",
"KASEYA_BMS_K1_TOKEN",
"ghcr.io/wyre-ai/kaseya-bms-mcp:v1.1.5"
],
"env": {
"KASEYA_BMS_TENANT_SUBDOMAIN": "<kaseya-bms-tenant-subdomain>",
"KASEYA_BMS_API_TOKEN": "<kaseya-bms-api-token>",
"KASEYA_BMS_K1_TOKEN": "<kaseya-bms-k1-token>"
}
}
}
}Add to .vscode/mcp.json in your workspace.
Install in Windsurf
{
"mcpServers": {
"kaseya-bms-wyre-ai": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"KASEYA_BMS_TENANT_SUBDOMAIN",
"-e",
"KASEYA_BMS_API_TOKEN",
"-e",
"KASEYA_BMS_K1_TOKEN",
"ghcr.io/wyre-ai/kaseya-bms-mcp:v1.1.5"
],
"env": {
"KASEYA_BMS_TENANT_SUBDOMAIN": "<kaseya-bms-tenant-subdomain>",
"KASEYA_BMS_API_TOKEN": "<kaseya-bms-api-token>",
"KASEYA_BMS_K1_TOKEN": "<kaseya-bms-k1-token>"
}
}
}
}Add to ~/.codeium/windsurf/mcp_config.json.
Configuration
| Variable | Required | Secret | Description |
|---|---|---|---|
| KASEYA_BMS_TENANT_SUBDOMAIN | yes | — | Tenant subdomain (e.g. 'yourcompany' for yourcompany.bms.kaseya.com) |
| KASEYA_BMS_API_TOKEN | — | yes | BMS API token (omit if using Kaseya One token) |
| KASEYA_BMS_K1_TOKEN | — | yes | Kaseya One SSO token (alternative to API token) |
| MCP_TRANSPORT | — | — | Transport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting. |
| AUTH_MODE | — | — | Credential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway. |
| LOG_LEVEL | — | — | Log verbosity: debug, info, warn, error |
Freshness
Active — last maintenance signal 4d ago. The newest of the signals below sets the band.
Last commit (default branch)
2026-10-05 · 4d ago · GitHub
Latest release
2026-08-25 · 45d ago · GitHub · v1.1.5
Package published
no data · npm/PyPI
Registry entry updated
2026-08-26 · 45d ago · official registry · v1.1.5
FAQ
›How do I install the Kaseya BMS MCP server in Claude Code?
Run: claude mcp add kaseya-bms-wyre-ai -e KASEYA_BMS_TENANT_SUBDOMAIN='<kaseya-bms-tenant-subdomain>' -e KASEYA_BMS_API_TOKEN='<kaseya-bms-api-token>' -e KASEYA_BMS_K1_TOKEN='<kaseya-bms-k1-token>' -- docker run -i --rm -e KASEYA_BMS_TENANT_SUBDOMAIN -e KASEYA_BMS_API_TOKEN -e KASEYA_BMS_K1_TOKEN ghcr.io/wyre-ai/kaseya-bms-mcp:v1.1.5. For Cursor, VS Code, Claude Desktop and Windsurf, use the install tabs above.
›Does Kaseya BMS require an API key?
Yes. It expects KASEYA_BMS_TENANT_SUBDOMAIN, KASEYA_BMS_API_TOKEN, KASEYA_BMS_K1_TOKEN, of which 2 are secrets.
›Can I use Kaseya BMS as a remote (hosted) MCP server?
No hosted endpoint is published; it runs locally over stdio.
›Is Kaseya BMS in the official MCP registry?
Yes, as io.github.WYRE-AI/kaseya-bms-mcp.
Alternatives to Kaseya BMS
Other project management MCP servers.