How to integrate Jira MCP with Codex

GET STARTED FOR FREE
Jira logo
Codex logo
divider

Introduction

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With Jira MCP integration, you can draft, triage, summarise emails, and much more, all without leaving the terminal or the app, whichever you prefer.

Also integrate Jira with

Why use Composio?

Apart from a managed and hosted MCP server, you will get:

  • CodeAct: A dedicated workbench that allows GPT to write its code to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Large tool responses: Handle them to minimise context rot.
  • Dynamic just-in-time access to 20,000 tools across 870+ other Apps for cross-app workflows. It loads the tools you need, so GPTs aren't overwhelmed by tools you don't need.

How to install Jira MCP in Codex

Run the setup command

Run this command in your terminal to add the Composio MCP server to Codex.

Terminal

It will initiate the authentication in a browser window, authorize Codex to access your Composio account.

Composio authentication page

(Optional) Authenticate with OAuth

To authenticate manually, run the login command to open a browser window and authorize Codex to access your Composio account.

bash
codex mcp login composio

Verify the connection

Run codex mcp list to confirm Composio appears as a registered MCP server.

bash
codex mcp list

Codex App

Codex App follows the same approach as VS Code.

  1. Click ⚙️ on the bottom left → MCP Servers → + Add servers → Streamable HTTP:
  2. Fill the header and Key fields with { "x-consumer-api-key" = "ck_*******" }.
  3. The Key is the Composio API key, that you can find on dashboard.composio.dev
  4. Click on Authenticate and authorize Codex to your Composio account and you're all set.
Codex App MCP setup
  1. Restart and verify if it's there in .codex/config.toml
bash
[mcp_servers.composio]
url = "https://connect.composio.dev/mcp"
http_headers = { "x-consumer-api-key" = "ck_*******" }

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.

Conclusion

You've successfully integrated Jira with Codex using Composio's MCP server. Now you can interact with Jira directly from your terminal, VS Code, or the Codex App using natural language commands.

Key benefits of this setup:

  • Seamless integration across CLI, VS Code, and standalone app
  • Natural language commands for Jira operations
  • Managed authentication through Composio
  • Access to 20,000+ tools across 870+ apps for cross-app workflows
  • CodeAct workbench for complex tool chaining

Next steps:

  • Try asking Codex to perform various Jira operations
  • Explore cross-app workflows by connecting more toolkits
  • Build automation scripts that leverage Codex's AI capabilities

How to build Jira MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Jira MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Jira MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Jira MCP with Claude Code

OpenClaw logo

OpenClaw

Use Jira MCP with OpenClaw

Hermes logo

Hermes

Use Jira MCP with Hermes

CLI logo

CLI

Use Jira MCP with CLI

Google ADK logo

Google ADK

Use Jira MCP with Google ADK

LangChain logo

LangChain

Use Jira MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Jira MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Jira MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Jira MCP with LlamaIndex

CrewAI logo

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 Codex?

Yes, you can. Codex 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
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
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