# Jira Service Management MCP for AI Agents AI Agent Connect > Jira Service Management (JSM) MCP lets your AI agent manage service desks, customer requests, and support queues. It connects directly to your Jira JSM instance so your agent can pull ticket details, browse knowledge bases, and monitor organizational data without you having to switch tabs. ## Overview - **Category:** industry-titans - **Price:** Free - **Endpoint:** https://edge.vinkius.com/vk_preview_tI7XM1qch201nTS7j7hYErs51QO1nPjtHqKTsPsi/ai-agent-connect - **Tags:** itsm, service-desk, incident-management, queues, knowledge-base, automation ## Description Imagine you're trying to handle a sudden surge in support tickets. Usually, that means jumping between different browser tabs, searching for specific customer details, and digging through old documentation to find the right fix. This Connector changes that by giving your AI client a direct line to your Jira Service Management environment. Instead of you doing the legwork, your agent can pull up the status of any request, identify which organization a customer belongs to, and grab the relevant knowledge base articles in seconds. It handles the tedious data gathering so you can focus on actually solving the problems. You can manage your service desks and monitor your queues as easily as sending a chat message. Because Vinkius hosts this Connector, you can plug it into your existing workflow and let your agent take over the heavy lifting of navigating your ITSM setup. It makes the whole process of managing customer requests feel like a conversation rather than a chore. You'll no longer have to remember which desk holds which request type or manually count how many tickets are sitting in the unassigned queue. Your agent keeps that data ready for you whenever you need it. Whether you're managing IT help desks, HR inquiries, or general customer service, this connection ensures your agent always has the context it needs to be helpful. You can quickly see who is asking for help and what they need without digging through nested menus. ## Tools ### list_queues Lists all queues for a specific service desk. Use this to see how tickets are triaged and identify backlog counts. ### list_request_types Lists all request types for a specific service desk. This helps your agent understand the service catalog of your team. ### list_organizations Lists all organizations in JSM. This is useful for grouping support data by business entity. ### get_info Retrieves system information for your JSM instance. Use this to check the overall health of your setup. ### get_request Fetches full descriptions and custom fields for a specific request. This is perfect for deep investigations into customer inquiries. ### get_service_desk Returns project information and branding for a specific desk. It helps you understand the configuration of your support portals. ### list_customers Lists all customers for a specific service desk. Use this to identify support recipients and their account details. ### list_knowledge_bases Lists all knowledge base articles for a specific service desk. It helps your agent find the right documentation to resolve common issues. ### list_requests Lists all customer requests including keys and summaries. Use this to monitor the support queue and identify urgent issues. ### list_service_desks Lists all service desks in your instance. This helps you identify the correct ID before querying requests or queues. ## Prompt Examples **Prompt:** ``` What's the status of our IT Help desk queues? ``` **Response:** ``` I've checked the queues for the IT Help desk. Here is the current status: | Queue Name | Count | Status | | :--- | :--- | :--- | | **All Open** | 42 | ⚠️ High Volume | | **Unassigned** | 12 | Needs Attention | | **Hardware Request** | 8 | Normal | It looks like the **Unassigned** queue needs a quick look. ``` **Prompt:** ``` Can you find the knowledge base articles for the hardware request portal? ``` **Response:** ``` I found the following articles in the hardware service desk: * **Laptop Setup Guide** (Updated 2 days ago) * **Monitor Connection** (Updated last week) * **Keyboard Troubleshooting** (Updated 3 months ago) Would you like me to summarize any of these or find something else? ``` **Prompt:** ``` List the most recent customer requests for us. ``` **Response:** ``` Here are the 5 most recent requests: 1. **REQ-101**: Password Reset — *In Progress* 2. **REQ-102**: New Laptop — *Pending* 3. **REQ-103**: VPN Issue — *High Priority* 4. **REQ-104**: Software Install — *Done* 5. **REQ-105**: Printer Offline — *Open* ``` ## Capabilities ### Pull specific request details Your agent can fetch full descriptions and custom fields for any customer inquiry. ### Browse service desk configs See branding and project info for any specific support portal. ### Identify support recipients Get a full list of customers associated with a specific service desk. ### Access knowledge base articles Retrieve documentation for specific desks to help resolve common issues. ### Monitor support queues Check backlog counts and see how tickets are currently triaged. ### View request types See all available request types in a portal to understand the service catalog. ## Use Cases ### Handling a sudden spike in hardware requests An IT lead asks the agent to list all requests and identify which ones are high priority. The agent uses `list_requests` to summarize the backlog. ### Onboarding a new corporate client A success manager asks the agent to find the organization details and list all customers for the new desk. The agent uses `list_organizations` and `list_customers`. ### Troubleshooting a complex software bug An agent asks for the knowledge base articles for a specific service desk. The agent uses `list_knowledge_bases` to find the fix. ### Auditing service desk configurations An admin asks the agent to show all request types and branding details for the IT Help desk. The agent uses `list_request_types` and `get_service_desk`. ## Benefits - Stop switching between tabs by having your agent pull request details using `get_request` directly into your chat window. - Spot urgent issues faster by letting your agent monitor your backlog and summarize the queue using `list_requests`. - Provide faster answers to customers by having your agent find the right documentation instantly with `list_knowledge_bases`. - Understand your team's service catalog better by using `list_request_types` to see what options are available to users. - Keep a pulse on your team's workload by checking queue sizes with `list_queues` at any time of the day. - Group your data by business entity using `list_organizations` to see which companies need the most support from your team. ## How It Works The bottom line is your agent gains the ability to read and navigate your entire JSM environment on demand. 1. Connect your Jira JSM API credentials to your Vinkius account. 2. Enable the Jira Service Management MCP in your AI client. 3. Ask your agent to check ticket statuses, list customers, or find documentation. ## Frequently Asked Questions **How can the Jira Service Management MCP help my help desk?** It lets your AI agent read your JSM data directly. Your team can ask the agent to find customer info, check ticket statuses, or pull articles without manual searching. **Can I use the Jira Service Management MCP to see my support queues?** Yes, the Connector can list all queues for a specific service desk. This helps you see exactly how many tickets are waiting and where the bottlenecks are. **Does the Jira Service Management MCP work with my knowledge base?** It can list all knowledge base articles for a specific service desk. Your agent can use this to find the right documentation to help solve customer issues. **How do I find customer details using the Jira Service Management MCP?** The Connector can list customers for a specific service desk and list all organizations. This makes it easy for your agent to identify who is asking for help. **Can the Jira Service Management MCP show me all request types?** Yes, it lists all request types for a specific service desk. This helps your agent understand the full service catalog offered by your team. **Is the Jira Service Management MCP good for monitoring ticket volume?** It's great for that. Your agent can list all customer requests to give you a quick summary of the current workload and identify urgent issues. **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.