Jira Alerts (JSM Oper… vs Invgate Service Desk… | AllMCPs
Side-by-Side Model Context Protocol Comparison
Jira Alerts (JSM Operations) vs Invgate Service Desk MCP
In-depth architectural comparison of the Jira Alerts (JSM Operations) 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
Jira Alerts (JSM Operations)
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 Jira Alerts (JSM Operations) 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 Jira Alerts (JSM Operations) 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: JSM_CLOUD_ID, JSM_EMAIL, JSM_API_TOKEN, JSM_OAUTH_TOKEN, JSM_TOOLSETS, JSM_READ_ONLY, TRANSPORT, PORT.
Primary tools included: Search and list JSM Operations alerts, Read alert notes and activity timelines, Acknowledge, close, and annotate alerts.
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.
Primary tools included: 96 tools across 11 service-management domains, Read-only operation by default, Profile-based write controls.
MCP server for Jira Service Management Operations — alerts, on-call schedules and responders
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.
Jira Alerts (JSM Operations) 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 Jira Alerts (JSM Operations) when you need capabilities focused on support & service management and Invgate Service Desk MCP when you require tools for support & service management.