Kaseya BMS

MCP server for Kaseya BMS PSA — tickets, accounts, time entries, contracts.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "kaseya-bms": {
      "command": "npx",
      "args": [
        "-y",
        "kaseya-bms"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Documentation Overview

Kaseya BMS MCP Server

Model Context Protocol (MCP) server for the Kaseya BMS PSA API. Exposes tickets, accounts, contacts, contracts, time entries, the service catalog, and the knowledge base to AI assistants.

Tools

Tool	Description
`kaseya_bms_list_tickets`	List tickets. Optional `$filter`; status pick if omitted.
`kaseya_bms_get_ticket`	Get a ticket by id.
`kaseya_bms_create_ticket`	Create a new ticket (destructive — confirmation required).
`kaseya_bms_add_ticket_note`	Append a note to a ticket (destructive — confirmation required).
`kaseya_bms_list_time_entries`	Time entries by date range (24h / 7d / 30d / custom / all).
`kaseya_bms_list_accounts`	Accounts (clients).
`kaseya_bms_list_contacts`	Contacts.
`kaseya_bms_list_contracts`	Contracts.
`kaseya_bms_list_service_catalog`	Service catalog items.
`kaseya_bms_search_knowledge_base`	Knowledge base search.

When the user omits required filters or runs a destructive action, the server uses MCP elicitation to prompt for choices or confirm.

Interactive Ticket Card (MCP Apps)

kaseya_bms_get_ticket renders as an interactive card in MCP Apps hosts (Claude Desktop/web) with an in-card "Add note" round-trip via kaseya_bms_add_ticket_note (always posted internal-only); plain-JSON behavior is unchanged in other hosts. The card is neutral by default and brandable via window.__BRAND__ injection or MCP_BRAND_* env vars (MCP_BRAND_NAME, MCP_BRAND_LOGO_URL, MCP_BRAND_PRIMARY_COLOR, MCP_BRAND_ACCENT_COLOR, MCP_BRAND_BG, MCP_BRAND_TEXT) — no rebuild needed. After editing ui/, regenerate the embedded bundle with npm run build:ui.

Configuration

Environment-variable mode (default)

Variable	Required	Description
`KASEYA_BMS_TENANT_SUBDOMAIN`	yes	Tenant subdomain (e.g. `yourcompany`)
`KASEYA_BMS_API_TOKEN`	one of	BMS API token (secret)
`KASEYA_BMS_K1_TOKEN`	one of	Kaseya One SSO token (secret)
`MCP_TRANSPORT`	no	`stdio` (default) or `http`
`MCP_HTTP_PORT`	no	HTTP listen port (default `8080`)
`AUTH_MODE`	no	`env` (default) or `gateway`

Either KASEYA_BMS_API_TOKEN OR KASEYA_BMS_K1_TOKEN is required.

Gateway mode

When deployed behind the WYRE MCP Gateway, set AUTH_MODE=gateway and the server will read credentials from per-request HTTP headers:

X-Kaseya-BMS-Tenant-Subdomain (required)
X-Kaseya-BMS-API-Token (or)
X-Kaseya-BMS-K1-Token

Each request creates a fresh server instance with isolated credentials — no cross-tenant process.env pollution.

Local development

Terminal

npm install
npm run build
KASEYA_BMS_TENANT_SUBDOMAIN=yourcompany \
  KASEYA_BMS_API_TOKEN=... \
  npm start

Run as HTTP for testing:

bash

MCP_TRANSPORT=http npm start
curl http://localhost:8080/health

Docker

Terminal

docker build -t kaseya-bms-mcp .
docker run --rm -p 8080:8080 \
  -e KASEYA_BMS_TENANT_SUBDOMAIN=yourcompany \
  -e KASEYA_BMS_API_TOKEN=... \
  kaseya-bms-mcp

License

Apache-2.0

Read the full README →View source on GitHub →

Related MCP Servers

View all in Legal View all alternatives

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Kaseya BMS

Add the following block to your claude_desktop_config.json under mcpServers: "mcpServers": { "kaseya-bms": { "command": "npx", "args": ["-y", "Kaseya BMS"] } }

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/kaseya-bms?style=directory)](https://allmcps.com/mcp/kaseya-bms)

HTML Embed

<a href="https://allmcps.com/mcp/kaseya-bms"><img src="https://allmcps.com/api/badge/kaseya-bms?style=directory" alt="Kaseya BMS on AllMCPs" /></a>

Technical Specs & Signals

CategoryLegal

27Quality signal: Emerging · 27/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership8/20

Documentation & tools11/30

Adoption & activity1/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

★ Featured

Moxie Docs MCP

MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Explore Server →

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge and attach your website — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in ⚖️ Legal →Best MCP servers for Legal →Alternatives to Kaseya BMS →Install in Claude Desktop Install in Cursor Install in VS Code

Documentation Overview

Kaseya BMS MCP Server

Model Context Protocol (MCP) server for the Kaseya BMS PSA API. Exposes tickets, accounts, contacts, contracts, time entries, the service catalog, and the knowledge base to AI assistants.

Tools

Tool	Description
`kaseya_bms_list_tickets`	List tickets. Optional `$filter`; status pick if omitted.
`kaseya_bms_get_ticket`	Get a ticket by id.
`kaseya_bms_create_ticket`	Create a new ticket (destructive — confirmation required).
`kaseya_bms_add_ticket_note`	Append a note to a ticket (destructive — confirmation required).
`kaseya_bms_list_time_entries`	Time entries by date range (24h / 7d / 30d / custom / all).
`kaseya_bms_list_accounts`	Accounts (clients).
`kaseya_bms_list_contacts`	Contacts.
`kaseya_bms_list_contracts`	Contracts.
`kaseya_bms_list_service_catalog`	Service catalog items.
`kaseya_bms_search_knowledge_base`	Knowledge base search.

When the user omits required filters or runs a destructive action, the server uses MCP elicitation to prompt for choices or confirm.

Interactive Ticket Card (MCP Apps)

Configuration

Environment-variable mode (default)

Variable	Required	Description
`KASEYA_BMS_TENANT_SUBDOMAIN`	yes	Tenant subdomain (e.g. `yourcompany`)
`KASEYA_BMS_API_TOKEN`	one of	BMS API token (secret)
`KASEYA_BMS_K1_TOKEN`	one of	Kaseya One SSO token (secret)
`MCP_TRANSPORT`	no	`stdio` (default) or `http`
`MCP_HTTP_PORT`	no	HTTP listen port (default `8080`)
`AUTH_MODE`	no	`env` (default) or `gateway`

Either KASEYA_BMS_API_TOKEN OR KASEYA_BMS_K1_TOKEN is required.

Gateway mode

When deployed behind the WYRE MCP Gateway, set AUTH_MODE=gateway and the server will read credentials from per-request HTTP headers:

X-Kaseya-BMS-Tenant-Subdomain (required)
X-Kaseya-BMS-API-Token (or)
X-Kaseya-BMS-K1-Token

Each request creates a fresh server instance with isolated credentials — no cross-tenant process.env pollution.

Local development

Terminal

npm install
npm run build
KASEYA_BMS_TENANT_SUBDOMAIN=yourcompany \
  KASEYA_BMS_API_TOKEN=... \
  npm start

Run as HTTP for testing:

bash

MCP_TRANSPORT=http npm start
curl http://localhost:8080/health

Docker

Terminal

docker build -t kaseya-bms-mcp .
docker run --rm -p 8080:8080 \
  -e KASEYA_BMS_TENANT_SUBDOMAIN=yourcompany \
  -e KASEYA_BMS_API_TOKEN=... \
  kaseya-bms-mcp

License

Apache-2.0