← Index

Kaseya BMS MCP

io.github.Servosity/kaseya-bms-mcpv0.1.2CRM & Sales

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

The current version, v0.1.2, was published to the official MCP registry on 2026-08-27. It is distributed through a declared package, filed under CRM & Sales by this index, and declares 6 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using Kaseya BMS MCP in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Auditable install path →Watch it hold a drift →
Trust verdict · v1 advisory · method
REVIEWstatus: PARTIALfresh until 2026-09-13 13:42 UTC
screened 2026-07-22tier: scannedgranularity: description-levelsource: registry

Semantic screen found no manipulation pattern in the description. Conformance probe not yet run.

mcpindex.integrity.descriptionpassINFO

evidence“No malicious instructions found”via static_description

Limits of this verdict
  • - Semantic screen only - the deterministic conformance probe has not run on this server
  • - Confidence is reported but not yet calibrated (v1)
  • - Screen reads the tool description, not the live behavior
  • - advisory
  • - registry description only no input schema
  • - screen model 8b
  • - Still current: the description we screened is unchanged, re-checked against the registry
  • - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not

Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.

Own this server? Screen its description →

That verdict was true at screening time (snapshot 2026-09-06).

Contracts can change after screening, with no version bump. The gate pins Kaseya BMS MCP’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Cite this record

People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.

Markdown
[Independent trust record for Kaseya BMS MCP](https://mcpindex.ai/server/io-github-servosity-kaseya-bms-mcp) - screening verdict, registry provenance, and contract drift monitoring.
HTML
<a href="https://mcpindex.ai/server/io-github-servosity-kaseya-bms-mcp">Independent trust record for Kaseya BMS MCP</a> - screening verdict, registry provenance, and contract drift monitoring.
Embed this badge

A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.

Markdown
[![mcpindex](https://mcpindex.ai/api/v1/badge/io-github-servosity-kaseya-bms-mcp)](https://mcpindex.ai/server/io-github-servosity-kaseya-bms-mcp)
HTML
<a href="https://mcpindex.ai/server/io-github-servosity-kaseya-bms-mcp"><img src="https://mcpindex.ai/api/v1/badge/io-github-servosity-kaseya-bms-mcp" alt="mcpindex verdict" height="20" /></a>
Environment variables
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
secret

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
requiredsecret

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
secret

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.

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
20
installability
25
documentation
15
stability
5
Alternatives in CRM & Sales
BoondManager MCP Server
io.github.fauguste/boondmanager-mcp-server

MCP Server for BoondManager API - 182 tools, 12 prompts, 22 resources (ERP/CRM)

codev
io.github.flxbl-io/codev

Connect AI agents to codev for Salesforce projects, builds, releases, validations, and insights.

SparkLaunch
io.github.SparkLaunch-Dev/sparklaunch

Founder workflows for idea validation, branding, campaigns, landing pages, analytics, and CRM.