Skip to content

Ticketing

Jira MCP connector

The Jira connector brings your projects, issues, comments, and attachments into Claude, ChatGPT, Cursor, Microsoft Copilot, and any MCP client, so anyone on your team can search, create, and update Jira issues while signed in as themselves.

Connect on Elaichi How to connect
  • OAuth or API key
  • Free 14-day trial
  • No credit card
ChatGPT Elaichi connected

Summarize the issues created in Jira this week.

Working in Jira with Elaichi

  • List all Jira accessible resources
  • Get single Jira issue attachment by ID
  • List all Jira issue attachments
Ask anything…
Governance / Audit log Last 24 hours
Jira List all Jira issue attachments Emily Carter · ChatGPT · 9:41 AM Done
Jira Get single Jira issue attachment by ID Emily Carter · ChatGPT · 9:41 AM Done
Jira List all Jira accessible resources Emily Carter · ChatGPT · 9:41 AM Done
Jira Create a Jira issue attachment Megan Brooks · Claude · 9:38 AM Done
Jira Jira issue attachments download by ID Ryan Hayes · Cursor · 9:35 AM Done

How to connect Jira to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Jira MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Jira MCP connector for Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

    https://api.elaichi.ai/mcp
  2. 2

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

Jira MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

Jira MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Jira MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

    https://api.elaichi.ai/mcp
  3. 3

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

Connect Jira to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Connect Jira on Elaichi See pricing

What teams do with Jira through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Jira is logged.

  • Engineering

    Turn a bug report into a Jira issue

    Describe the problem in plain language and have the issue created in the right Jira project, with the right labels and the screenshot attached, without opening a form.

  • Support

    Check where a customer's ticket stands

    Ask what happened on the Jira issue linked to a customer complaint and get the latest comments and status back, then post an update for the engineer while the customer is still on the line.

  • Product

    Summarize what shipped this sprint

    Search a Jira project for everything closed in the last two weeks and get a readable summary by label, ready to paste into release notes or a stakeholder update.

  • IT

    Clean up stale issues in a project

    Find Jira issues nobody has touched in ninety days, add a comment asking the owner to confirm, and update the ones that should be closed.

  • Program management

    See who owns what across projects

    List the Jira projects a group is working in, look up who holds which role, and spot issues with no assignee before the weekly review.

  • Compliance

    Review Jira access and license use

    Pull the Jira audit log for a date range, check which users and groups exist, and see how many licenses are in use before a renewal or an access review.

Try asking

  • “Summarize the issues created in Jira this week.”
  • “Which Jira issues are unassigned and still open?”
  • “Add a comment to the top three blocked issues.”

See all 41 Jira tools →

What connecting Jira gets you

6 screens from Elaichi, each doing one job for your Jira account.

Elaichi Agent

Ask Elaichi to work across your apps.

Summarize the issues created in Jira this week.

Which Jira issues are unassigned and still open?

Add a comment to the top three blocked issues.

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask about Jira issues, get real answers.

Type a question in plain language and read it back from live Jira issues.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

 • Connected 4 minutes ago
Cursor
M

Megan Brooks

 • Connected 2 hours ago
ChatGPT
R

Ryan Hayes

 • Connected Yesterday

AI apps

Claude, ChatGPT, Cursor and Microsoft Copilot reach Jira here.

One governed MCP endpoint over OAuth, no SDK and no shared API key.

ElaichiTools
Tool Action Description
List all Jira accessible resources List Get list of accessible resources in Jira. Returns id, name, url, scopes, and avatarUrl for each resource.
Create a Jira issue attachment Create Add one or more attachments to an issue in Jira using issueIdOrKey. Returns attachment details including id, filename, mimeType, size, content URL, author info, and creation timestamp.
Get single Jira issue attachment by ID Get Get metadata for an attachment by id in Jira. Returns author details, content URL, creation date, filename, mimeType, size, thumbnail URL, and self link.
List all Jira issue attachments List Get details about a specific issue in Jira by id. Returns key fields including attachments with author info, filename, size, and content URL.
Jira issue attachments download by ID Download Download the file of a Jira issue attachment by its attachment id. Get the id from the issue-attachments list or get tool. Returns the raw file (stored by Elaichi as a downloadable file). Required: id.

Tool catalog

41 Jira tools ready without custom code.

Issues, comments, attachments and search, with every method listed in the catalog.

ElaichiToolboxes
Name Source template Tools Created

Engineering toolbox

Jira · issues and comments

 Jira starter 18 Mar 4, 2026

QA toolbox

Jira · bug issues and attachments

 — 9 Mar 2, 2026

Support toolbox

Jira · escalated issues and comments

 — 24 Feb 27, 2026

Product toolbox

Jira · issue search and roadmap epics

 Jira starter 6 Feb 19, 2026

Design toolbox

