Kaseya BMS
MCP server for Kaseya BMS PSA — tickets, accounts, time entries, contracts.
- Pricing
- Open source
- Runs
- Locally
- Version
- 1.1.4
- Listing updated
- 6 days ago
About Kaseya BMS
Kaseya BMS is an open-source MCP server. It runs locally on your machine and is started by your AI client.
Install
Run in a terminal
claude mcp add kaseya-bms-mcp --env KASEYA_BMS_TENANT_SUBDOMAIN='<KASEYA_BMS_TENANT_SUBDOMAIN>' --env KASEYA_BMS_API_TOKEN='<KASEYA_BMS_API_TOKEN>' --env 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-technology/kaseya-bms-mcp:v1.1.4Add to claude_desktop_config.json
{
"mcpServers": {
"kaseya-bms-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"KASEYA_BMS_TENANT_SUBDOMAIN",
"-e",
"KASEYA_BMS_API_TOKEN",
"-e",
"KASEYA_BMS_K1_TOKEN",
"ghcr.io/wyre-technology/kaseya-bms-mcp:v1.1.4"
],
"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
{
"mcpServers": {
"kaseya-bms-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"KASEYA_BMS_TENANT_SUBDOMAIN",
"-e",
"KASEYA_BMS_API_TOKEN",
"-e",
"KASEYA_BMS_K1_TOKEN",
"ghcr.io/wyre-technology/kaseya-bms-mcp:v1.1.4"
],
"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
{
"servers": {
"kaseya-bms-mcp": {
"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-technology/kaseya-bms-mcp:v1.1.4"
],
"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
{
"mcpServers": {
"kaseya-bms-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"KASEYA_BMS_TENANT_SUBDOMAIN",
"-e",
"KASEYA_BMS_API_TOKEN",
"-e",
"KASEYA_BMS_K1_TOKEN",
"ghcr.io/wyre-technology/kaseya-bms-mcp:v1.1.4"
],
"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 your client's MCP settings (most use this shape)
{
"mcpServers": {
"kaseya-bms-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"KASEYA_BMS_TENANT_SUBDOMAIN",
"-e",
"KASEYA_BMS_API_TOKEN",
"-e",
"KASEYA_BMS_K1_TOKEN",
"ghcr.io/wyre-technology/kaseya-bms-mcp:v1.1.4"
],
"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>"
}
}
}
}Using several servers? Build one config file with the MCP config generator.
Configuration
KASEYA_BMS_TENANT_SUBDOMAINTenant subdomain (e.g. 'yourcompany' for yourcompany.bms.kaseya.com)RequiredKASEYA_BMS_API_TOKENBMS API token (omit if using Kaseya One token)KASEYA_BMS_K1_TOKENKaseya One SSO token (alternative to API token)MCP_TRANSPORTTransport mode for the server. Set to 'stdio' for local CLI use; the image defaults to 'http' for gateway hosting.AUTH_MODECredential source: 'env' reads vars locally, 'gateway' expects header injection from the WYRE MCP Gateway.LOG_LEVELLog verbosity: debug, info, warn, error
Pricing
Open source
Kaseya BMS FAQ
Is Kaseya BMS free?
Yes. Kaseya BMS is open source, so you can use and self-host it for free.
How do I add Kaseya BMS to Claude Code?
Run this command in your terminal: claude mcp add kaseya-bms-mcp --env KASEYA_BMS_TENANT_SUBDOMAIN='<KASEYA_BMS_TENANT_SUBDOMAIN>' --env KASEYA_BMS_API_TOKEN='<KASEYA_BMS_API_TOKEN>' --env 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-technology/kaseya-bms-mcp:v1.1.4
Where this comes from
- Description: from the official MCP Registry entry.
- Install steps: from the official MCP Registry entry.