Ticketing
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.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
30 tools
How to connect
How to connect Jira Service Management to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Jira Service Management once
-
Open Connections, choose Add connection, and pick Jira Service Management.
-
Optionally set Share with to give a team access, then press Connect.
-
Approve it in Jira Service Management. Jira Service Management's own window opens. Whoever approves it decides what this connection can reach.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Jira Service Management to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Jira Service Management to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Jira Service Management through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Support
See what is waiting in a queue
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.
-
IT
Get up to speed before a call
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.
-
Customer success
Check every open request for a customer
Before a renewal conversation, list the people in a customer organization and find the requests they have open across your service desks.
-
Service desk leads
Spot repeat problems across service desks
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.
-
Support
Pull the screenshot from a request
Download the log file or screenshot a customer attached to a request and have it read back to you in plain language.
-
IT
Know who belongs to which organization
List the customer organizations on a service desk and the users in each, so access questions and escalations go to the right people.
Try asking
- “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”
AI tools
Jira Service Management tools for your AI agents
30 tools are ready to call through Elaichi's MCP endpoint the moment you connect Jira Service Management, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Jira Service Management gets you
6 screens from the product, each doing one job for your Jira Service Management account.
The agent
Ask about queues, read answers from live issues.
Plain language questions return real Jira Service Management issues, queues and service desks.
- issues
- queues
- service desks
- attachments
Ask Elaichi to work across your apps.
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
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint reaches Jira Service Management everywhere.
Claude, ChatGPT and Cursor connect over OAuth, with no SDK or shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
30 Jira Service Management tools, no custom code.
Service desks, queues, issues, attachments and users are already mapped to callable methods.
- List all Jira Service Management me
- List all Jira Service Management accessible resources
- List all Jira Service Management service desks
- Get single Jira Service Management service desk by ID
ElaichiToolsToolboxes
Every team gets its own service desk toolbox.
Curate one toolbox per team so support, engineering and IT see different tools.
- Support
- IT operations
- Engineering
- Customer success
ElaichiToolboxesShared connections
Teammates work the queue without a credential.
The connections table shows who connected each site and which teams and members share it.
- Support EMEA
- IT helpdesk
- Engineering escalations
- Customer success
ElaichiConnectionsAudit log
Every issue read is written down.
When, who, what happened, type and resource for each Jira Service Management call.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires, a digest posts back.
Six steps fetch issues, group them, draft a digest, wait for approval, then comment.
Jira Service Management digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch issues
Jira Service Management
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Jira Service Management
Queued
Collections and dashboards
Service desk health, counted not generated.
Four metrics, 14 days of issues created and a team breakdown, refreshed on schedule.
Jira Service Management health
Refreshed 4 minutes ago · every 15 minutes · from the issues collection
Issues
1,284 ↓ 12%
Queues
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Issues created
Last 14 days
By team
Share of activity
Support EMEA 34%
IT helpdesk 27%
Engineering escalations 21%
Customer success 18%
Related connectors
More from the catalog
FAQ
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 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.
Put Jira Service Management in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.