How to integrate Jira MCP with CrewAI

Connect CrewAI to Jira MCP. Create a new bug in project alpha, assign issue jira-102 to sarah lee, and more using natural language, with authentication handled for you.

Jira logoJira
Oauth2S2s Oauth2Api Key

Jira is Atlassian’s platform for bug tracking, issue tracking, and agile project management. It helps teams organize work, prioritize tasks, and deliver projects efficiently.

127 Tools17 Triggers

Introduction

This guide walks you through connecting Jira to CrewAI using the Composio tool router. By the end, you'll have a working Jira agent that can create and update issues, assign work, manage sprints and boards, log work, and search projects with JQL through natural language commands.

This guide will help you understand how to give your CrewAI agent real control over a Jira account through Composio's Jira MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Jira with

TL;DR

Here's what you'll learn:
  • Get a Composio API key and configure your Jira connection
  • Set up CrewAI with an MCP enabled agent
  • Create a Tool Router session or standalone MCP server for Jira
  • Build a conversational loop where your agent can execute Jira operations

What is CrewAI?

CrewAI is a powerful framework for building multi-agent AI systems. It provides primitives for defining agents with specific roles, creating tasks, and orchestrating workflows through crews.

Key features include:

  • Agent Roles: Define specialized agents with specific goals and backstories
  • Task Management: Create tasks with clear descriptions and expected outputs
  • Crew Orchestration: Combine agents and tasks into collaborative workflows
  • MCP Integration: Connect to external tools through Model Context Protocol

What is the Jira MCP server, and what's possible with it?

The Jira MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Jira account. It provides structured and secure access to your issues, projects, boards, sprints, and teams, so your agent can create issues, update work, plan sprints, manage projects, and coordinate users on your behalf.

  • Issue creation and updates: Have your agent create individual or bulk issues, edit their fields, assign them to teammates, link related work, or delete outdated issues.
  • Comments, attachments, and worklogs: Let the agent add rich text comments, upload or retrieve attachments, record worklogs, and add watchers to issues.
  • Sprint and board planning: Direct your agent to create Scrum or Kanban boards, set up sprints with goals and dates, and create release versions for project milestones.
  • Project setup and oversight: Instruct your agent to list or inspect projects, create new projects from available templates, review dashboards, and retrieve saved filters.
  • Team and access coordination: Have your agent review users, groups, roles, and permissions, then add users to groups or assign people and groups to project roles.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step08 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Python 3.9 or higher
  • A Composio account and API key
  • A Jira connection authorized in Composio
  • An OpenAI API key for the CrewAI LLM
  • Basic familiarity with Python
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

bash
pip install composio crewai crewai-tools[mcp] python-dotenv
What's happening:
  • composio connects your agent to Jira via MCP
  • crewai provides Agent, Task, Crew, and LLM primitives
  • crewai-tools[mcp] includes MCP helpers
  • python-dotenv loads environment variables from .env
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID scopes the session to your account
  • OPENAI_API_KEY lets CrewAI use your chosen OpenAI model
5

Import dependencies

python
import os
from composio import Composio
from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
import dotenv

dotenv.load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")
What's happening:
  • CrewAI classes define agents and tasks, and run the workflow
  • MCPServerHTTP connects the agent to an MCP endpoint
  • Composio will give you a short lived Jira MCP URL
6

Create a Composio Tool Router session for Jira

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["jira"])

url = session.mcp.url
What's happening:
  • You create a Jira only session through Composio
  • Composio returns an MCP HTTP URL that exposes Jira tools
7

Initialize the MCP Server

python
server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users search the internet effectively",
        backstory="You are a helpful assistant with access to search tools.",
        tools=tools,
        verbose=False,
        max_iter=10,
    )
What's Happening:
  • Server Configuration: The code sets up connection parameters including the MCP server URL, streamable HTTP transport, and Composio API key authentication.
  • MCP Adapter Bridge: MCPServerAdapter acts as a context manager that converts Composio MCP tools into a CrewAI-compatible format.
  • Agent Setup: Creates a CrewAI Agent with a defined role (Search Assistant), goal (help with internet searches), and access to the MCP tools.
  • Configuration Options: The agent includes settings like verbose=False for clean output and max_iter=10 to prevent infinite loops.
  • Dynamic Tool Usage: Once created, the agent automatically accesses all Composio Search tools and decides when to use them based on user queries.
8

Create a CLI Chatloop and define the Crew

python
print("Chat started! Type 'exit' or 'quit' to end.\n")

