Jira Service Management (JSM) MCP. Get ticket data and service structure via your AI agent.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Jira Service Management (JSM) MCP Server connects your AI client to your service desk data. It lets you read customer requests, check queue status, list service desks, and search knowledge bases directly via the Jira JSM API.
Use it to automate IT support tasks, triage tickets, or pull up deep details on any service inquiry.
What your AI agents can do
Get info
Retrieves general system information for the JSM instance, useful for monitoring system health.
Get request
Fetches full details for a specific customer request, including participants and custom field values.
Get service desk
Retrieves project details and branding information for a specific support portal.
The get_info tool retrieves general operational information about the JSM instance.
The get_request tool fetches complete information for a single customer request, including participants and custom fields.
The get_service_desk tool provides details and branding information for a specific support portal.
The list_customers tool pulls a list of all known customers attached to a service desk.
The list_knowledge_bases tool fetches a list of documentation available for a specific service desk.
The list_organizations tool retrieves all business organizations managed within JSM.
The list_queues tool lists defined queues for a service desk, showing where tickets are being triaged.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 Compatible Gemini Waiting for input…
Jira Service Management (JSM) MCP Server: 10 Tools
Use these 10 tools to programmatically interact with your Jira Service Management data, allowing your AI agent to automate service desk tasks.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Jira Service Management (JSM) on Vinkius019d75bdget info
Retrieves general system information for the JSM instance, useful for monitoring system health.
019d75bdget request
Fetches full details for a specific customer request, including participants and custom field values.
019d75bdget service desk
Retrieves project details and branding information for a specific support portal.
019d75bdlist customers
Lists all customers associated with a specific service desk for account identification.
019d75bdlist knowledge bases
Lists all available knowledge base articles for a given service desk, helping find solutions.
019d75bdlist organizations
Lists all business organizations supported by JSM, useful for data grouping.
019d75bdlist queues
Lists all queues defined for a service desk, helping track ticket status and backlogs.
019d75bdlist request types
Lists all available request types (like 'IT Help' or 'Hardware Request') in a service catalog.
019d75bdlist requests
Lists summaries and statuses for all customer requests, essential for monitoring the general support queue.
019d75bdlist service desks
Returns project keys, names, and IDs, allowing you to identify the correct service desk for subsequent queries.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Jira Service Management (JSM), then connect any of our 4,800+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,800+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Jira Service Management. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Manually gathering ticket data takes way too much time.
Today, if you need a full picture of a customer issue, you're clicking through Jira's web interface: checking the ticket summary, opening the activity feed, looking at the associated user records, and cross-referencing the knowledge base link. You spend minutes just moving between tabs and copying IDs to build a single status report.
With this MCP server, your agent handles the clicks. You ask for the status of a ticket, and the agent uses `get_request` to pull every detail—the status, the history, the participants—into one structured response. You get the full context instantly.
Jira Service Management (JSM) MCP Server
The `list_service_desks` tool eliminates the need to guess which project key or ID you're working with. You simply ask for a list of all available service desks, and the agent gets the accurate IDs required to move forward.
Now your agent can reliably target the right support portal every single time. It's not just data access; it's reliable data access, period.
What you can do with this MCP connector
Jira Service Management (JSM) MCP Server connects your AI client directly to your service desk data. You can read customer requests, check queue status, list service desks, and search knowledge bases without writing complex API calls. This lets your agent automate IT support tasks, triage tickets, or pull up deep details on any service inquiry.
Inspect System Healthget_info retrieves general operational information about the JSM instance.
Service Desk Configurationlist_service_desks returns project keys, names, and IDs, letting you identify the right service desk for later queries. get_service_desk provides details and branding info for a specific support portal.
Customer and Organization Managementlist_organizations retrieves all business organizations managed within JSM. list_customers pulls a list of all known customers attached to a service desk for account identification.
Request Triage and Statuslist_requests lists summaries and statuses for all customer requests, letting you monitor the general support queue. list_queues lists defined queues for a service desk, showing where tickets are being triaged. get_request fetches complete information for a single customer request, including participants and custom field values. list_request_types lists all available request types, like 'IT Help' or 'Hardware Request', in a service catalog.
Knowledge and Documentationlist_knowledge_bases fetches a list of documentation available for a specific service desk, helping find solutions.
Core Data Retrievallist_service_desks returns project keys, names, and IDs, allowing you to identify the correct service desk for subsequent queries. list_organizations retrieves all business organizations managed within JSM.
019d75bd-25a7-73f2-8f75-7e93c6c9f481 
How Jira Service Management (JSM) MCP Works
- 1 You prompt your AI client to investigate a customer issue (e.g., 'Find the status of ticket SD-123').
- 2 The agent determines it needs ticket data and calls the
get_requesttool, passing the ticket ID. - 3 The server executes the API call and returns a detailed JSON object with the ticket's full description, participants, and custom fields to your agent.
The bottom line is, your agent gets the exact data it needs from Jira, without needing to write any API code itself.
Who Is Jira Service Management (JSM) MCP For?
This is for the Ops Engineer who gets bogged down in Jira dashboards, spending hours clicking through tickets just to piece together a status report. It’s for the Support Manager who needs to know instantly if the 'IT Help' queue is backed up. It’s for the IT Director who needs to audit service delivery without logging into the web UI.
Uses get_request to pull up every detail on a specific ticket, quickly confirming who was involved or what custom fields are missing.
Uses list_queues and list_requests to monitor ticket volume, spot backlogs, and ensure the team is prioritizing the right work.
Uses list_service_desks and list_organizations to map out the entire support structure and understand which business unit owns which support portal.
What Changes When You Connect
- Deep Dive into Tickets: Use
get_requestto pull more than just the summary. You get the full history, every participant, and custom field data for deep investigations. - Know Your Scope: Before querying tickets, run
list_service_desksto find the correct project key or ID. This prevents bad calls and ensures your agent targets the right support portal. - Monitor Backlogs: Use
list_requeststo get a quick overview of all open tickets, or uselist_queuesto see exactly which triage queues are building up with unassigned work. - Map Your Structure: Run
list_organizationsandlist_customerstogether. This lets your agent understand which business unit is responsible for which customer account, making reporting accurate. - Find Answers Fast: Need documentation?
list_knowledge_basespulls the list of articles, letting your agent guide the user to the right self-help answer. - Understand Service Offerings: Call
list_request_typesto see the full service catalog, letting your agent know what kind of requests the team can actually handle.
Real-World Use Cases
Investigating a Single, Complex Ticket
A support agent gets a call about a strange error. Instead of reading through the ticket history manually, the agent tells their AI client to run get_request on the ticket ID. The agent instantly gets all participants and custom fields, letting them confirm the required steps without wasting time.
Auditing the Entire Support Backlog
The Service Desk Manager needs to know the total volume of unassigned work. They instruct their agent to first run list_service_desks to find the correct scope, then call list_requests and list_queues to get a real-time count and status of all pending tickets.
Onboarding a New Support Team
The Ops Engineer needs to map out the entire support ecosystem. They run list_organizations to see all business units, then use list_customers for each one, and finally list_knowledge_bases to see what documentation exists for that unit.
Checking Service Availability
A developer wants to see if a specific service offering is even available. They ask their agent to run list_request_types and list_service_desks to confirm the service catalog and the operational scope.
The Tradeoffs
Trying to find a ticket ID manually
A user starts by just asking, 'What's wrong with the support queue?' and the agent just replies with a vague list of services, forcing the user to start over and hunt for the correct ticket ID.
→
First, run list_service_desks to narrow the scope. Then, use list_requests to get a summary list and find the key ID. Finally, call get_request with the specific ID for all details.
Assuming all data is in one place
The agent tries to get customer account data and ticket status simultaneously, resulting in an error because the two types of data are managed by different tools.
→
Separate the calls. First, run list_customers to get the account details. Then, run get_request using the customer ID to pull the ticket status. The AI client chains the data correctly.
Ignoring the service structure
The agent tries to query a queue ID that belongs to a different service desk, leading to an empty or irrelevant result set.
→
Always start by calling list_service_desks to confirm the correct project ID. Then, use that ID when calling list_queues or get_service_desk.
When It Fits, When It Doesn't
Use this server if your primary need is reading, listing, or auditing structured service desk data (tickets, users, documentation). It's perfect for building stateful workflows like 'Investigate Customer Issue' or 'Audit Backlog Status.'
Don't use this if you need to create a ticket, update a field, or send a message. This server is read-only for operational data. For those actions, you'll need a different API integration (e.g., a dedicated write-access MCP server). If you just need to know what data exists, but don't care about its actual content, an external database listing tool might suffice, but this is the most complete source of truth for Jira Service Management.
Common Questions About Jira Service Management (JSM) MCP
How do I use the `list_requests` tool to see all open tickets? +
The list_requests tool fetches a list of summaries and statuses across the service desk. This is the best starting point for monitoring the general health of the queue.
What is the difference between `list_requests` and `get_request`? +
The difference is scope. list_requests gives you a high-level summary (keys and statuses) for many tickets. get_request requires a specific ID and gives you the complete, deep-dive record for one ticket.
Does `list_service_desks` help me find the right project ID? +
Yes, it does. list_service_desks returns the project keys, names, and IDs. This is critical because most other tools need the correct service desk ID to function properly.
Can I use `list_customers` to see billing information? +
No. list_customers only lists support recipients and their account details within the service desk context. It doesn't provide billing or financial records.
How do I check the queue status with `list_queues`? +
Running list_queues lists all defined queues for a service desk, showing where tickets are being triaged. This helps identify backlogs and understand the workflow structure.
How do I use `list_organizations` to understand customer groupings? +
It lists all organizations within JSM. This helps you group support data by business entity, letting your agent know which customers belong together for better context.
What is the purpose of the `get_service_desk` tool? +
It retrieves details for a specific service desk. You use this to understand the portal's configuration and branding before automating support tasks.
Can I use `list_knowledge_bases` to find relevant articles for a ticket? +
It lists all available knowledge base articles for a service desk. Your agent can use this list to pull documentation and suggest articles while resolving a customer request.
How do I get Jira JSM API credentials? +
You need your Jira instance domain (e.g., acme.atlassian.net), your account email, and an API Token. You can generate an API Token in your Atlassian Account Settings under Security > API Token.
Can I see requests from all service desks? +
The list_requests tool allows you to retrieve customer requests across your Jira Service Management instance, subject to your account permissions.
Are knowledge base articles supported? +
Yes, you can list knowledge base articles for a specific service desk using the list_knowledge_bases tool.
Multi-server workflows that include Jira Service Management (JSM) MCP
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.