# Jira Service Management MCP connector Connect Jira Service Management to Claude, ChatGPT, Cursor and any MCP client through Elaichi, so people can ask about service desks, queues, requests, comments, attachments and customer organizations inside their own Jira Service Management access, with every call logged. Source: https://elaichi.ai/connectors/jiraservicemanagement/ ## Facts | | | | --- | --- | | Application | Jira Service Management | | Category | Ticketing | | AI tools | 30 | | Authentication | Connects over OAuth | | Needs your own OAuth app | No | | MCP endpoint | https://api.elaichi.ai/mcp | | Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent | | Tools advertised by name | Yes | ## What you can ask once Jira Service Management is connected - Show open issues in the IT support queue today - Which service desks have issues with no assignee? - Summarize attachments on issue SUP-1420 for the handover ## Connect Jira Service Management in Elaichi This happens once for the organization, before any client is involved. 1. Open Connections, choose Add connection, and pick Jira Service Management. 2. Optionally set Share with, then press Connect. 3. Approve it in Jira Service Management. Jira Service Management's own window opens. Whoever approves it decides what this connection can reach. Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Jira Service Management tools are exposed, rename them, or freeze arguments before anyone points a client at it. ## Connect Jira Service Management to Claude Endpoint: https://api.elaichi.ai/mcp 1. Open Customize, then Connectors. 2. Press Add. 3. Name it, paste the MCP server URL, then Continue. 4. Sign in and approve. On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves. ## Connect Jira Service Management to ChatGPT Endpoint: https://api.elaichi.ai/mcp 1. Open Plugins, then press the + button. 2. Name it and paste the endpoint into Server URL. 3. Leave Authentication on OAuth, then tick the risk acknowledgement. 4. Press Create, then sign in and approve. Works on the web today. The plugin directory lives at chatgpt.com/plugins. ## Connect Jira Service Management to Cursor Endpoint: https://api.elaichi.ai/mcp 1. Open `~/.cursor/mcp.json`. 2. Add the endpoint under `mcpServers`. 3. Reload Cursor, then sign in and approve. Set up per machine, so repeat it on each computer you work from. ## Connect Jira Service Management to any MCP client Endpoint: https://api.elaichi.ai/mcp 1. Add the endpoint as a remote MCP server. 2. Sign in and approve. The Elaichi Agent already has these tools, with nothing to set up. ## What the consent screen decides Only Read is granted by default, which is not enough to call a Jira Service Management tool. Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone. ## What teams do with Jira Service Management through Elaichi ### See what is waiting in a queue Support. Ask which requests are sitting in the high priority queue right now, how old they are and who raised them, without opening Jira Service Management and clicking through each one. ### Get up to speed before a call IT. Pull a single request with its full comment thread and attachments so you walk into the call knowing what the customer already tried and what the last agent told them. ### Check every open request for a customer Customer success. Before a renewal conversation, list the people in a customer organization and find the requests they have open across your service desks. ### Spot repeat problems across service desks Service desk leads. Search requests across projects for a theme, such as VPN or invoice access, and get a plain summary of how often it shows up and where. ### Pull the screenshot from a request Support. Download the log file or screenshot a customer attached to a request and have it read back to you in plain language. ### Know who belongs to which organization IT. List the customer organizations on a service desk and the users in each, so access questions and escalations go to the right people. ## Frequently asked questions ### How do I connect Jira Service Management to Claude? In Elaichi, choose Jira Service Management from the connector catalog and click connect. Jira Service Management opens its own Atlassian sign-in page, you sign in as yourself and approve access, and there is no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. ### Does Jira Service Management work with ChatGPT and Cursor as well as Claude? Yes. Once Jira Service Management is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any MCP client and the Elaichi Agent. You connect Jira Service Management once and every client uses it. ### What can an AI agent actually do with my Jira Service Management data? With this connector an agent can look up service desks, queues and projects in Jira Service Management, search requests, read a request with its comments, and download attachments such as screenshots and log files. It can also list customer organizations, the users in them and the agents on a service desk. That means you can ask what is in a queue, what a customer has open or what was said on a request, and get an answer from live Jira Service Management records. ### Does connecting Jira Service Management give the AI every project and service desk? No. The agent works inside the access of the person who signed in to Jira Service Management, so it only sees the service desks, queues and requests that person can already see. Elaichi can narrow that further, for example to a single service desk, but it can never widen it beyond what Jira Service Management itself allows. ### Can my team share one Jira Service Management connection? Yes. One person connects Jira Service Management in Elaichi and shares the connection with a team, and nobody else handles a password or token. Each teammate still signs in to Elaichi as themselves, so every request they read from Jira Service Management is recorded under their own name in the audit log. ### Can I stop an agent from deleting or changing things in Jira Service Management? Yes. Restrictions in Elaichi are set per action, so you decide exactly which Jira Service Management actions a team can use, for example allowing agents to read requests and comments but not download attachments. A blocked action is never shown to Claude, ChatGPT or Cursor at all, so no prompt can reach it. ### What happens to a Jira Service Management connection when someone leaves? When a person is offboarded in Elaichi, their access to Jira Service Management through every AI client ends at once. A Jira Service Management connection shared with a team keeps working for everyone else on it. If you want to remove Jira Service Management entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together. ## All 30 Jira Service Management tools Every tool below is callable through https://api.elaichi.ai/mcp once Jira Service Management is connected, subject to the toolbox it is in and the restrictions on the caller. - **List all Jira Service Management me** (List). Retrieves Jira Service Management instance details like version, build, and links - **List all Jira Service Management accessible resources** (List). Get list of accessible resources in Jira Service Management. Returns id, name, url, scopes, and avatarUrl for each resource. - **List all Jira Service Management service desks** (List). Get all service desks in Jira Service Management. Returns id, projectId, projectName, and projectKey for each service desk. - **Get single Jira Service Management service desk by ID** (Get). Get service desk details by id in Jira Service Management. Returns id, projectId, projectName, projectKey, and self link. - **List all Jira Service Management queues** (List). Get queues for a service desk in Jira Service Management using service_desk_id. Returns id, name, jql, fields, and issueCount (customer request count) for each queue. - **Get single Jira Service Management queue by ID** (Get). Get a specific queue by serviceDeskId and id in Jira Service Management. Returns fields id, name, jql, fields, issueCount, and _links.self. - **List all Jira Service Management users** (List). Get all users in Jira Service Management. Returns a list of users including active, inactive, and deleted Atlassian accounts with fields accountId, accountType, active status, avatarUrls, displayName, and self URL. - **Get single Jira Service Management user by ID** (Get). Get user details by account_id in Jira Service Management. Returns accountId, accountType, active status, applicationRoles, avatarUrls, displayName, emailAddress, groups, self link, and timeZone. Privacy controls apply. - **List all Jira Service Management issue attachments** (List). Get issue attachments by issue id in Jira Service Management. Returns attachment details including id, filename, author, created date, size, mimeType, content URL, and thumbnail URL. - **Get single Jira Service Management issue attachment by ID** (Get). Get metadata for an issue attachment by id in Jira Service Management. Returns author details, filename, mimeType, size, created date, content URL, and thumbnail URL. - **Jira Service Management issue attachments download** (Download). Use this endpoint to download a specific file or attachment from the given file path or URL reference provided by the API. - **List all Jira Service Management issue createmeta** (List). Get create issue metadata including projects and issue types with fields for each issue type in Jira Service Management. Returns projects with id, key, name, avatarUrls, and issue types with id, name, description, iconUrl, and fields. - **List all Jira Service Management search issues** (List). Search issues using JQL in Jira Service Management. Requires jql parameter. Returns issues array with fields like id, key, fields (including status, project, description, comments, attachments). - **Get single Jira Service Management issue by ID** (Get). Get details for a specific issue by id in Jira Service Management. Returns fields like watcher status, attachments, sub-tasks, description, project info, comments, issue links, worklogs, and timetracking. - **List all Jira Service Management queue issues** (List). Get issues in queue with service_desk_id and queue_id in Jira Service Management. Returns fields configured in the queue such as summary, issuetype, duedate, created, reporter, id, and key. - **List all Jira Service Management issue comments** (List). Get all comments for an issue in Jira Service Management by issueIdOrKey. Returns comment id, author, body, created and updated timestamps, and visibility details. - **Get single Jira Service Management issue comment by ID** (Get). Get comment for issue with issue_id_or_key and id in Jira Service Management. Returns author, body, created, id, updateAuthor, updated, and visibility fields. - **List all Jira Service Management field metadata** (List). Get create field metadata for a project and issueTypeId in Jira Service Management. Returns fields with fieldId, name, required status, and operations for creating issues. - **List all Jira Service Management issue type createmeta** (List). Get create metadata issue types for a project in Jira Service Management using projectIdOrKey. Returns issueTypes array with id, name, description, iconUrl, self, and subtask fields. - **List all Jira Service Management organizations** (List). Get a list of organizations in Jira Service Management. Returns organization id, name, and scimManaged status. Use accountId to filter organizations for a specific user. - **Get single Jira Service Management organization by ID** (Get). Get organization details by id in Jira Service Management. Returns id, name, scimManaged fields. Customers can only retrieve organizations they are members of. - **List all Jira Service Management organization users** (List). Get users in organization using organization_id. Returns accountId, emailAddress, displayName, active status, and timeZone for each user in Jira Service Management. - **List all Jira Service Management customers** (List). Get a list of customers for a service desk in Jira Service Management using service_desk_id. Returns accountId, name, emailAddress, displayName, active status, and timeZone for each customer. - **List all Jira Service Management projects** (List). Get a paginated list of projects visible to the user in Jira Service Management. Returns fields including id, key, name, projectCategory, and insight with totalIssueCount and lastIssueUpdateTime. - **Get single Jira Service Management project by ID** (Get). Get project details for project with id in Jira Service Management. Returns fields including assigneeType, avatarUrls, components, description, email, id, insight, issueTypes, key, lead, name, projectCategory, properties, roles, self, simplified, style, url, and versions. - **List all Jira Service Management organization issues** (List). Get customer requests filtered by searchTerm, requestOwnership, requestStatus, approvalStatus, organizationId, serviceDeskId, and requestTypeId in Jira Service Management. Returns issueId, issueKey, summary, createdDate, reporter, requestFieldValues, and currentStatus. - **List all Jira Service Management project statuses** (List). Get all statuses for project using project_id_or_key in Jira Service Management. Returns statuses grouped by issue type including id, name, description, and iconUrl fields. - **List all Jira Service Management statuses** (List). Get a paginated list of statuses filtered by searchString and statusCategory in Jira Service Management. Returns id, name, description, statusCategory, scope, usages, and workflowUsages for each status. - **List all Jira Service Management roles** (List). Use this endpoint to retrieve a list of all global project roles available in your Jira instance. - **Get single Jira Service Management role by ID** (Get). Use this endpoint to fetch detailed information about a specific project role by its ID.