Kaseya BMS MCP Server

Kaseya BMS MCP is an MCP integration. CLI and MCP server for Kaseya BMS PSA: tickets, CRM, contracts, finance, and offline analytics.

Packages and local setup

The published mcpb package is https://github.com/Servosity/msp-skills/releases/download/kaseya-bms-v0.1.3/kaseya-bms-mcp.mcpb, version 0.1.3. Its declared MCP transport is stdio.

The package declares 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 (required): Password for KASEYA_BMS_USERNAME. Exchanged for a JWT; never sent on data calls.; KASEYA_BMS_TENANT (required): 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 (required): Kaseya BMS login used by auth login to exchange for a short-lived JWT..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.1.3 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.