conversation_context = ""

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ["exit", "quit", "bye"]:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_context += f"\nUser: {user_input}\n"
    print("\nAgent is thinking...\n")

    task = Task(
        description=(
            f"Conversation history:\n{conversation_context}\n\n"
            f"Current request: {user_input}"
        ),
        expected_output="A helpful response addressing the user's request",
        agent=agent,
    )

    crew = Crew(agents=[agent], tasks=[task], verbose=False)
    result = crew.kickoff()
    response = str(result)

    conversation_context += f"Agent: {response}\n"
    print(f"Agent: {response}\n")
What's Happening:
  • Interactive CLI Setup: The code creates an infinite loop that continuously prompts for user input and maintains the entire conversation history in a string variable.
  • Input Validation: Empty inputs are ignored to prevent processing blank messages and keep the conversation clean.
  • Context Building: Each user message is appended to the conversation context, which preserves the full dialogue history for better agent responses.
  • Dynamic Task Creation: For every user input, a new Task is created that includes both the full conversation history and the current request as context.
  • Crew Execution: A Crew is instantiated with the agent and task, then kicked off to process the request and generate a response.
  • Response Management: The agent's response is converted to a string, added to the conversation context, and displayed to the user, maintaining conversational continuity.

Complete Code

Here's the complete code to get you started with Jira and CrewAI:

python
from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter
from composio import Composio
from dotenv import load_dotenv
import os

load_dotenv()

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

# Initialize Composio and create a session
composio = Composio(api_key=COMPOSIO_API_KEY)
session = composio.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["jira"],
)
url = session.mcp.url

# Configure LLM
llm = LLM(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY"),
)

server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users with internet searches",
        backstory="You are an expert assistant with access to Composio Search tools.",
        tools=tools,
        llm=llm,
        verbose=False,
        max_iter=10,
    )

    print("Chat started! Type 'exit' or 'quit' to end.\n")

    conversation_context = ""

    while True:
        user_input = input("You: ").strip()

        if user_input.lower() in ["exit", "quit", "bye"]:
            print("\nGoodbye!")
            break

        if not user_input:
            continue

        conversation_context += f"\nUser: {user_input}\n"
        print("\nAgent is thinking...\n")

        task = Task(
            description=(
                f"Conversation history:\n{conversation_context}\n\n"
                f"Current request: {user_input}"
            ),
            expected_output="A helpful response addressing the user's request",
            agent=agent,
        )

        crew = Crew(agents=[agent], tasks=[task], verbose=False)
        result = crew.kickoff()
        response = str(result)

        conversation_context += f"Agent: {response}\n"
        print(f"Agent: {response}\n")

Conclusion

You now have a CrewAI agent connected to Jira through Composio's Tool Router. The agent can perform Jira operations through natural language commands.

Next steps:

  • Add role-specific instructions to customize agent behavior
  • Plug in more toolkits for multi-app workflows
  • Chain tasks for complex multi-step operations
TOOLS & TRIGGERS

Supported Tools and Triggers

Every Jira action and event your agent gets out of the box.

Add Attachment

Uploads and attaches a file to a Jira issue.

Add Comment

Adds a comment using Atlassian Document Format (ADF) for rich text to an existing Jira issue.

Add Field to Screen Tab

Adds a Jira field to a screen tab.

Add Users to Project Role

Adds users or groups to a Jira project role.

Add User to Group

Adds a user to a Jira group.

Add Watcher to Issue

Adds a user to an issue's watcher list by account ID.

Add Worklog

Adds a worklog entry to a Jira issue to record time spent.

Analyse Jira Expression

Analyses Jira expressions for syntax validation, type checking, and complexity analysis.

Assign Issue

Assigns a Jira issue to a user, default assignee, or unassigns; supports email/name lookup.

Bulk Create Issues

Creates multiple Jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.

Bulk Move Issues

Submits an asynchronous bulk move of Jira issues using destination project, issue type, and optional parent mappings.

Check User Permissions

Check user permissions for global and project-level operations in Jira.

Create Board

Creates a new Jira board (kanban, scrum, or agility) with optional filter and location configuration.

Create Component

Create a component in a Jira project.

Create Custom Field Context

Create a project and issue-type context for a Jira custom field.

Create Filter

Create a Jira saved filter with a required name and optional JQL query.

Create Group

Creates a new group in Jira with the specified name.

Create Issue

Creates a Jira issue in a specified project with standard and additional custom fields, including fields required by the project.

Link Issues

Links two Jira issues using a specified link type with optional comment.

Create Issue Type

Create a global Jira issue type.

Get JQL Autocomplete Data

Retrieves JQL autocomplete reference data including reserved words, field names, and function names.

Create Project

Creates a new Jira project with required lead, template, and type configuration.

Create Screen

