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

MCP Atlassian 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 MCP Atlassian 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 MCP Atlassian and Invgate Service Desk MCP free or paid?

MCP Atlassian operates under a BYOK (Pay Provider Direct) model (API Key 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?

MCP Atlassian lists 5 tools with 1 views and 5,931 GitHub stars. Invgate Service Desk MCP lists 6 tools with 2 views and 3 GitHub stars.

Can I use both MCP Atlassian 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

MCP Atlassian vs Invgate Service Desk MCP

In-depth architectural comparison of the MCP Atlassian 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

MCP Atlassian

Support & Service Management · Local stdio

Quality: 56/100 (Good) | Auth: API Key required

Invgate Service Desk MCP

Support & Service Management · Local stdio

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

Verdict Summary: Choose MCP Atlassian 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 MCP Atlassian 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: JIRA_URL, JIRA_USERNAME, JIRA_API_TOKEN, JIRA_PERSONAL_TOKEN, CONFLUENCE_URL, CONFLUENCE_USERNAME, CONFLUENCE_API_TOKEN.
Primary tools included: Supports Jira Cloud and Server/Data Center (v8.14+), Supports Confluence Cloud and Server/Data Center (v6.0+), Provides 98 tools for Jira and Confluence operations.

Explore MCP Atlassian 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: (BYOK (Pay Provider Direct)).

Feature & Specification Comparison

Specification	MCP Atlassian sooperset Support & Service Management	Invgate Service Desk MCP tracegazer Support & Service Management
Summary	MCP server for Atlassian products (Confluence and Jira). Supports Confluence Cloud, Jira Cloud, and Jira Server/Data Center. Provides comprehensive tools for searching, reading, creating, and managing content across Atlassian workspaces.	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

Tools & Capabilities Breakdown

MCP Atlassian Tools (5)

Supports Jira Cloud and Server/Data Center (v8.14+)

Supports Confluence Cloud and Server/Data Center (v6.0+)

Provides 98 tools for Jira and Confluence operations

Authentication via API tokens or Personal Access Tokens

Supports multi-user and streaming HTTP transports

Invgate Service Desk MCP Tools (6)

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

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

MCP Atlassian Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "sooperset-mcp-atlassian": {
      "command": "uvx",
      "args": [
        "mcp-atlassian"
      ],
      "env": {
        "JIRA_URL": "YOUR_JIRA_URL_HERE",
        "JIRA_USERNAME": "YOUR_JIRA_USERNAME_HERE",
        "JIRA_API_TOKEN": "YOUR_JIRA_API_TOKEN_HERE",
        "JIRA_PERSONAL_TOKEN": "YOUR_JIRA_PERSONAL_TOKEN_HERE",
        "CONFLUENCE_URL": "YOUR_CONFLUENCE_URL_HERE",
        "CONFLUENCE_USERNAME": "YOUR_CONFLUENCE_USERNAME_HERE",
        "CONFLUENCE_API_TOKEN": "YOUR_CONFLUENCE_API_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_WRITE_PROFILE": "YOUR_INVGATE_WRITE_PROFILE_HERE"
      }
    }
  }
}

Frequently Asked Questions

MCP Atlassian 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 MCP Atlassian 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 MCP Atlassian More alternatives to Invgate Service Desk MCP Support & Service Management category hub