Kaseya BMS MCP vs sevDesk
Kaseya BMS MCP is an MCP server published by Servosity. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). sevDesk is an MCP server published by jaylann. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |   Kaseya BMS MCP |  sevDesk |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.12 Forks (GitHub): 17 Stars (GitHub): 74 Not marked · First seen |
Listed Version: 1.2.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Kaseya BMS MCP | sevDesk |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 74 | No figure on GitHub |
| Forks (GitHub) (differs) | 17 | No figure on GitHub |
| Last release (differs) | 2026-11-11 (better) | 2026-11-11 (worse) |
| Where it runs (differs) | On your machine (https://github.com/Servosity/msp-skills/releases/download/kaseya-bms-v0.1.12/kaseya-bms-mcp.mcpb) | On your machine (mcp-server-sevdesk) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 11, secrets among them: 5 | 9, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/servosity/msp-skills | github.com/jaylann/mcp-server-sevdesk |
| Changes in the last 7 days (differs) | 13 | 5 |
| First seen (differs) | 2026-10-11 | 2026-11-10 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Kaseya BMS MCP
CLI and MCP server for Kaseya BMS PSA: tickets, CRM, contracts, finance, and offline analytics.
sevDesk
Safety-first MCP server for sevDesk accounting: invoices, receipts, banking, reports. Unofficial.
How to run each
Kaseya BMS MCP As a Claude Code plugin
/plugin marketplace add servosity/msp-skills
/plugin install kaseya-bms@msp-skillsRequires: KASEYA_BMS_BEARER_AUTH (secret), KASEYA_BMS_MCP_HTTP_TOKEN (secret), KASEYA_BMS_PASSWORD (secret), KASEYA_BMS_TENANT, KASEYA_BMS_TOKEN (secret), KASEYA_BMS_USERNAME, PRINTING_PRESS_CLIENT_PROFILE (secret)
sevDesk As a local MCP server: npm package
claude mcp add --env "SEVDESK_API_TOKEN=<YOUR_SEVDESK_API_TOKEN>" --transport stdio mcp-server-sevdesk -- npx -y mcp-server-sevdeskRequires: SEVDESK_API_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only Kaseya BMS MCP asks for
KASEYA_BMS_BASE_URLKASEYA_BMS_BEARER_AUTH (secret)KASEYA_BMS_MCP_HTTP_TOKEN (secret)KASEYA_BMS_MCP_READ_ONLYKASEYA_BMS_NO_LOCAL_DATAKASEYA_BMS_PASSWORD (secret)KASEYA_BMS_TENANTKASEYA_BMS_TOKEN (secret)KASEYA_BMS_USERNAMEKASEYA_BMS_USER_AGENTPRINTING_PRESS_CLIENT_PROFILE (secret)
Only sevDesk asks for
SEVDESK_ALLOWSEVDESK_API_TOKEN (secret)SEVDESK_AUDIT_LOGSEVDESK_CONFIRMSEVDESK_DRY_RUNSEVDESK_FILE_DIRSSEVDESK_OUTPUT_DIRSEVDESK_READ_ONLYSEVDESK_TOOLSETS
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Kaseya BMS MCP · What it can do: sevDesk · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.