# How to integrate Jira MCP with Autogen

```json
{
  "title": "How to integrate Jira MCP with Autogen",
  "toolkit": "Jira",
  "toolkit_slug": "jira",
  "framework": "AutoGen",
  "framework_slug": "autogen",
  "url": "https://composio.dev/toolkits/jira/framework/autogen",
  "markdown_url": "https://composio.dev/toolkits/jira/framework/autogen.md",
  "updated_at": "2026-05-06T08:17:11.418Z"
}
```

## Introduction

This guide walks you through connecting Jira to AutoGen using the Composio tool router. By the end, you'll have a working Jira agent that can create a new bug in project alpha, assign issue jira-102 to sarah lee, add comment to ticket jira-207 with update through natural language commands.
This guide will help you understand how to give your AutoGen 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

- [ChatGPT](https://composio.dev/toolkits/jira/framework/chatgpt)
- [OpenAI Agents SDK](https://composio.dev/toolkits/jira/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/jira/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/jira/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/jira/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/jira/framework/codex)
- [Cursor](https://composio.dev/toolkits/jira/framework/cursor)
- [VS Code](https://composio.dev/toolkits/jira/framework/vscode)
- [OpenCode](https://composio.dev/toolkits/jira/framework/opencode)
- [OpenClaw](https://composio.dev/toolkits/jira/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/jira/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/jira/framework/cli)
- [Google ADK](https://composio.dev/toolkits/jira/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/jira/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/jira/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/jira/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/jira/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/jira/framework/crew-ai)

## TL;DR

Here's what you'll learn:
- Get and set up your OpenAI and Composio API keys
- Install the required dependencies for Autogen and Composio
- Initialize Composio and create a Tool Router session for Jira
- Wire that MCP URL into Autogen using McpWorkbench and StreamableHttpServerParams
- Configure an Autogen AssistantAgent that can call Jira tools
- Run a live chat loop where you ask the agent to perform Jira operations

## What is AutoGen?

Autogen is a framework for building multi-agent conversational AI systems from Microsoft. It enables you to create agents that can collaborate, use tools, and maintain complex workflows.
Key features include:
- Multi-Agent Systems: Build collaborative agent workflows
- MCP Workbench: Native support for Model Context Protocol tools
- Streaming HTTP: Connect to external services through streamable HTTP
- AssistantAgent: Pre-built agent class for tool-using assistants

## 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 Jira projects, so your agent can perform actions like creating issues, managing sprints, commenting on tasks, assigning work, and tracking releases on your behalf.
- Automated issue creation and tracking: Let your agent create new bugs, tasks, or stories, and keep tabs on issues across your Jira projects.
- Collaborative commenting and updates: Have your agent add rich-text comments or attachments to issues, keeping team communication seamless and up to date.
- Effortless assignment and watcher management: Easily assign issues to teammates or add watchers, ensuring everyone stays in the loop and accountable.
- Sprint and release planning: Empower your agent to create sprints, manage boards, and organize project milestones or versions for agile teams.
- Issue linking and bulk operations: Direct your agent to link related issues or perform bulk creation of tasks, streamlining project workflows and dependencies.

## Supported Tools

| Tool slug | Name | Description |
|---|---|---|
| `JIRA_ADD_ATTACHMENT` | Add Attachment | Uploads and attaches a file to a jira issue. |
| `JIRA_ADD_COMMENT` | Add Comment | Adds a comment using atlassian document format (adf) for rich text to an existing jira issue. |
| `JIRA_ADD_WATCHER_TO_ISSUE` | Add Watcher to Issue | Adds a user to an issue's watcher list by account id. |
| `JIRA_ASSIGN_ISSUE` | Assign Issue | Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup. |
| `JIRA_BULK_CREATE_ISSUE` | Bulk Create Issues | Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling. |
| `JIRA_CREATE_ISSUE` | Create Issue | Creates a new jira issue (e.g., bug, task, story) in a specified project. |
| `JIRA_CREATE_ISSUE_LINK` | Link Issues | Links two jira issues using a specified link type with optional comment. |
| `JIRA_CREATE_PROJECT` | Create Project | Creates a new jira project with required lead, template, and type configuration. |
| `JIRA_CREATE_SPRINT` | Create Sprint | Creates a new sprint on a jira board with optional start/end dates and goal. |
| `JIRA_CREATE_VERSION` | Create Version | Creates a new version for releases or milestones in a jira project. |
| `JIRA_DELETE_COMMENT` | 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. |
| `JIRA_DELETE_ISSUE` | Delete Issue | Deletes a jira issue by its id or key. |
| `JIRA_DELETE_VERSION` | Delete Version | Deletes a jira version and optionally reassigns its issues. |
| `JIRA_DELETE_WORKLOG` | Delete Worklog | Deletes a worklog from a jira issue with estimate adjustment options. |
| `JIRA_EDIT_ISSUE` | Edit Issue | Updates an existing jira issue with field values and operations. supports direct field parameters (summary, description, assignee, priority, etc.) that are merged with the fields parameter. direct parameters take precedence. |
| `JIRA_FIND_USERS` | Find Users | Searches for jira users by email, display name, or username to find account ids; essential for assigning issues, adding watchers, and other user-related operations. |
| `JIRA_GET_ALL_ISSUE_TYPE_SCHEMES` | Get All Issue Type Schemes | Retrieves all jira issue type schemes with optional filtering and pagination. |
| `JIRA_GET_ALL_PROJECTS` | Get all projects | Retrieves all visible projects using the modern paginated jira api with server-side filtering and pagination support. |
| `JIRA_GET_ALL_STATUSES` | Get Issue Statuses | Retrieves all available issue statuses from jira with details. |
| `JIRA_GET_ALL_USERS` | Get All Users | Retrieves all users from the jira instance including active, inactive, and other user states with pagination support. |
| `JIRA_GET_COMMENT` | Get Comment | Retrieves a specific comment by id from a jira issue with optional expansions. |
| `JIRA_GET_CURRENT_USER` | Get Current User | Retrieves detailed information about the currently authenticated jira user. |
| `JIRA_GET_ISSUE` | Get Issue | Retrieves a jira issue by id or key with customizable fields and expansions. |
| `JIRA_GET_ISSUE_LINK_TYPES` | Get Issue Link Types | Retrieves all configured issue link types from jira. |
| `JIRA_GET_ISSUE_PROPERTY` | Get Issue Property | Retrieves a custom property from a jira issue by key. |
| `JIRA_GET_ISSUE_RESOLUTIONS` | Get Issue Resolutions | Retrieves all available issue resolution types from jira. |
| `JIRA_GET_ISSUE_TYPES` | 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. |
| `JIRA_GET_ISSUE_TYPE_SCHEME` | Get Issue Type Scheme | Gets a jira issue type scheme by id with all associated issue types. |
| `JIRA_GET_ISSUE_WATCHERS` | Get Issue Watchers | Retrieves users watching a jira issue for update notifications. |
| `JIRA_GET_ISSUE_WORKLOGS` | Get Issue Worklogs | Retrieves worklogs for a jira issue with user permission checks. |
| `JIRA_GET_PROJECT_VERSIONS` | Get Project Versions | Retrieves all versions for a jira project with optional expansion. |
| `JIRA_GET_REMOTE_ISSUE_LINKS` | Get Issue Remote Links | Retrieves links from a jira issue to external resources. |
| `JIRA_GET_TRANSITIONS` | Get Transitions | Retrieves available workflow transitions for a jira issue. |
| `JIRA_GET_VOTES` | Get Issue Votes | Fetches voting details for a jira issue; requires voting to be enabled in jira's general settings. |
| `JIRA_GET_WORKLOG` | Get Worklogs | Retrieves worklogs for a specified jira issue. |
| `JIRA_LIST_BOARDS` | List Boards | Retrieves paginated jira boards with filtering and sorting options. |
| `JIRA_LIST_ISSUE_COMMENTS` | List Issue Comments | Retrieves paginated comments from a jira issue with optional ordering. |
| `JIRA_LIST_SPRINTS` | List Sprints | Retrieves paginated sprints from a jira board with optional state filtering. |
| `JIRA_MOVE_ISSUE_TO_SPRINT` | Move Issues to Sprint | Moves one or more jira issues to a specified active sprint. |
| `JIRA_REMOVE_WATCHER_FROM_ISSUE` | Remove Watcher from Issue | Removes a user from an issue's watcher list by account id. |
| `JIRA_SEARCH_FOR_ISSUES_USING_JQL_GET` | Search Issues Using JQL (GET) | Searches for jira issues using jql with pagination and field selection. |
| `JIRA_SEARCH_FOR_ISSUES_USING_JQL_POST` | Search Issues Using JQL (POST) | Searches for jira issues using jql via post request for complex queries; ideal for lengthy jql queries that might exceed url character limits |
| `JIRA_SEARCH_ISSUES` | Search issues | Advanced jira issue search supporting structured filters and raw jql. |
| `JIRA_SEND_NOTIFICATION_FOR_ISSUE` | Send Notification for Issue | Sends a customized email notification for a jira issue. |
| `JIRA_TRANSITION_ISSUE` | Transition Issue | Transitions a jira issue to a different workflow state, with support for transition name lookup and user assignment by email. |
| `JIRA_UPDATE_COMMENT` | Update Comment | Updates text content or visibility of an existing jira comment. |

## Supported Triggers

| Trigger slug | Name | Description |
|---|---|---|
| `JIRA_NEW_ISSUE_TRIGGER` | New Issue | Triggered when a new issue is created in Jira |
| `JIRA_NEW_PROJECT_TRIGGER` | New Project | Triggered when a new project is added in Jira |
| `JIRA_UPDATED_ISSUE_TRIGGER` | Updated Issue | Triggered when an issue is updated in Jira |

## Creating MCP Server - Stand-alone vs Composio SDK

The Jira MCP server is an implementation of the Model Context Protocol that connects your AI agents and assistants directly to Jira. Instead of manually wiring Jira APIs, OAuth, and scopes yourself, you get a structured, tool-based interface that an LLM can call safely.
With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster.

## Step-by-step Guide

### 1. Prerequisites

You will need:
- A Composio API key
- An OpenAI API key (used by Autogen's OpenAIChatCompletionClient)
- A Jira account you can connect to Composio
- Some basic familiarity with Autogen and Python async

### 1. Getting API Keys for OpenAI and Composio

OpenAI API Key
- Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) 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](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs).
- Navigate to your API settings and generate a new API key.
- Store this key securely as you'll need it for authentication.

### 2. Install dependencies

Install Composio, Autogen extensions, and dotenv.
What's happening:
- composio connects your agent to Jira via MCP
- autogen-agentchat provides the AssistantAgent class
- autogen-ext-openai provides the OpenAI model client
- autogen-ext-tools provides MCP workbench support
```bash
pip install composio python-dotenv
pip install autogen-agentchat autogen-ext-openai autogen-ext-tools
```

### 3. Set up environment variables

Create a .env file in your project folder.
What's happening:
- COMPOSIO_API_KEY is required to talk to Composio
- OPENAI_API_KEY is used by Autogen's OpenAI client
- USER_ID is how Composio identifies which user's Jira connections to use
```bash
COMPOSIO_API_KEY=your-composio-api-key
OPENAI_API_KEY=your-openai-api-key
USER_ID=your-user-identifier@example.com
```

### 4. Import dependencies and create Tool Router session

What's happening:
- load_dotenv() reads your .env file
- Composio(api_key=...) initializes the SDK
- create(...) creates a Tool Router session that exposes Jira tools
- session.mcp.url is the MCP endpoint that Autogen will connect to
```python
import asyncio
import os
from dotenv import load_dotenv
from composio import Composio

from autogen_agentchat.agents import AssistantAgent
from autogen_ext.models.openai import OpenAIChatCompletionClient
from autogen_ext.tools.mcp import McpWorkbench, StreamableHttpServerParams

load_dotenv()

async def main():
    # Initialize Composio and create a Jira session
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    session = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["jira"]
    )
    url = session.mcp.url
```

### 5. Configure MCP parameters for Autogen

Autogen expects parameters describing how to talk to the MCP server. That is what StreamableHttpServerParams is for.
What's happening:
- url points to the Tool Router MCP endpoint from Composio
- timeout is the HTTP timeout for requests
- sse_read_timeout controls how long to wait when streaming responses
- terminate_on_close=True cleans up the MCP server process when the workbench is closed
```python
# Configure MCP server parameters for Streamable HTTP
server_params = StreamableHttpServerParams(
    url=url,
    timeout=30.0,
    sse_read_timeout=300.0,
    terminate_on_close=True,
    headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")}
)
```

### 6. Create the model client and agent

What's happening:
- OpenAIChatCompletionClient wraps the OpenAI model for Autogen
- McpWorkbench connects the agent to the MCP tools
- AssistantAgent is configured with the Jira tools from the workbench
```python
# Create model client
model_client = OpenAIChatCompletionClient(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY")
)

# Use McpWorkbench as context manager
async with McpWorkbench(server_params) as workbench:
    # Create Jira assistant agent with MCP tools
    agent = AssistantAgent(
        name="jira_assistant",
        description="An AI assistant that helps with Jira operations.",
        model_client=model_client,
        workbench=workbench,
        model_client_stream=True,
        max_tool_iterations=10
    )
```

### 7. Run the interactive chat loop

What's happening:
- The script prompts you in a loop with You:
- Autogen passes your input to the model, which decides which Jira tools to call via MCP
- agent.run_stream(...) yields streaming messages as the agent thinks and calls tools
- Typing exit, quit, or bye ends the loop
```python
print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
print("Ask any Jira related question or task to the agent.\n")

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

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

    if not user_input:
        continue

    print("\nAgent is thinking...\n")

    # Run the agent with streaming
    try:
        response_text = ""
        async for message in agent.run_stream(task=user_input):
            if hasattr(message, "content") and message.content:
                response_text = message.content

        # Print the final response
        if response_text:
            print(f"Agent: {response_text}\n")
        else:
            print("Agent: I encountered an issue processing your request.\n")

    except Exception as e:
        print(f"Agent: Sorry, I encountered an error: {str(e)}\n")
```

## Complete Code

```python
import asyncio
import os
from dotenv import load_dotenv
from composio import Composio

from autogen_agentchat.agents import AssistantAgent
from autogen_ext.models.openai import OpenAIChatCompletionClient
from autogen_ext.tools.mcp import McpWorkbench, StreamableHttpServerParams

load_dotenv()

async def main():
    # Initialize Composio and create a Jira session
    composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY"))
    session = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["jira"]
    )
    url = session.mcp.url

    # Configure MCP server parameters for Streamable HTTP
    server_params = StreamableHttpServerParams(
        url=url,
        timeout=30.0,
        sse_read_timeout=300.0,
        terminate_on_close=True,
        headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")}
    )

    # Create model client
    model_client = OpenAIChatCompletionClient(
        model="gpt-5",
        api_key=os.getenv("OPENAI_API_KEY")
    )

    # Use McpWorkbench as context manager
    async with McpWorkbench(server_params) as workbench:
        # Create Jira assistant agent with MCP tools
        agent = AssistantAgent(
            name="jira_assistant",
            description="An AI assistant that helps with Jira operations.",
            model_client=model_client,
            workbench=workbench,
            model_client_stream=True,
            max_tool_iterations=10
        )

        print("Chat started! Type 'exit' or 'quit' to end the conversation.\n")
        print("Ask any Jira related question or task to the agent.\n")

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

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

            if not user_input:
                continue

            print("\nAgent is thinking...\n")

            # Run the agent with streaming
            try:
                response_text = ""
                async for message in agent.run_stream(task=user_input):
                    if hasattr(message, 'content') and message.content:
                        response_text = message.content

                # Print the final response
                if response_text:
                    print(f"Agent: {response_text}\n")
                else:
                    print("Agent: I encountered an issue processing your request.\n")

            except Exception as e:
                print(f"Agent: Sorry, I encountered an error: {str(e)}\n")

if __name__ == "__main__":
    asyncio.run(main())
```

## Conclusion

You now have an Autogen assistant wired into Jira through Composio's Tool Router and MCP. From here you can:
- Add more toolkits to the toolkits list, for example notion or hubspot
- Refine the agent description to point it at specific workflows
- Wrap this script behind a UI, Slack bot, or internal tool
Once the pattern is clear for Jira, you can reuse the same structure for other MCP-enabled apps with minimal code changes.

## How to build Jira MCP Agent with another framework

- [ChatGPT](https://composio.dev/toolkits/jira/framework/chatgpt)
- [OpenAI Agents SDK](https://composio.dev/toolkits/jira/framework/open-ai-agents-sdk)
- [Claude Agent SDK](https://composio.dev/toolkits/jira/framework/claude-agents-sdk)
- [Claude Code](https://composio.dev/toolkits/jira/framework/claude-code)
- [Claude Cowork](https://composio.dev/toolkits/jira/framework/claude-cowork)
- [Codex](https://composio.dev/toolkits/jira/framework/codex)
- [Cursor](https://composio.dev/toolkits/jira/framework/cursor)
- [VS Code](https://composio.dev/toolkits/jira/framework/vscode)
- [OpenCode](https://composio.dev/toolkits/jira/framework/opencode)
- [OpenClaw](https://composio.dev/toolkits/jira/framework/openclaw)
- [Hermes](https://composio.dev/toolkits/jira/framework/hermes-agent)
- [CLI](https://composio.dev/toolkits/jira/framework/cli)
- [Google ADK](https://composio.dev/toolkits/jira/framework/google-adk)
- [LangChain](https://composio.dev/toolkits/jira/framework/langchain)
- [Vercel AI SDK](https://composio.dev/toolkits/jira/framework/ai-sdk)
- [Mastra AI](https://composio.dev/toolkits/jira/framework/mastra-ai)
- [LlamaIndex](https://composio.dev/toolkits/jira/framework/llama-index)
- [CrewAI](https://composio.dev/toolkits/jira/framework/crew-ai)

## Related Toolkits

- [Google Sheets](https://composio.dev/toolkits/googlesheets) - Google Sheets is a cloud-based spreadsheet tool for real-time collaboration and data analysis. It lets teams work together from anywhere, updating information instantly.
- [Notion](https://composio.dev/toolkits/notion) - Notion is a collaborative workspace for notes, docs, wikis, and tasks. It streamlines team knowledge, project tracking, and workflow customization in one place.
- [Airtable](https://composio.dev/toolkits/airtable) - Airtable combines the flexibility of spreadsheets with the power of a database for easy project and data management. Teams use Airtable to organize, track, and collaborate with custom views and automations.
- [Asana](https://composio.dev/toolkits/asana) - Asana is a collaborative work management platform for teams to organize and track projects. It streamlines teamwork, boosts productivity, and keeps everyone aligned on goals.
- [Google Tasks](https://composio.dev/toolkits/googletasks) - Google Tasks is a to-do list and task management tool integrated into Gmail and Google Calendar. It helps you organize, track, and complete tasks across your Google ecosystem.
- [Linear](https://composio.dev/toolkits/linear) - Linear is a modern issue tracking and project planning tool for fast-moving teams. It helps streamline workflows, organize projects, and boost productivity.
- [Clickup](https://composio.dev/toolkits/clickup) - ClickUp is an all-in-one productivity platform for managing tasks, docs, goals, and team collaboration. It streamlines project workflows so teams can work smarter and stay organized in one place.
- [Monday](https://composio.dev/toolkits/monday) - Monday.com is a customizable work management platform for project planning and collaboration. It helps teams organize tasks, automate workflows, and track progress in real time.
- [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time.
- [Agiled](https://composio.dev/toolkits/agiled) - Agiled is an all-in-one business management platform for CRM, projects, and finance. It helps you streamline workflows, consolidate client data, and manage business processes in one place.
- [Ascora](https://composio.dev/toolkits/ascora) - Ascora is a cloud-based field service management platform for service businesses. It streamlines scheduling, invoicing, and customer operations in one place.
- [Basecamp](https://composio.dev/toolkits/basecamp) - Basecamp is a project management and team collaboration tool by 37signals. It helps teams organize tasks, share files, and communicate efficiently in one place.
- [Beeminder](https://composio.dev/toolkits/beeminder) - Beeminder is an online goal-tracking platform that uses monetary pledges to keep you motivated. Stay accountable and hit your targets with real financial incentives.
- [Boxhero](https://composio.dev/toolkits/boxhero) - Boxhero is a cloud-based inventory management platform for SMBs, offering real-time updates, barcode scanning, and team collaboration. It helps businesses streamline stock tracking and analytics for smarter inventory decisions.
- [Breathe HR](https://composio.dev/toolkits/breathehr) - Breathe HR is cloud-based HR software for SMEs to manage employee data, absences, and performance. It simplifies HR admin, making it easy to keep employee records accurate and up to date.
- [Breeze](https://composio.dev/toolkits/breeze) - Breeze is a project management platform designed to help teams plan, track, and collaborate on projects. It streamlines workflows and keeps everyone on the same page.
- [Bugherd](https://composio.dev/toolkits/bugherd) - Bugherd is a visual feedback and bug tracking tool for websites. It helps teams and clients report website issues directly on live sites for faster fixes.
- [Canny](https://composio.dev/toolkits/canny) - Canny is a platform for managing customer feedback and feature requests. It helps teams prioritize product decisions based on real user insights.
- [Chmeetings](https://composio.dev/toolkits/chmeetings) - Chmeetings is a church management platform for events, members, donations, and volunteers. It streamlines church operations and improves community engagement.
- [ClickSend](https://composio.dev/toolkits/clicksend) - ClickSend is a cloud-based SMS and email marketing platform for businesses. It streamlines communication by enabling quick message delivery and contact management.

## Frequently Asked Questions

### What are the differences in Tool Router MCP and Jira MCP?

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.

### Can I use Tool Router MCP with Autogen?

Yes, you can. Autogen 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.

### Can I manage the permissions and scopes for Jira while using Tool Router?

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.

### How safe is my data with Composio Tool Router?

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.

---
[See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)