What is the key difference between Kaseya BMS and Invgate Service Desk MCP?

Kaseya BMS belongs to the Support & Service Management category with local stdio execution, while Invgate Service Desk MCP belongs to the Support & Service Management category with local stdio execution.

How do I install Kaseya BMS or Invgate Service Desk MCP in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Kaseya BMS and Invgate Service Desk MCP free or paid?

Kaseya BMS operates under a Free / Open Source model (No auth required). Invgate Service Desk MCP operates under a BYOK (Pay Provider Direct) model (API Key required).

Which MCP server has more tools and community activity?

Kaseya BMS lists 10 tools with 0 views and 0 GitHub stars. Invgate Service Desk MCP lists 6 tools with 2 views and 4 GitHub stars.

Can I use both Kaseya BMS and Invgate Service Desk MCP together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Kaseya BMS vs Invgate Service Desk MCP

In-depth architectural comparison of the Kaseya BMS and Invgate Service Desk MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Kaseya BMS

Support & Service Management · Local stdio

Quality: 45/100 (Fair) | Auth: No auth required

Invgate Service Desk MCP

Support & Service Management · Local stdio

Quality: 48/100 (Fair) | Auth: API Key required

Verdict Summary: Choose Kaseya BMS if you need specialized Support & Service Management tools running via a local process. Choose Invgate Service Desk MCP if your workspace requires Support & Service Management integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Kaseya BMS when:

You need dedicated capabilities in the Support & Service Management domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: KASEYA_BMS_TENANT_SUBDOMAIN, KASEYA_BMS_API_TOKEN, KASEYA_BMS_K1_TOKEN.
Primary tools included: kaseya_bms_list_tickets, kaseya_bms_get_ticket, kaseya_bms_create_ticket.

Explore Kaseya BMS Details

Choose Invgate Service Desk MCP when:

You need dedicated capabilities in the Support & Service Management domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: INVGATE_BASE_URL, INVGATE_API_TOKEN, INVGATE_API_USERNAME, INVGATE_WRITE_PROFILE, INVGATE_ENABLE_WRITES, INVGATE_TELEMETRY, INVGATE_TELEMETRY_DETAIL.

Feature & Specification Comparison

Specification	Kaseya BMS Support & Service Management	Invgate Service Desk MCP tracegazer Support & Service Management
Summary	MCP server for Kaseya BMS PSA — tickets, accounts, time entries, contracts.	MCP server for InvGate Service Desk: 96 tools across 11 domains (incidents, users, knowledge base, assets, custom fields, workflows, time tracking), read-only by default with opt-in writes.
Category & Scope	Support & Service Management

Tools & Capabilities Breakdown

Kaseya BMS Tools (10)

kaseya_bms_list_tickets

List tickets. Optional `$filter`; status pick if omitted.

kaseya_bms_get_ticket

Get a ticket by id.

kaseya_bms_create_ticket

Create a new ticket (destructive — confirmation required).

kaseya_bms_add_ticket_note

Append a note to a ticket (destructive — confirmation required).

kaseya_bms_list_time_entries

Time entries by date range (24h / 7d / 30d / custom / all).

kaseya_bms_list_accounts

Accounts (clients).

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Kaseya BMS Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "kaseya-bms": {
      "command": "npx",
      "args": [
        "-y",
        "kaseya-bms"
      ],
      "env": {
        "KASEYA_BMS_TENANT_SUBDOMAIN": "YOUR_KASEYA_BMS_TENANT_SUBDOMAIN_HERE",
        "KASEYA_BMS_API_TOKEN": "YOUR_KASEYA_BMS_API_TOKEN_HERE",
        "KASEYA_BMS_K1_TOKEN": "YOUR_KASEYA_BMS_K1_TOKEN_HERE"
      }
    }
  }
}

Invgate Service Desk MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "tracegazer-invgate-service-desk-mcp": {
      "command": "uvx",
      "args": [
        "invgate-service-desk-mcp"
      ],
      "env": {
        "INVGATE_BASE_URL": "YOUR_INVGATE_BASE_URL_HERE",
        "INVGATE_API_TOKEN": "YOUR_INVGATE_API_TOKEN_HERE",
        "INVGATE_API_USERNAME": "YOUR_INVGATE_API_USERNAME_HERE",
        "INVGATE_WRITE_PROFILE": "YOUR_INVGATE_WRITE_PROFILE_HERE",
        "INVGATE_ENABLE_WRITES": "YOUR_INVGATE_ENABLE_WRITES_HERE",
        "INVGATE_TELEMETRY": "YOUR_INVGATE_TELEMETRY_HERE",
        "INVGATE_TELEMETRY_DETAIL": "YOUR_INVGATE_TELEMETRY_DETAIL_HERE"
      }
    }
  }
}

Frequently Asked Questions

Kaseya BMS is categorized under Support & Service Management and uses a local stdio subprocess. In contrast, Invgate Service Desk MCP belongs to Support & Service Management using local stdio subprocess. Select Kaseya BMS when you need capabilities focused on support & service management and Invgate Service Desk MCP when you require tools for support & service management.

More alternatives to Kaseya BMS More alternatives to Invgate Service Desk MCP Support & Service Management category hub