Jira Service Management MCP. Manage support desks, tickets, and knowledge base articles instantly.
Jira Service Management (JSM) MCP connects your AI agent directly to an enterprise-grade IT service desk. Use this to instantly list all active services, retrieve full customer ticket histories, check support queue backlogs, and search knowledge base articles from one prompt. Automate complex IT operations without ever leaving your client.
Give Claude and any AI agent real-world access
List all active service desks to understand the project structure, and check specific queues to gauge ticket backlogs.
Get a complete breakdown of any single customer inquiry, including participants, custom fields, and full history.
List all organizations or customers associated with the service desk to pinpoint who needs support.
Find available knowledge base articles relevant to common issues without manual searching.
View all current customer requests and list the types of services offered through the portal.
Ask an AI about this
Waiting for input…
What AI agents can do with Jira Service Management (JSM) MCP with 10 Tools
These ten tools allow your agent to perform everything from listing all active service desks to retrieving the full history of any single customer request.
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) MCPGet Info
Retrieves general system information about your JSM instance for health checks.
Get Request
Pulls the complete record, participants list, and custom data fields for a single...
Get Service Desk
Gets project details and branding information for a specific support portal setup.
List Customers
Provides a list of all customers associated with a service desk, helping identify...
List Knowledge Bases
Fetches a list of available knowledge articles for the service desk to guide issue...
List Organizations
Lists all business units within JSM, useful for grouping support data by company.
List Queues
Retrieves the names and status of defined ticket queues, helping track where tickets are stuck in triage.
List Request Types
Lists all types of requests (like 'IT Help' or 'Hardware') available through the...
List Requests
Gives a summary list of current customer requests, including keys and status, for...
List Service Desks
Lists all active service desks in the system so you can determine the correct...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
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 each 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 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
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 CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
The Pain of Context Switching in Support
Right now, handling a single complex ticket means bouncing between tabs. You jump from the main Jira dashboard to check the queue status; you click over to the customer record to see their account history; then you open a separate knowledge base portal just to confirm if the solution is documented anywhere. It's a manual nightmare of copy-pasting IDs and juggling screens.
With this MCP, your agent manages that entire process for you. You ask one question—like, 'What's happening with ticket SD-123?'—and the agent handles all the necessary calls: pulling the service desk info, checking the current queue status, and getting the full request history. You get a single answer, not five tabs to read.
Get Full Service History with get_request
Before this, investigating an issue meant opening a ticket, scrolling back through dozens of comments, and manually checking who participated. You often missed key pieces of context or had to ask three different people for the same data points.
Now, using `get_request` pulls everything together. It gives you the full breakdown of participants and all custom fields in one go. What was once a 20-minute forensic investigation is now an instant summary.
What Jira Service Management MCP does for your AI
Need a better way to handle the flood of customer requests? This MCP gives your AI agent deep access to Jira Service Management's core functions. Instead of clicking through multiple pages just to get a full picture, you can ask your agent to pull together all the necessary data points.
For instance, you can first use it to list available service desks, then check the current queues for backlogs, and finally retrieve the full details of any specific customer request using its ID or key. This capability is crucial when building complex IT support workflows. When you connect this MCP via Vinkius, your agent gains an entire suite of tools, letting you identify support recipients through list_customers or find relevant documentation by listing available knowledge bases, making service delivery automation genuinely practical.
019d75bd-25a7-73f2-8f75-7e93c6c9f481 How to set up Jira Service Management MCP
The bottom line is that instead of opening Jira yourself, you simply tell your agent what data you need, and it handles the necessary steps within the system.
First, your agent uses list_service_desks to find the specific project ID you need to work with.
Next, it can run list_queues or list_requests using that service desk ID to get a summary of open items and backlogs.
Finally, you prompt your agent to use get_request on a specific ticket key to retrieve the full, detailed conversation history.
Who uses Jira Service Management MCP
The Service Desk Analyst who spends half the day manually navigating ticket IDs. The Operations Manager who needs a real-time view of service backlogs without logging into multiple dashboards. Anyone whose job depends on having perfect context from complex support history.
Uses this MCP to quickly pull up the full details of an incoming ticket using get_request, saving time when following up with a customer.
Runs reports on queue status using list_queues and tracks overall service coverage by listing available knowledge bases.
Uses the MCP to list all possible request types or services offered, ensuring documentation matches current offerings.
Benefits of connecting Jira Service Management MCP
Get a full picture of ticket status without clicking through menus. Use list_requests to pull a summary list of open items across the board, letting you spot urgent issues fast.
Stop guessing who owns the support request. By listing organizations with list_organizations, you can group data and understand which business entity needs attention.
When investigating a problem, don't waste time reading entire threads. Use get_request to pull all necessary details—participants, custom fields, everything—in one go.
Stay ahead of backlogs by checking queues with list_queues. You see exactly where tickets are piling up and if the triage process is slowing down.
Build better self-service flows. Use list_knowledge_bases to confirm that documentation exists before sending a customer an article link, ensuring accuracy.
Jira Service Management MCP use cases
Onboarding a New Support Agent
A new agent needs to understand the support landscape. They ask their agent to first run list_service_desks and then check list_request_types. This gives them an immediate overview of what services are offered and which support portals exist, allowing them to guide users accurately.
Auditing a High-Priority Customer Issue
A manager needs to review the history for a critical client. They start by running list_service_desks to confirm the correct project ID, then use that ID with get_request to pull every single detail and participant involved in the ticket.
Identifying Documentation Gaps
A team lead realizes customers are asking about a niche topic. They run list_knowledge_bases for that service desk, see nothing relevant, and know they need to create new documentation immediately.
Checking Backlog Health Before Shift Start
A shift supervisor needs an immediate status report. They ask their agent to run list_queues to see if the 'Unassigned' queue is overflowing, giving them a clear metric of where manpower is needed.
Jira Service Management MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Searching by vague keywords
Asking your agent, 'Find me all tickets about network issues.' This is too broad and might return irrelevant results or fail entirely.
First, use list_service_desks to get the correct project ID. Then, run list_requests with that scope, which gives you a list of keys you can then filter.
Assuming IDs are known
Telling your agent to check Service Desk 'XYZ' when you only know the name. The request will fail because it needs an ID.
Always start by calling list_service_desks to get a list of valid project keys and IDs before trying to query queues or requests.
Trying to find customer details first
Just listing customers without context. You get names, but no idea what service desk they are tied to.
Use list_service_desks first, then use the resulting ID scope when calling list_customers. This ensures you're looking at the right set of users.
When to use Jira Service Management MCP
Use this MCP if your core job involves managing service tickets, tracking backlogs, or synthesizing complex support histories. If you need to know who is asking for help, what services are offered, and what the current status is across multiple internal systems, this is mandatory. Don't use it if you just need a simple list of contacts—you can handle that with basic directory tools. Also, don't rely on this MCP to execute changes; it reads data, but for writing records or changing statuses, you’ll need another toolset. If your only goal is to read the system health, use get_info; if you want a deep dive into an issue, grab get_request.
Frequently asked questions about Jira Service Management MCP
How do I find out which service desks are available using Jira Service Management MCP? +
You use the list_service_desks tool. It immediately returns a list of all active project keys and names, so you know exactly what IDs to reference for your next query.
Can I see how many tickets are waiting in the queue with Jira Service Management MCP? +
Yes, run list_queues. This shows you all defined queues and helps you gauge the current backlog count for a specific service desk.
I need to check customer details; what tool should I use in Jira Service Management MCP? +
Use list_customers. It efficiently lists every customer associated with your designated service desk, helping you identify support recipients and their account data.
How do I get the full history of a ticket using Jira Service Management MCP? +
You must use get_request, providing either the request key or ID. This pulls all necessary details, participants, and custom field values for deep investigation.
Does this MCP help me find documentation? (Jira Service Management) +
Yes, call list_knowledge_bases. It lists all available articles for the service desk, letting you quickly identify if the answer is already documented.