MCP server for Kaseya BMS PSA — tickets, accounts, time entries, contracts.
Use this profile to copy client config, check auth requirements, review tools and resources, and compare related MCP servers before adding it to an AI client.
Get practical integration notes and launch examples for MCP servers like Kaseya BMS.
{
"KASEYA_BMS_TENANT_SUBDOMAIN": "YOUR_VALUE_HERE",
"KASEYA_BMS_API_TOKEN": "YOUR_SECRET_VALUE",
"KASEYA_BMS_K1_TOKEN": "YOUR_SECRET_VALUE",
"MCP_TRANSPORT": "stdio",
"AUTH_MODE": "env",
"LOG_LEVEL": "info"
}Add this server entry to the mcpServers object in your Claude Desktop config, then restart the app.
{
"mcpServers": {
"io-github-wyre-technology-kaseya-bms-mcp": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-io-github-wyre-technology-kaseya-bms-mcp"
],
"env": {
"KASEYA_BMS_TENANT_SUBDOMAIN": "YOUR_VALUE_HERE",
"KASEYA_BMS_API_TOKEN": "YOUR_SECRET_VALUE",
"KASEYA_BMS_K1_TOKEN": "YOUR_SECRET_VALUE",
"MCP_TRANSPORT": "stdio",
"AUTH_MODE": "env",
"LOG_LEVEL": "info"
}
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonNo remote HTTP endpoint is advertised. Use the package or stdio setup shown in Install.
Kaseya BMS is an MCP server for MCP server for Kaseya BMS PSA — tickets, accounts, time entries, contracts.. It supports STDIO transport.
Use the client-specific config in Install and add it to your MCP-compatible client.
Choose the Claude Desktop tab in Install and copy the config into Claude Desktop's MCP server settings.
Choose the Claude Code tab in Install and copy the config into Claude Code's MCP server settings.
Choose the Codex tab in Install and copy the config into Codex's MCP server settings.
Choose the Cursor or VS Code tab in Install and copy the config into Cursor or VS Code's MCP server settings.
Kaseya BMS uses STDIO transport. Use the package or command config in Install.
Kaseya BMS inventory is listed when the MCP endpoint exposes tools, resources, or prompts. Some servers require auth first.
Kaseya BMS is marked with Auth required by registry metadata auth. You may need provider login, an API key, a bearer token, or a session header.
| Package | Registry | Version | Inputs |
|---|---|---|---|
ghcr.io/wyre-technology/kaseya-bms-mcp:v1.0.6stdio | oci | Not captured | Env: KASEYA_BMS_TENANT_SUBDOMAIN required Env: KASEYA_BMS_API_TOKEN secret Env: KASEYA_BMS_K1_TOKEN secret Env: MCP_TRANSPORT Env: AUTH_MODE Env: LOG_LEVEL |