Create a Jira screen with a default field tab.

Create Screen Scheme

Create a Jira screen scheme with optional operation-specific screens.

Create Sprint

Creates a new sprint on a Jira board with optional start/end dates and goal.

Create Version

Creates a new version for releases or milestones in a Jira project.

Delete Attachment

Permanently deletes an attachment from Jira by its ID.

Delete Comment

Deletes a specific comment from a Jira issue using its ID and the issue's ID/key; requires user permission to delete comments on the issue.

Delete Issue

Permanently deletes a Jira issue by ID or key, optionally deleting its subtasks as well.

Delete Issue Link

Permanently deletes a link between two Jira issues by link identifier.

Delete Statuses

Deletes one to fifty Jira workflow statuses by identifier.

Delete Version

Deletes a Jira version and optionally reassigns its issues.

Delete Worklog

Deletes a worklog from a Jira issue with estimate adjustment options.

Edit Issue

Updates a Jira issue with field values and operations, with direct field parameters taking precedence over fields.

Evaluate Jira Expression

Tool to evaluate Jira expressions using the enhanced search API.

Bulk Fetch Issues

Tool to bulk fetch multiple Jira issues by their IDs or keys (max 100 per call).

Find Users 2

Searches Jira users by query string, account ID, or property, returning one page of matches.

Find Users For Picker

Find users for picker components by matching query against user attributes like display name and email.

Find Users With Permissions

Find users who hold every requested permission for a Jira issue or project.

Get All Groups

Retrieves a page of groups from the Jira instance.

Get All Issue Type Schemes

Retrieves all Jira issue type schemes with optional filtering and pagination.

Get all projects

Retrieves a page of visible Jira projects with server-side filtering and pagination.

Get Issue Statuses

Retrieves all issue statuses associated with workflows from Jira.

Get All Users

Retrieves all users from the Jira instance including active, inactive, app accounts, and system accounts, with pagination support.

Get Attachment

Retrieves the binary content of a Jira attachment by ID.

Get Attachment Meta

Tool to retrieve Jira attachment settings including upload limits and enabled status.

Get Comment

Retrieves a specific comment by ID from a Jira issue with optional expansions.

Get Component

Tool to retrieve components from Jira projects with search and filtering.

Get Create Field Metadata for Issue Type

Tool to retrieve field metadata for a specific issue type in a project.

Get Current User

Retrieves detailed information about the currently authenticated Jira user.

Get Dashboard Item Properties

List property keys for a dashboard item or retrieve one property's value.

Get Dashboards

Tool to list and search Jira dashboards visible to the current user.

Get Favorite Filters

Tool to retrieve favorite filters for the current user.

Get fields

Retrieves Jira issue field metadata to discover field IDs and names, with optional custom-field and project-scope filtering or creation fields for a project and issue type.

Get custom fields paginated

Tool to retrieve Jira fields in pages.

Get Filter

Retrieves a specific Jira saved filter by ID, including its JQL and sharing metadata, to reuse in subsequent searches.

Get Group

Retrieves details of a specific Jira group by name or ID.

Get Service Management Info

Retrieves runtime information for the Jira Service Management instance.

Get Issue

Retrieves a Jira issue by ID or key with customizable fields and expansions.

Get Issue Changelogs

Return one oldest-first page of an issue's complete change history.

Get Issue Edit Meta

Tool to retrieve editable fields for a Jira issue.

Get Issue Link Types

Retrieves all configured issue link types from Jira.

Get issue picker

Tool to get issue picker suggestions from Jira.

Get Issue Property

Retrieves a custom property from a Jira issue by key.

Get Issue Resolutions

Retrieves Jira issue resolution types.

Get Issue Type

Retrieves one Jira issue type by its unique ID.

Get issue types

Retrieves all Jira issue types available to the user using the modern API v3 endpoint; results vary based on 'Administer Jira' global or 'Browse projects' project permissions.

Get Issue Watchers

Retrieves watcher information for a Jira issue, subject to Jira permissions.

Get JQL autocomplete reference data

Tool to retrieve JQL autocomplete reference data.

Get JQL autocomplete suggestions

Tool to get JQL field auto-complete suggestions.

Get My Permissions

Tool to retrieve the user's permissions in Jira.

Get User Locale Preference

Tool to retrieve the locale preference of the currently authenticated Jira user.

Get Permissions

Tool to retrieve all available Jira permissions.

Get Permitted Projects

Tool to retrieve projects where the current user has specific permissions.

Get Project

Retrieves details of a Jira project by its ID or key.

Get Project Permission Scheme

Return the permission scheme assigned to a Jira project.

Get Project Roles