Jira · issue attachments and reviews

 — 31 Jan 30, 2026

Release management toolbox

Jira · issue status and fix versions

 — 12 Jan 22, 2026

Toolboxes

Every team gets its own Jira toolbox.

Curate one toolbox per team and scope it to the Jira work they own.

ElaichiConnections
Connection Scope Status Access
JI

Jira (Core platform)

Connected by Emily Carter

 Personal • Active 1 team · 6 members
JI

Jira (Mobile apps)

Connected by Jake Morgan

 Organization • Active 3 teams · 24 members
JI

Jira (Support escalations)

Connected by Megan Brooks

 Organization • Active 2 teams · 11 members
JI

Jira (Infrastructure)

Connected by Tyler Reed

 Personal • Needs re-auth 1 team · 3 members
JI

Jira (QA automation)

Connected by Ryan Hayes

 Personal • Active Not shared
JI

Jira (Product roadmap)

Connected by Ashley Parker

 Personal • Active 2 teams · 9 members

Shared connections

Teammates work in Jira without a credential.

See who connected each Jira account and which teams and members share it.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM
E

Emily Carter

[email protected]

 Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM
J

Jake Morgan

[email protected]

 Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM
M

Megan Brooks

[email protected]

 Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM
T

Tyler Reed

[email protected]

 Jira Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM
R

Ryan Hayes

[email protected]

 Jira Issues Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM
A

Ashley Parker

[email protected]

 Jira Issues List Toolbox

Audit log

Every Jira call is written down.

When, who, what happened, type and resource, in an append only log.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.

Jira digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch issues

    Jira

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s

  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve

  6. Post the digest

    Jira

    Queued

Automations

A schedule fires and Jira issues move.

Six steps fetch issues, group them, draft a digest, await approval, comment back.

Jira health

Refreshed 4 minutes ago · every 15 minutes · from the issues collection

Live

Issues

1,284 ↓ 12%

Comments

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Issues created

Last 14 days

By team

Share of activity

Core platform 34%

Mobile apps 27%

Support escalations 21%

Infrastructure 18%

Collections and dashboards

Jira issue health, counted not guessed.

Four metrics, 14 days of issues created and a team breakdown, refreshed on schedule.

For IT and engineering

Elaichi vs Zapier MCP vs Composio for Jira

All three can connect Jira to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Jira, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Jira tools Allow or restrict single Jira tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Jira call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price Free for one person; $15 per user per month on Gold. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

Jira tools for your AI agents

41 tools are ready to call through Elaichi's MCP endpoint the moment you connect Jira, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

More from the catalog

Browse all 650+ connectors →

Questions, answered

How do I connect Jira to Claude?

Connect Jira in Elaichi first: pick Jira from the catalog and either sign in with your Atlassian account or paste a Jira API key, whichever your organization prefers. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude will ask you to sign in to Elaichi, and from then on Jira is available in your conversations.

Does Jira work with ChatGPT and Cursor as well as Claude?

Yes. Once Jira is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client, and the Elaichi Agent. You connect Jira once and every client you use picks it up.

What can an AI agent actually do with my Jira data?

With Jira connected, an agent can search issues, read and write comments, create and update issues, attach files, and look up projects, users, groups, labels, roles, audit logs, and license counts. In practice that means asking what is blocking a release, having a bug written up from a chat message, or getting a summary of everything closed last week. Because Jira offers a lot of actions, short concrete asks such as "create an issue in the Billing project for the failed invoice export" work better than long instructions.

Does connecting Jira give the AI access to every project?

No. Every call to Jira runs as the person who signed in, so an agent only sees the projects and issues that person can already see in Jira and cannot do anything their Jira permissions forbid. Elaichi can narrow that further, for example limiting a team to reading issues without editing them, but it can never grant more than the person already has in Jira.

Can my team share one Jira connection?

Yes. One person connects Jira in Elaichi and shares the connection with a team, and nobody else ever handles the API key or signs in to Jira separately. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every issue created or comment posted in Jira.

Can I stop an agent from deleting or changing things in Jira?

Yes. Restrictions in Elaichi work per action, so you can allow searching and reading Jira issues while restricting deleting issues, deleting comments, or editing anything at all. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, or any other client cannot run it, whatever the prompt says.

What happens to a Jira connection when someone leaves?

Offboarding a person in Elaichi ends their access to Jira through every client at once, with no need to hunt through Claude, ChatGPT, Cursor, Microsoft Copilot, or Microsoft Copilot settings. If they connected a shared Jira account, that connection keeps working for everyone else on the team. Disconnecting Jira once in Elaichi removes it from every client for everyone.

Does the Jira MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Jira is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Jira?

Yes. Both let Claude, ChatGPT or Cursor use Jira. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Jira call.

How is Elaichi different from Composio for Jira?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Jira: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Jira in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

Connect Jira Talk to us

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot