Jira Service Management (JSM) MCP Server for LlamaIndex 10 tools — connect in under 2 minutes
LlamaIndex specializes in data-aware AI agents that connect LLMs to structured and unstructured sources. Add Jira Service Management (JSM) as an MCP tool provider through the Vinkius and your agents can query, analyze, and act on live data alongside your existing indexes.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
import asyncio
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI
async def main():
# Your Vinkius token — get it at cloud.vinkius.com
mcp_client = BasicMCPClient("https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
mcp_tool_spec = McpToolSpec(client=mcp_client)
tools = await mcp_tool_spec.to_tool_list_async()
agent = FunctionAgent(
tools=tools,
llm=OpenAI(model="gpt-4o"),
system_prompt=(
"You are an assistant with access to Jira Service Management (JSM). "
"You have 10 tools available."
),
)
response = await agent.run(
"What tools are available in Jira Service Management (JSM)?"
)
print(response)
asyncio.run(main())
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
About Jira Service Management (JSM) MCP Server
Empower your AI agents with Jira Service Management's leading ITSM platform. This MCP server allows you to list service desks, retrieve customer requests, manage organizations and queues, and access knowledge base articles directly through the Jira JSM API. Ideal for automating IT support and service delivery workflows.
LlamaIndex agents combine Jira Service Management (JSM) tool responses with indexed documents for comprehensive, grounded answers. Connect 10 tools through the Vinkius and query live data alongside vector stores and SQL databases in a single turn — ideal for hybrid search, data enrichment, and analytical workflows.
The Jira Service Management (JSM) MCP Server exposes 10 tools through the Vinkius. Connect it to LlamaIndex in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.
How to Connect Jira Service Management (JSM) to LlamaIndex via MCP
Follow these steps to integrate the Jira Service Management (JSM) MCP Server with LlamaIndex.
Install dependencies
Run pip install llama-index-tools-mcp llama-index-llms-openai
Replace the token
Replace [YOUR_TOKEN_HERE] with your Vinkius token
Run the agent
Save to agent.py and run: python agent.py
Explore tools
The agent discovers 10 tools from Jira Service Management (JSM)
Why Use LlamaIndex with the Jira Service Management (JSM) MCP Server
LlamaIndex provides unique advantages when paired with Jira Service Management (JSM) through the Model Context Protocol.
Data-first architecture: LlamaIndex agents combine Jira Service Management (JSM) tool responses with indexed documents for comprehensive, grounded answers
Query pipeline framework lets you chain Jira Service Management (JSM) tool calls with transformations, filters, and re-rankers in a typed pipeline
Multi-source reasoning: agents can query Jira Service Management (JSM), a vector store, and a SQL database in a single turn and synthesize results
Observability integrations show exactly what Jira Service Management (JSM) tools were called, what data was returned, and how it influenced the final answer
Jira Service Management (JSM) + LlamaIndex Use Cases
Practical scenarios where LlamaIndex combined with the Jira Service Management (JSM) MCP Server delivers measurable value.
Hybrid search: combine Jira Service Management (JSM) real-time data with embedded document indexes for answers that are both current and comprehensive
Data enrichment: query Jira Service Management (JSM) to augment indexed data with live information before generating user-facing responses
Knowledge base agents: build agents that maintain and update knowledge bases by periodically querying Jira Service Management (JSM) for fresh data
Analytical workflows: chain Jira Service Management (JSM) queries with LlamaIndex's data connectors to build multi-source analytical reports
Jira Service Management (JSM) MCP Tools for LlamaIndex (10)
These 10 tools become available when you connect Jira Service Management (JSM) to LlamaIndex via MCP:
get_info
Use for system health monitoring. Retrieves system information for the JSM instance
get_request
g., "SD-123") or ID. Returns full descriptions, participants, and custom field values. Use this for deep investigation of a specific customer inquiry. Retrieves details for a specific customer request
get_service_desk
Returns project information and branding details. Useful for understanding the configuration of a specific support portal. Retrieves details for a specific service desk
list_customers
Useful for identifying support recipients and their account details. Lists all customers for a specific service desk
list_knowledge_bases
Essential for identifying available documentation that might help resolve common customer issues. Lists all knowledge base articles for a specific service desk
list_organizations
Useful for understanding which business entities are being supported and grouping support data by customer. Lists all organizations in JSM
list_queues
g., "All Open", "Unassigned") defined for a service desk. Useful for understanding how tickets are triaged and identifying backlog counts. Lists all queues for a specific service desk
list_request_types
g., "IT Help", "Hardware Request") available in a portal. Useful for understanding the service catalog of a specific team. Lists all request types for a specific service desk
list_requests
Includes request keys, summaries, and current status. Essential for monitoring the support queue and identifying urgent issues. Lists all customer requests
list_service_desks
Returns project keys, names, and IDs. Use this to identify the service desk ID before querying requests or queues. Lists all service desks
Example Prompts for Jira Service Management (JSM) in LlamaIndex
Ready-to-use prompts you can give your LlamaIndex agent to start working with Jira Service Management (JSM) immediately.
"List all active service desks in JSM."
"Show me the latest customer requests."
"Check the queues for service desk ID '1'."
Troubleshooting Jira Service Management (JSM) MCP Server with LlamaIndex
Common issues when connecting Jira Service Management (JSM) to LlamaIndex through the Vinkius, and how to resolve them.
BasicMCPClient not found
pip install llama-index-tools-mcpJira Service Management (JSM) + LlamaIndex FAQ
Common questions about integrating Jira Service Management (JSM) MCP Server with LlamaIndex.
How does LlamaIndex connect to MCP servers?
Can I combine MCP tools with vector stores?
Does LlamaIndex support async MCP calls?
Connect Jira Service Management (JSM) with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect Jira Service Management (JSM) to LlamaIndex
Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.