Jira MCP Server

Soon

Connect Jira to Claude, ChatGPT, Grok, Perplexity, Claude Code, Codex, Cursor or Antigravity — one connection, from the subscription you already pay for.

The Jira MCP server is a connector on HeyMetra. Authorise Jira once with OAuth and it becomes tools your assistant can call — read-only, so nothing here can change your account.

Example exchange

At a glance

Category: Work
How you connect: OAuth
Access: Read-only
Status: Soon

What Jira is

Jira is where the work is written down: issues and their status, projects, sprints, who a thing is assigned to, and what was said in the comments. It answers "what is actually in flight" without anybody building a report for it.

What it can do, and what you can switch off

Each of these is a switch on the connection itself. Turn one off and the assistant is told, and cannot use it — so a team can read order volume without ever reaching the payouts. Where Jira itself will not serve something, it says so here rather than answering as though there were nothing to find.

Direct API access

Reads

Let your assistant use this account's own API for anything HeyMetra's other operations do not cover. It reads directly, and what comes back is the provider's own answer rather than a figure HeyMetra has checked. It can also propose changes — those are never applied until you approve them, and HeyMetra cannot undo one afterwards.

Limit Read-only. This connection asks Atlassian for no permission to change anything, so no card can propose one.

Limit The grant covers the one site picked when it was made. Another site on the same account is another connection.

Setting it up

You sign in on Jira's own screen, so no password reaches us. Then add HeyMetra as a remote MCP server where you ask.

Press Connect and sign in to Atlassian

You are sent to Atlassian's own screen. Nothing is typed into HeyMetra: the grant is made there and Atlassian tells us what it covers.
Pick the site this connection is for

If your account has more than one — acme.atlassian.net and acme-dev.atlassian.net — Atlassian asks which. The one you pick is the one this grant covers, and the others stay out of reach until you connect them too.

Worth knowing Connect the site your team actually works in first. A second connection costs another minute and can be added whenever it is wanted.
Name the connection after the site

'Acme' rather than 'Jira'. That name is what you say when you ask a question about it, and it is what tells two connections apart.

When it does not work

These are the things that actually go wrong, written from what you see rather than from what caused it.

The site you wanted is not in the list Atlassian showed.

The grant is made by the person signing in, and it covers the sites that person can open. A site nobody added you to is not one of them.

Fix Ask a Jira admin to add you to that site, then connect again so the list is read afresh.

Issues answer, but the assignee comes back as an id.

Naming a person is a separate permission from reading the work itself, and this connection was made before it was asked for.

Fix Reconnect. The current grant asks for both, and a connection made before one of them was added keeps the narrower one until it is replaced.

You want the assistant to create or move issues.

This connector asks only to read. The write permission is not requested, so no card can propose a change here.

Fix Tell us — it is a decision about personal data rather than a technical limit, and knowing somebody wants it is what would reopen it.

Where you ask

Frequently asked

Is the Jira connector available yet?

Not yet — Jira is marked Soon. When it opens it is on every plan: plans differ in how many accounts you connect at once, never in which ones. The connectors page names everything that is ready today.

What can I ask about Jira once it is connected?

Whatever the tools can answer — you type the question into Claude or ChatGPT, not into anything of ours. For example: “Which issues are still open in this sprint?” or “What is assigned to me and not done?”

Can HeyMetra change my Jira account?

No. This connector is read-only: HeyMetra has no tool that writes to Jira.

How do I connect Jira to Claude or ChatGPT?

You connect Jira to HeyMetra once — by signing in on Jira, so no password reaches us — and then add HeyMetra as a remote MCP server in whichever of them you use. There is a setup page here for each one.

What does the Jira connector cost?

Nothing on its own. Plans are priced by how many connectors and seats you get, not per connector or per tool call, and every plan can reach every connector that is live. The pricing page carries the current figures.

Connectors next to this one

The other half of the question lives in a different category: Zoho Marketing Automation data sits behind the same connection, which is what lets one answer cover both.

Jira is not available yet

This page exists so it is ready when the connector is. Do not buy a plan for Jira — tell us you want it instead, and we will say when it lands rather than when we hope it will.

Tell us you want it See what works today