How to integrate Jira MCP with Google ADK

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Jira Logo
Google ADK Logo
divider

Introduction

This guide walks you through connecting Jira to Google ADK 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, start a new sprint for the dev board through natural language commands.

This guide will help you understand how to give your Google ADK 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.

TL;DR

Here's what you'll learn:
  • Get a Jira account set up and connected to Composio
  • Install the Google ADK and Composio packages
  • Create a Composio Tool Router session for Jira
  • Build an agent that connects to Jira through MCP
  • Interact with Jira using natural language

What is Google ADK?

Google ADK (Agents Development Kit) is Google's framework for building AI agents powered by Gemini models. It provides tools for creating agents that can use external services through the Model Context Protocol.

Key features include:

  • Gemini Integration: Native support for Google's Gemini models
  • MCP Toolset: Built-in support for Model Context Protocol tools
  • Streamable HTTP: Connect to external services through streamable HTTP
  • CLI and Web UI: Run agents via command line or web interface

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 & Triggers

Tools
Triggers
Add AttachmentUploads and attaches a file to a jira issue.
Add CommentAdds a comment using atlassian document format (adf) for rich text to an existing jira issue.
Add Watcher to IssueAdds a user to an issue's watcher list by account id.
Assign IssueAssigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.
Bulk Create IssuesCreates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.
Create IssueCreates a new jira issue (e.
Link IssuesLinks two jira issues using a specified link type with optional comment.
Create ProjectCreates a new jira project with required lead, template, and type configuration.
Create SprintCreates a new sprint on a jira board with optional start/end dates and goal.
Create VersionCreates a new version for releases or milestones in a jira project.
Delete CommentDeletes 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 IssueDeletes a jira issue by its id or key.
Delete VersionDeletes a jira version and optionally reassigns its issues.
Delete WorklogDeletes a worklog from a jira issue with estimate adjustment options.
Edit IssueUpdates an existing jira issue with field values and operations.
Find UsersSearches for jira users by email, display name, or username to find account ids; essential for assigning issues, adding watchers, and other user-related operations.
Get All Issue Type SchemesRetrieves all jira issue type schemes with optional filtering and pagination.
Get all projectsRetrieves all visible projects using the modern paginated jira api with server-side filtering and pagination support.
Get Issue StatusesRetrieves all available issue statuses from jira with details.
Get All UsersRetrieves all users from the jira instance including active, inactive, and other user states with pagination support.
Get CommentRetrieves a specific comment by id from a jira issue with optional expansions.
Get Current UserRetrieves detailed information about the currently authenticated jira user.
Get IssueRetrieves a jira issue by id or key with customizable fields and expansions.
Get Issue Link TypesRetrieves all configured issue link types from jira.
Get Issue PropertyRetrieves a custom property from a jira issue by key.
Get Issue ResolutionsRetrieves all available issue resolution types from jira.
Get issue typesRetrieves 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 Type SchemeGets a jira issue type scheme by id with all associated issue types.
Get Issue WatchersRetrieves users watching a jira issue for update notifications.
Get Issue WorklogsRetrieves worklogs for a jira issue with user permission checks.
Get Project VersionsRetrieves all versions for a jira project with optional expansion.
Get Issue Remote LinksRetrieves links from a jira issue to external resources.
Get TransitionsRetrieves available workflow transitions for a jira issue.
Get Issue VotesFetches voting details for a jira issue; requires voting to be enabled in jira's general settings.
Get WorklogsRetrieves worklogs for a specified jira issue.
List BoardsRetrieves paginated jira boards with filtering and sorting options.
List Issue CommentsRetrieves paginated comments from a jira issue with optional ordering.
List SprintsRetrieves paginated sprints from a jira board with optional state filtering.
Move Issues to SprintMoves one or more jira issues to a specified active sprint.
Remove Watcher from IssueRemoves a user from an issue's watcher list by account id.
Search Issues Using JQL (GET)Searches for jira issues using jql with pagination and field selection.
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
Search issuesAdvanced jira issue search supporting structured filters and raw jql.
Send Notification for IssueSends a customized email notification for a jira issue.
Transition IssueTransitions a jira issue to a different workflow state, with support for transition name lookup and user assignment by email.
Update CommentUpdates text content or visibility of an existing jira comment.

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

What is Tool Router?

Composio's Tool Router 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 Tool Router

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

How the Tool Router works

The Tool Router 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

Prerequisites

Before starting, make sure you have:
  • A Google API key for Gemini models
  • A Composio account and API key
  • Python 3.9 or later installed
  • Basic familiarity with Python

Getting API Keys for Google and Composio

Google API Key
  • Go to Google AI Studio and create an API key.
  • Copy the key and keep it safe. You will put this in GOOGLE_API_KEY.
Composio API Key and User ID
  • Log in to the Composio dashboard.
  • Go to Settings → API Keys and copy your Composio API key. Use this for COMPOSIO_API_KEY.
  • Decide on a stable user identifier to scope sessions, often your email or a user ID. Use this for COMPOSIO_USER_ID.

Install dependencies

bash
pip install google-adk composio-google python-dotenv

Inside your virtual environment, install the required packages.

What's happening:

  • google-adk is Google's Agents Development Kit
  • composio connects your agent to Jira via MCP
  • composio-google provides the Google ADK provider
  • python-dotenv loads environment variables

Set up ADK project

bash
adk create my_agent

Set up a new Google ADK project.

What's happening:

  • This creates an agent folder with a root agent file and .env file

Set environment variables

bash
GOOGLE_API_KEY=your-google-api-key
COMPOSIO_API_KEY=your-composio-api-key
COMPOSIO_USER_ID=your-user-id-or-email

Save all your credentials in the .env file.

What's happening:

  • GOOGLE_API_KEY authenticates with Google's Gemini models
  • COMPOSIO_API_KEY authenticates with Composio
  • COMPOSIO_USER_ID identifies the user for session management

Import modules and validate environment

python
import os
import warnings

from composio import Composio
from composio_google import GoogleProvider
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

load_dotenv()

warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

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.")
What's happening:
  • os reads environment variables
  • Composio is the main Composio SDK client
  • GoogleProvider declares that you are using Google ADK as the agent runtime
  • Agent is the Google ADK LLM agent class
  • McpToolset lets the ADK agent call MCP tools over HTTP

Create Composio client and Tool Router session

python
print("Initializing Composio client...")
composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider())

