How to Use the Jira Service Management (JSM) MCP in LlamaIndex

Q: How do I configure LlamaIndex to query my Jira Service Management (JSM) queues?

Initialize the BasicMCPClient with your endpoint URL and wrap it in McpToolSpec. You then call totoollistasync to expose tools like listqueues to your LlamaIndex FunctionAgent.

Q: Can I use LlamaIndex to index Jira Service Management (JSM) knowledge base articles?

Yes. Use listknowledgebases to pull the active article directory, then load the content into a LlamaIndex document store. This lets your agent run semantic searches across your support documentation.

Q: Does this Jira Service Management (JSM) MCP Server support asynchronous execution in LlamaIndex?

Yes. The tools support asynchronous execution via totoollistasync, allowing your agent to run concurrent calls to listrequests and listcustomers without blocking your main application loop.

Q: How do I filter which MCP tools are exposed to my LlamaIndex agent?

You can pass an allowedtools list during initialization. This lets you restrict your agent to specific operations, like only allowing getrequest while hiding system tools.

Index Jira Service Management queues and requests directly into LlamaIndex for semantic search.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Jira Service Management (JSM) MCP to LlamaIndex

Create your Vinkius account to connect Jira Service Management (JSM) to LlamaIndex and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Jira Service Management (JSM) with LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Convert ticket histories into searchable indexes

`list_requests` pulls your live customer ticket summaries and status codes directly into your LlamaIndex pipeline. The framework indexes these records into your vector store, turning raw support history into a searchable knowledge base. Your agent queries this index to find historical resolutions. To keep the context accurate, `get_request` retrieves the full descriptions and custom field values for deep indexing. This ensures your semantic search results are grounded in actual historical data rather than hallucinated responses.

Search across support portals and organizations

`list_organizations` retrieves the business entities associated with your active support contracts. LlamaIndex uses this data to segment your search indexes, allowing your agent to run queries restricted to specific customer groups. By using `list_service_desks`, the framework mapping matches specific project keys to their respective document stores. This structure keeps your multi-tenant support data organized and searchable.

Build RAG pipelines with this MCP Server

`list_knowledge_bases` lists all documentation articles configured for your service desks. LlamaIndex reads these links and combines them with live ticket data, creating a unified context window for your agent. The agent uses `list_queues` via the MCP connection to monitor active backlogs and pull relevant knowledge base context before suggesting a fix. This keeps your automated triage grounded in your existing documentation.

Setup guide

Set up Jira Service Management (JSM) MCP in LlamaIndex

Prerequisites

Python 3.10+ installed
llama-index-tools-mcp package
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install llama-index-tools-mcp llama-index-llms-openai. The MCP tools package provides BasicMCPClient and McpToolSpec.
2

Connect with BasicMCPClient
Point BasicMCPClient to your Vinkius endpoint URL. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. Supports SSE and Streamable HTTP transports.
3

Convert to LlamaIndex tools
Call mcp_tool_spec.to_tool_list_async() to convert all Jira Service Management (JSM) MCP tools into native FunctionTool objects that any LlamaIndex agent can use.
4

Run with any LLM
Create a FunctionAgent with the tools and your preferred LLM. Swap OpenAI for Anthropic, Gemini, or any LlamaIndex-supported provider.

agent.py

from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

# Connect to the MCP
mcp_client = BasicMCPClient(
    "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)
mcp_tool_spec = McpToolSpec(client=mcp_client)

# Convert MCP tools to LlamaIndex tools
tools = await mcp_tool_spec.to_tool_list_async()

# Create and run the agent
agent = FunctionAgent(
    tools=tools,
    llm=OpenAI(model="gpt-4o"),
    system_prompt="You have access to Jira Service Management (JSM) tools.",
)
response = await agent.run("List recent Jira Service Management (JSM) data")

Get your connection token →

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.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Jira Service Management (JSM) now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Jira Service Management (JSM) MCP in LlamaIndex

Initialize the `BasicMCPClient` with your endpoint URL and wrap it in `McpToolSpec`. You then call `to_tool_list_async` to expose tools like `list_queues` to your LlamaIndex `FunctionAgent`.

Yes. Use `list_knowledge_bases` to pull the active article directory, then load the content into a LlamaIndex document store. This lets your agent run semantic searches across your support documentation.

Yes. The tools support asynchronous execution via `to_tool_list_async`, allowing your agent to run concurrent calls to `list_requests` and `list_customers` without blocking your main application loop.

You can pass an `allowed_tools` list during initialization. This lets you restrict your agent to specific operations, like only allowing `get_request` while hiding system tools.

Absolutely. The MCP Server runs in an isolated V8 sandbox that processes your service desk data, customer lists, and ticket descriptions ephemerally. No data is stored permanently on Vinkius, and all communication uses TLS encryption.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript