# Jira Service Management MCP > 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. ## Overview - **Category:** industry-titans - **Price:** Free - **Tags:** itsm, service-desk, incident-management, queues, knowledge-base, automation ## Description 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. ## Tools ### get_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 customer request. ### 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 account holders. ### list_knowledge_bases Fetches a list of available knowledge articles for the service desk to guide issue resolution. ### 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 service portal. ### list_requests Gives a summary list of current customer requests, including keys and status, for monitoring purposes. ### list_service_desks Lists all active service desks in the system so you can determine the correct project ID to use. ## Prompt Examples **Prompt:** ``` List all active service desks in JSM. ``` **Response:** ``` I'll fetch the list of available service desks from your Jira Service Management instance. ``` **Prompt:** ``` Show me the latest customer requests. ``` **Response:** ``` I'll retrieve the most recent requests across all service desks for you. ``` **Prompt:** ``` Check the queues for service desk ID '1'. ``` **Response:** ``` I'll look up the current queues and their status for that specific service desk. ``` ## Capabilities ### Monitor Service Desks and Queues List all active service desks to understand the project structure, and check specific queues to gauge ticket backlogs. ### Investigate Specific Requests Get a complete breakdown of any single customer inquiry, including participants, custom fields, and full history. ### Identify Support Assets List all organizations or customers associated with the service desk to pinpoint who needs support. ### Search Documentation Find available knowledge base articles relevant to common issues without manual searching. ### Track Support Intake View all current customer requests and list the types of services offered through the portal. ## 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. ## Benefits - 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. ## How It Works 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. 1. First, your agent uses `list_service_desks` to find the specific project ID you need to work with. 2. Next, it can run `list_queues` or `list_requests` using that service desk ID to get a summary of open items and backlogs. 3. Finally, you prompt your agent to use `get_request` on a specific ticket key to retrieve the full, detailed conversation history. ## Frequently Asked Questions **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.