Retrieves all available roles for a Jira project.

Get Project Templates

Lists project template keys from a fixed catalog, optionally filtered by project type.

Get Project Type

Retrieves detailed information about a specific Jira project type by its key.

Get Project Versions

Retrieves all versions for a Jira project with optional expansion.

Get Recent Projects

Retrieves a list of projects recently accessed by the authenticated user.

Get Issue Remote Links

Retrieves links from a Jira issue to external resources.

Get Server Info

Tool to retrieve Jira instance server information.

Get Service Desk Request Type Fields

Tool to retrieve JSM request type field metadata for filling out portal requests.

Get Sprint

Retrieves detailed information about a specific sprint by its ID.

Get System Avatars

Tool to retrieve all system avatars for a specific type (issuetype, project, user, or priority).

Get Transitions

Retrieves available workflow transitions for a Jira issue.

Get Universal Avatar Type Owner

Tool to retrieve all avatars (system and custom) for a specific type and entity in Jira.

Get Universal Avatar View Type

Tool to retrieve the default avatar image for a specific type (project, issuetype, or priority) from Jira.

Get User Groups

Retrieves all groups for a specific Jira user by account ID.

Get Avatar Image

Tool to retrieve a specific avatar image by type and ID from Jira.

Get Issue Votes

Fetches voting details for a Jira issue; requires voting to be enabled in Jira's general settings.

Get Worklogs

Retrieves worklogs for a specified Jira issue.

Get Worklogs By IDs

Retrieve full worklog records for a list of Jira worklog IDs.

List Assignable Users

Search a page of users eligible for assignment in a Jira project or issue, optionally evaluating a workflow transition.

List Boards

Retrieves paginated Jira boards with filtering and sorting options.

List Comments by IDs

Tool to retrieve multiple comments by their IDs in a single request.

List Custom Field Context Default Values

Return one page of custom field defaults grouped by context and issue type.

List Custom Field Context Issue Type Mappings

Return one page of issue type mappings for a Jira custom field's contexts.

List Custom Field Context Options

Return one page of options configured for a custom field context.

List Custom Field Context Project Mappings

Return one page of project mappings for a Jira custom field's contexts.

List Custom Field Contexts

Return one page of contexts for a Jira custom field.

List Dashboard Gadgets

Lists gadgets on a Jira dashboard, optionally filtered by type, URI, or ID.

List Field Scheme Fields

List fields via an experimental endpoint requiring Jira field-schemes beta enrollment.

List Jira Filters

Tool to search and list Jira saved filters (saved searches) visible to the current user.

List Group Members

Return one page of users belonging to a Jira group.

List Groups (Picker)

Tool to search and list groups using Jira's picker endpoint.

List Issue Comments

Retrieves paginated comments from a Jira issue with optional ordering.

List Issue Forms

List basic metadata for forms attached to a Jira issue.

List Issue Property Keys

Lists the keys and URLs of properties defined on a Jira issue.

List Project Types

Retrieves all Jira project types available in the instance.

List Sprints

Retrieves paginated sprints from a Jira board with optional state filtering.

List Updated Worklogs

Return one updated-worklog checkpoint page.

Move Issues to Sprint

Moves one or more Jira issues to a specified active sprint.

Parse JQL Queries

Parse and validate JQL queries, returning their abstract syntax tree structure along with any errors or warnings.

Remove User from Group

Removes a user from a Jira group.

Remove User from Project Role

Removes a user or group from a project role.

Remove Watcher from Issue

Removes a user from an issue's watcher list by account ID.

Search Approximate Count

Count issues matching a JQL query using approximate count endpoint.

Search Dashboards

Tool to search for Jira dashboards with filtering, sorting, and pagination support.

Search Issues Using JQL (GET)

Searches Jira issues using JQL with token pagination and field selection.

Search issues

Searches Jira issues using structured filters or raw JQL, defaulting to issues updated in the last 30 days when no criteria are supplied.

Send Notification for Issue

Sends a customized email notification for a Jira issue.

Set Issue Property

Sets a named JSON property on a Jira issue.

Transition Issue

Transitions a Jira issue to a different workflow state, with support for transition name lookup and user assignment by email.

Update Comment

Updates an existing Jira comment by replacing its text content, with optional visibility restrictions.

Who Am I

Returns Jira connection identity information.

FAQ

Frequently asked questions

With a standalone Jira MCP server, the agents and LLMs can only access a fixed set of Jira tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Jira and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. CrewAI fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Jira tools.

Yes, absolutely. You can configure which Jira scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Jira data and credentials are handled as safely as possible.

Start with Jira.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Jira tool your agent needs.Free to start.

Start building