print("Creating Composio session...")
composio_session = composio_client.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["jira"],
)

COMPOSIO_MCP_URL = composio_session.mcp.url
print(f"Composio MCP HTTP URL: {COMPOSIO_MCP_URL}")
What's happening:
  • Authenticates to Composio with your API key
  • Declares Google ADK as the provider
  • Spins up a short-lived MCP endpoint for your user and selected toolkit
  • Stores the MCP HTTP URL for the ADK MCP integration

Set up the McpToolset and create the Agent

python
print("Creating Composio toolset for the agent...")
composio_toolset = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url=COMPOSIO_MCP_URL,
        headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")}
    )
)

root_agent = Agent(
    model="gemini-2.5-pro",
    name="composio_agent",
    description="An agent that uses Jira tools to perform actions.",
    instruction=(
        "You are a helpful assistant connected to Composio. "
        "You have the following tools available: "
        "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
        "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
        "Use these tools to help users with Jira operations."
    ),
    tools=[composio_toolset],
)

print("\nAgent setup complete. You can now run this agent directly ;)")
What's happening:
  • Connects the ADK agent to the Composio MCP endpoint through McpToolset
  • Uses Gemini as the model powering the agent
  • Lists exact tool names in instruction to reduce misnamed tool calls

Run the agent

bash
# Run in CLI mode
adk run my_agent

# Or run in web UI mode
adk web
Execute the agent from the project root. The web command opens a web portal where you can chat with the agent. What's happening:
  • adk run runs the agent in CLI mode
  • adk web opens a web UI for interactive testing

Complete Code

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

python
import os
import warnings

from composio import Composio
from composio_google import GoogleProvider
from dotenv import load_dotenv
from google.adk.agents.llm_agent import Agent
from google.adk.tools.mcp_tool.mcp_session_manager import StreamableHTTPConnectionParams
from google.adk.tools.mcp_tool.mcp_toolset import McpToolset

def main():
    try:
        load_dotenv()

        warnings.filterwarnings("ignore", message=".*BaseAuthenticatedTool.*")

        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.")

        print("Initializing Composio client...")
        composio_client = Composio(api_key=COMPOSIO_API_KEY, provider=GoogleProvider())

        print("Creating Composio session...")
        composio_session = composio_client.create(
            user_id=COMPOSIO_USER_ID,
            toolkits=["jira"],
        )

        COMPOSIO_MCP_URL = composio_session.mcp.url
        print(f"Composio MCP HTTP URL: {COMPOSIO_MCP_URL}")

        print("Creating Composio toolset for the agent...")
        composio_toolset = McpToolset(
            connection_params=StreamableHTTPConnectionParams(
                url=COMPOSIO_MCP_URL,
                headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")}
            )
        )

        root_agent = Agent(
            model="gemini-2.5-pro",
            name="composio_agent",
            description="An agent that uses Jira tools to perform actions.",
            instruction=(
                "You are a helpful assistant connected to Composio. "
                "You have the following tools available: "
                "COMPOSIO_SEARCH_TOOLS, COMPOSIO_MULTI_EXECUTE_TOOL, "
                "COMPOSIO_MANAGE_CONNECTIONS, COMPOSIO_REMOTE_BASH_TOOL, COMPOSIO_REMOTE_WORKBENCH. "
                "Use these tools to help users with Jira operations."
            ),
            tools=[composio_toolset],
        )

        print("\nAgent setup complete. You can now run this agent directly ;)")

    except Exception as e:
        print(f"\nAn error occurred during agent setup: {e}")

if __name__ == "__main__":
    main()

Conclusion

You've successfully integrated Jira with the Google ADK through Composio's MCP Tool Router. Your agent can now interact with Jira using natural language commands.

Key takeaways:

  • The Tool Router approach dynamically routes requests to the appropriate Jira tools
  • Environment variables keep your credentials secure and separate from code
  • Clear agent instructions reduce tool calling errors
  • The ADK web UI provides an interactive interface for testing and development

You can extend this setup by adding more toolkits to the toolkits array in your session configuration.

How to build Jira MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Jira MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Jira MCP with Claude Agent SDK

LangChain

LangChain

Use Jira MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Jira MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Jira MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Jira MCP with LlamaIndex

CrewAI

CrewAI

Use Jira MCP with CrewAI

FAQ

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 Google ADK?

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

Used by agents from

Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
ASU
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Book a call↗Get started for free