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

Q: How do agents handle Jira Service Management (JSM) request types?

Agents use listrequesttypes to understand the current service catalog. They can then tailor their response or escalation path based on the specific type of help requested.

Deploy autonomous agent crews to monitor and resolve issues via Jira Service Management (JSM) integration.

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 CrewAI

Create your Vinkius account to connect Jira Service Management (JSM) to CrewAI 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 CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Collaborative support crews in CrewAI

Assign specialized agents to handle different parts of the support lifecycle. One agent calls `list_requests` to identify new tickets, while another uses `get_request` to draft a response. This setup allows your agents to share context and work as a team. They handle the repetitive triage so your human staff doesn't have to.

Queue management automation

Let your agents monitor `list_queues` to keep track of backlog counts. They can flag bottlenecks and report them back to your team leads. It removes the need for manual check-ins. Your agents stay on top of the queue and ensure no ticket sits unassigned for too long.

Documentation-backed resolution

Equip your agents with `list_knowledge_bases` to find relevant articles for customer issues. They can suggest solutions based on existing company documentation. This speeds up resolution times by putting the right info in front of the agent immediately. It keeps your support quality high and consistent across the board.

Setup guide

Set up Jira Service Management (JSM) MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Jira Service Management (JSM) tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Jira Service Management (JSM) Analyst",
    goal="Access and analyze Jira Service Management (JSM) data via MCP.",
    backstory="Expert analyst with direct Jira Service Management (JSM) access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Jira Service Management (JSM) transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Jira Service Management (JSM) Analyst",
        goal="Access and analyze Jira Service Management (JSM) data via MCP.",
        backstory="Expert analyst with direct Jira Service Management (JSM) access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Jira Service Management (JSM) transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

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 CrewAI

Simply pass the Vinkius MCP endpoint URL into your agent's configuration. The framework will automatically detect and register the available tools for your crew.

Yes. CrewAI provides shared memory between agents in a crew. Any information gathered via `get_request` or `list_customers` becomes available to other agents in the same session.

All tool executions happen inside isolated, ephemeral environments. Your Jira credentials are never exposed to the agents, and the session is destroyed once the crew finishes.

Agents use `list_request_types` to understand the current service catalog. They can then tailor their response or escalation path based on the specific type of help requested.

The agents only interact with ticket metadata, customer profiles, and queue statistics. All data is protected by strict role-based access control and is never persisted outside your authorized workflow.

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