Loading
Kaseya BMS MCP
Power your agent
Add this server
The publisher's own command. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
Local command
mcpb https://github.com/Servosity/msp-skills/releases/download/kaseya-bms-v0.1.9/kaseya-bms-mcp.mcpbCredentials from the publisher
- KASEYA_BMS_BASE_URL — Base URL for the Kaseya BMS API. Leave the prefilled default unless your account uses a different regional or self-hosted host.
- KASEYA_BMS_BEARER_AUTH — Alias for KASEYA_BMS_TOKEN - a pre-minted Kaseya BMS JWT sent as a Bearer token. Set one of the two, or use 'auth login'.
- KASEYA_BMS_PASSWORD — Password for KASEYA_BMS_USERNAME. Exchanged for a JWT; never sent on data calls.
- KASEYA_BMS_TENANT — Your company name exactly as it appears under My Settings in BMS. The authenticate call rejects the login without it.
- KASEYA_BMS_TOKEN — Pre-minted Kaseya BMS JWT, sent as a Bearer token. Set this OR KASEYA_BMS_BEARER_AUTH; alternatively run 'kaseya-bms-cli auth login' to mint one from username/password/tenant.
- KASEYA_BMS_USERNAME — Kaseya BMS login used by `auth login` to exchange for a short-lived JWT.
- KASEYA_BMS_MCP_READ_ONLY — Optional. Set to exactly 1 to expose only read-only tools and refuse any state-changing execute call.
- KASEYA_BMS_NO_LOCAL_DATA — Optional. Set to 1 to keep no local copy of API responses: reads go to the API and the response cache is off.
- KASEYA_BMS_MCP_HTTP_TOKEN — Required only when running the MCP server with --transport http. Not needed for the default local stdio transport.
- KASEYA_BMS_USER_AGENT — Optional. Overrides the User-Agent the CLI sends on Kaseya BMS requests. Leave blank to use the CLI's own built-in User-Agent.
- PRINTING_PRESS_CLIENT_PROFILE — Optional: binds the MCP server to an existing tenant-gated Printing Press client profile. Leave unset for a single-tenant install.
Claude Code has no install link for a local command. Copy the command below and run it in a terminal.
shClaude Code
KASEYA_BMS_BASE_URL=<value> KASEYA_BMS_BEARER_AUTH=<secret> KASEYA_BMS_PASSWORD=<secret> KASEYA_BMS_TENANT=<value> KASEYA_BMS_TOKEN=<secret> KASEYA_BMS_USERNAME=<value> KASEYA_BMS_MCP_READ_ONLY=<value> KASEYA_BMS_NO_LOCAL_DATA=<value> KASEYA_BMS_MCP_HTTP_TOKEN=<secret> KASEYA_BMS_USER_AGENT=<value> PRINTING_PRESS_CLIENT_PROFILE=<secret> claude mcp add io.github.servosity-kaseya-bms-mcp -- mcpb https://github.com/Servosity/msp-skills/releases/download/kaseya-bms-v0.1.9/kaseya-bms-mcp.mcpbRun in a terminal.
jsonClaude Desktop
{ "mcpServers": { "io.github.servosity-kaseya-bms-mcp": { "command": "mcpb", "args": [ "https://github.com/Servosity/msp-skills/releases/download/kaseya-bms-v0.1.9/kaseya-bms-mcp.mcpb" ], "env": { "KASEYA_BMS_BASE_URL": "<value>", "KASEYA_BMS_BEARER_AUTH": "<secret>", "KASEYA_BMS_PASSWORD": "<secret>", "KASEYA_BMS_TENANT": "<value>", "KASEYA_BMS_TOKEN": "<secret>", "KASEYA_BMS_USERNAME": "<value>", "KASEYA_BMS_MCP_READ_ONLY": "<value>", "KASEYA_BMS_NO_LOCAL_DATA": "<value>", "KASEYA_BMS_MCP_HTTP_TOKEN": "<secret>", "KASEYA_BMS_USER_AGENT": "<value>", "PRINTING_PRESS_CLIENT_PROFILE": "<secret>" } } }}claude_desktop_config.json
Local · mcpbPublisher installStep-by-step: add this in Claude
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
Host a copy with our keys and logs.
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchServer facts
LocalTools
Tools
No tool list yet. Remote servers get one after the first health check.
FAQ