What is the key difference between Invgate Service Desk MCP and Rootly MCP Server?

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

How do I install Invgate Service Desk MCP or Rootly MCP Server 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 Invgate Service Desk MCP and Rootly MCP Server free or paid?

Invgate Service Desk MCP operates under a BYOK (Pay Provider Direct) model (API Key required). Rootly MCP Server operates under a BYOK (Pay Provider Direct) model (API Key required).

Which MCP server has more tools and community activity?

Invgate Service Desk MCP lists 6 tools with 2 views and 3 GitHub stars. Rootly MCP Server lists 6 tools with 1 views and 45 GitHub stars.

Can I use both Invgate Service Desk MCP and Rootly MCP Server 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

Invgate Service Desk MCP vs Rootly MCP Server

In-depth architectural comparison of the Invgate Service Desk MCP and Rootly MCP Server 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

Invgate Service Desk MCP

Support & Service Management · Local stdio

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

Rootly MCP Server

Support & Service Management · Local stdio

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

Verdict Summary: Choose Invgate Service Desk MCP if you need specialized Support & Service Management tools running via a local process. Choose Rootly MCP Server 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 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_WRITE_PROFILE.
Primary tools included: 96 tools spanning incidents, users, assets, workflows, and more, Read-only access enabled by default, Optional write operations for incidents, time tracking, and knowledge base.

Explore Invgate Service Desk MCP Details

Choose Rootly MCP Server 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)).

Feature & Specification Comparison

Specification	Invgate Service Desk MCP tracegazer Support & Service Management	Rootly MCP Server Rootly-AI-Labs Support & Service Management
Summary	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.	MCP server for the incident management platform Rootly.
Category & Scope

Tools & Capabilities Breakdown

Invgate Service Desk MCP Tools (6)

96 tools spanning incidents, users, assets, workflows, and more

Read-only access enabled by default

Optional write operations for incidents, time tracking, and knowledge base

Supports searching, listing, creating, updating, and commenting

Authentication via API token with HTTP Basic

Prebuilt MCP bundle for easy installation with compatible clients

Rootly MCP Server Tools (6)

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).

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_WRITE_PROFILE": "YOUR_INVGATE_WRITE_PROFILE_HERE"
      }
    }
  }
}

Rootly MCP Server Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "rootly-ai-labs-rootly-mcp-server": {
      "command": "uvx",
      "args": [
        "--from",
        "rootly-mcp-server",
        "rootly-mcp-server"
      ],
      "env": {
        "ROOTLY_API_TOKEN": "YOUR_ROOTLY_API_TOKEN_HERE",
        "ROOTLY_MCP_HOSTED_TOOL_PROFILE": "YOUR_ROOTLY_MCP_HOSTED_TOOL_PROFILE_HERE",
        "ROOTLY_MCP_ENABLED_TOOLS": "YOUR_ROOTLY_MCP_ENABLED_TOOLS_HERE"
      }
    }
  }
}

Frequently Asked Questions

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

More alternatives to Invgate Service Desk MCP More alternatives to Rootly MCP Server Support & Service Management category hub Canonical compare URL