Kaseya BMS vs Git
A side-by-side look at the Kaseya BMS and Git MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Kaseya BMS for support & service management work; choose Git for version control as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Kaseya BMS when
- You need dedicated capabilities in the Support & Service Management domain.
- You have the keys it needs:
KASEYA_BMS_TENANT_SUBDOMAIN, KASEYA_BMS_API_TOKEN, KASEYA_BMS_K1_TOKEN. - You want tools like
kaseya_bms_list_tickets, kaseya_bms_get_ticket, kaseya_bms_create_ticket.
Choose Git when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
repo_path, context_lines, target.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Support & Service Management | Version Control |
| Quality signal | 45/100 · Fair | 81/100 · Excellent |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | KASEYA_BMS_TENANT_SUBDOMAINKASEYA_BMS_API_TOKENKASEYA_BMS_K1_TOKEN | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 91,550 |
| Directory activity | 2 views 0 installs 0 upvotes | 53 views 0 installs 0 upvotes |
| Tools | 10 | 16 |
| Full listing | View Kaseya BMS | View Git |
Tools & capabilities
Kaseya BMS tools 10
kaseya_bms_list_ticketsList tickets. Optional `$filter`; status pick if omitted.kaseya_bms_get_ticketGet a ticket by id.kaseya_bms_create_ticketCreate a new ticket (destructive — confirmation required).kaseya_bms_add_ticket_noteAppend a note to a ticket (destructive — confirmation required).kaseya_bms_list_time_entriesTime entries by date range (24h / 7d / 30d / custom / all).kaseya_bms_list_accountsAccounts (clients).kaseya_bms_list_contactsContacts.kaseya_bms_list_contractsContracts.kaseya_bms_list_service_catalogService catalog items.kaseya_bms_search_knowledge_baseKnowledge base search.
Git tools 16
repo_pathcontext_linestargetmessageMERGE_HEADHEADfilesmax_countstart_timestampend_timestampbranch_namebase_branch- +4 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Kaseya BMS
No confirmed install command for Kaseya BMS yet — follow the setup steps linked from its listing page rather than a guessed package name.
Git
{
"mcpServers": {
"git": {
"command": "uvx",
"args": [
"mcp-server-git"
]
}
}
}
Frequently asked questions
Kaseya BMS is categorized under Support & Service Management and uses an install path we have not confirmed yet. Git belongs to Version Control and uses a local stdio subprocess. Pick Kaseya BMS for support & service management work and Git for version control.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Kaseya BMS has no confirmed install command yet — follow its own setup instructions.
Kaseya BMS has no declared pricing — check the project's own site. Git is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add kaseya-bms and git as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Kaseya BMS has a quality signal of 45/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. Git has 81/100 (Excellent) with 53 views, 0 installs and 91,550 GitHub stars.