# io.github.WYRE-AI/kaseya-bms-mcp

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

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.1.5
- **Author:** io.github.WYRE-AI
- **License:** Unknown
- **Source:** https://github.com/WYRE-AI/kaseya-bms-mcp

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 1 day

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-25T01:27:16.230Z
- **Version scanned:** HEAD
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

10 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `kaseya_bms_list_tickets` — List BMS tickets. Supports OData $filter, $top, $skip. If no filter is provided, the user is prompted to choose a status scope.
- `kaseya_bms_get_ticket` — Get details for a single ticket by ticket id.
- `kaseya_bms_create_ticket` — Create a new ticket in BMS. DESTRUCTIVE: requires user confirmation before submission.
- `kaseya_bms_add_ticket_note` — Append a note to an existing ticket. DESTRUCTIVE: requires user confirmation before submission.
- `kaseya_bms_list_time_entries` — List time entries by date range. If no range is given the user is prompted (24h / 7d / 30d / custom / all).
- `kaseya_bms_list_accounts` — List accounts (clients) in the BMS tenant.
- `kaseya_bms_list_contacts` — List contacts in the BMS tenant.
- `kaseya_bms_list_contracts` — List contracts in the BMS tenant.
- `kaseya_bms_list_service_catalog` — List service catalog items configured in the tenant.
- `kaseya_bms_search_knowledge_base` — Search the BMS knowledge base. If no query is provided the user is prompted for one.

## Install

This entry has no npm package and no hosted endpoint, so there is nothing for an MCP client to launch or connect to. It is indexed as source only.

## Blast radius

Contained to moderate — no package coordinates and no declared endpoint — Forge cannot tell where this would run or whose authority it would borrow. Known so far: holds an api key; read-only tool surface.
- Floor 15, ceiling 27 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/io.github.WYRE-AI%2Fkaseya-bms-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/io.github.WYRE-AI%2Fkaseya-bms-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/io.github.WYRE-AI%2Fkaseya-bms-mcp
- HTML page: https://forgeregistry.com/registry/io.github.WYRE-AI%2Fkaseya-bms-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.