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.

Jira Service Management (JSM) MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Jira Service Management (JSM)
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Jira Service Management (JSM) through the Vinkius — pass the Edge URL in the `mcps` parameter and every Jira Service Management (JSM) tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Jira Service Management (JSM) Specialist",
    goal="Help users interact with Jira Service Management (JSM) effectively",
    backstory=(
        "You are an expert at leveraging Jira Service Management (JSM) tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token — get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Jira Service Management (JSM) "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

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

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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.

When paired with CrewAI, Jira Service Management (JSM) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Jira Service Management (JSM) tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

The Jira Service Management (JSM) MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI 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 CrewAI via MCP

Follow these steps to integrate the Jira Service Management (JSM) MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py — CrewAI auto-discovers 10 tools from Jira Service Management (JSM)

Why Use CrewAI with the Jira Service Management (JSM) MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Jira Service Management (JSM) through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles — one agent researches, another analyzes, a third generates reports — each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass the Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Jira Service Management (JSM) + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Jira Service Management (JSM) MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Jira Service Management (JSM) for raw data, then a second analyst agent cross-references findings and flags anomalies — all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Jira Service Management (JSM), analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Jira Service Management (JSM) tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Jira Service Management (JSM) against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Jira Service Management (JSM) MCP Tools for CrewAI (10)

These 10 tools become available when you connect Jira Service Management (JSM) to CrewAI 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 CrewAI

Ready-to-use prompts you can give your CrewAI 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 CrewAI

Common issues when connecting Jira Service Management (JSM) to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts — check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Jira Service Management (JSM) + CrewAI FAQ

Common questions about integrating Jira Service Management (JSM) MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily — when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.