MCP server for Kaseya BMS PSA — tickets, accounts, time entries, contracts.
KASEYA_BMS_API_TOKENAPI keyoptionalBMS API token (omit if using Kaseya One token)
KASEYA_BMS_K1_TOKENAPI keyoptionalKaseya One SSO token (alternative to API token)
Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
kaseya_bms_list_ticketsList BMS tickets. Supports OData $filter, $top, $skip. If no filter is provided, the user is prompted to choose a status scope.List BMS tickets. Supports OData $filter, $top, $skip. If no filter is provided, the user is prompted to choose a status scope.
No input schema was published for this tool.
kaseya_bms_get_ticketGet details for a single ticket by ticket id.Get details for a single ticket by ticket id.
No input schema was published for this tool.
kaseya_bms_create_ticketCreate a new ticket in BMS. DESTRUCTIVE: requires user confirmation before submission.Create a new ticket in BMS. DESTRUCTIVE: requires user confirmation before submission.
No input schema was published for this tool.
kaseya_bms_add_ticket_noteAppend a note to an existing ticket. DESTRUCTIVE: requires user confirmation before submission.Append a note to an existing ticket. DESTRUCTIVE: requires user confirmation before submission.
No input schema was published for this tool.
kaseya_bms_list_time_entriesList time entries by date range. If no range is given the user is prompted (24h / 7d / 30d / custom / all).List time entries by date range. If no range is given the user is prompted (24h / 7d / 30d / custom / all).
No input schema was published for this tool.
kaseya_bms_list_accountsList accounts (clients) in the BMS tenant.List accounts (clients) in the BMS tenant.
No input schema was published for this tool.
kaseya_bms_list_contactsList contacts in the BMS tenant.List contacts in the BMS tenant.
No input schema was published for this tool.
kaseya_bms_list_contractsList contracts in the BMS tenant.List contracts in the BMS tenant.
No input schema was published for this tool.
kaseya_bms_list_service_catalogList service catalog items configured in the tenant.List service catalog items configured in the tenant.
No input schema was published for this tool.
kaseya_bms_search_knowledge_baseSearch the BMS knowledge base. If no query is provided the user is prompted for one.Search the BMS knowledge base. If no query is provided the user is prompted for one.
No input schema was published for this tool.
10 of 10 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
MCP server for Kaseya BMS PSA — tickets, accounts, time entries, contracts.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.