Jira Service Management MCP
Every Jira Service Management Cloud request-API (servicedeskapi) and Assets endpoint in one binary
The current version, v0.1.4, was published to the official MCP registry on 2026-10-23. It is distributed through a declared package, filed under Productivity & Project Mgmt by this index, and declares 10 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.
Using Jira Service Management MCP in Claude, Cursor, Gemini CLI, Cline, or Zed?
MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).
Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less
uv tool install mcpindex-gate && mcpindex-config-wireSemantic screen found no manipulation pattern in the description. Conformance probe not yet run.
mcpindex.integrity.descriptionpassINFOevidence“Tool provides Jira Service Management API access”via static_description
- - Semantic screen only - the deterministic conformance probe has not run on this server
- - Confidence is reported but not yet calibrated (v1)
- - Screen reads the tool description, not the live behavior
- - advisory
- - registry description only no input schema
- - screen model 8b
- - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not
Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.
Own this server? Test a description on the public screen → It is a separate check from the verdict above, so the two can differ.
That verdict was true at screening time (snapshot 2026-10-23).
Contracts can change after screening, with no version bump. The gate pins Jira Service Management MCP’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.
See your first HOLD in 2 minutes →
Related: how to trust an MCP server · screen before install · silent contract drift
People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.
[Independent trust record for Jira Service Management MCP](https://mcpindex.ai/server/io-github-servosity-jira-service-management-mcp) - screening verdict, registry provenance, and contract drift monitoring.<a href="https://mcpindex.ai/server/io-github-servosity-jira-service-management-mcp">Independent trust record for Jira Service Management MCP</a> - screening verdict, registry provenance, and contract drift monitoring.A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.
[](https://mcpindex.ai/server/io-github-servosity-jira-service-management-mcp)<a href="https://mcpindex.ai/server/io-github-servosity-jira-service-management-mcp"><img src="https://mcpindex.ai/api/v1/badge/io-github-servosity-jira-service-management-mcp" alt="mcpindex verdict" height="20" /></a>JIRA_SERVICE_MANAGEMENT_API_TOKENAtlassian API token from id.atlassian.com/manage-profile/security/api-tokens (Basic auth password).
JIRA_SERVICE_MANAGEMENT_CLOUD_IDAssets only: your site's cloudId. Leave blank if you do not use Assets; 'cmdb discover' prints it.
JIRA_SERVICE_MANAGEMENT_EMAILAtlassian account email (Basic auth username).
JIRA_SERVICE_MANAGEMENT_SITEYour Atlassian site subdomain: acme for acme.atlassian.net.
JIRA_SERVICE_MANAGEMENT_WORKSPACE_IDAssets only: your Assets workspaceId. Leave blank if you do not use Assets; 'cmdb discover' prints it.
JIRA_SERVICE_MANAGEMENT_BASE_URLOptional. Replaces the request-API root built from your site. Leave blank: set the site instead, because this override also redirects Assets calls.
JIRA_SERVICE_MANAGEMENT_MCP_READ_ONLYOptional. Set to 1 to drop the MCP server's write tools and refuse any non-GET execute call.
JIRA_SERVICE_MANAGEMENT_MCP_HTTP_TOKENRequired only when running the MCP server with --transport http (a remote/hosted deployment); callers must send a matching Authorization: Bearer header. Not needed for the default local stdio transport Claude Desktop uses.
JIRA_SERVICE_MANAGEMENT_USER_AGENTOptional. Overrides the User-Agent the CLI sends to Atlassian. Leave blank to use the built-in one.
PRINTING_PRESS_CLIENT_PROFILEOnly used when the MCP server is bound to a tenant-gated client profile. This connector registers no tenant-gated source, so leave it blank.
Live interview and meeting coaching with saved context and Notion sync. Audio runs in the full app.
Search, read and create Linear issues, projects, teams and cycles.
MCP server for Jira Cloud — manage issues, sprints, boards, filters, and custom fields