Starter
For one person starting with their main account.
$6$5/mo
billed monthly $60 billed annually, save 17%
Try free for 7 daysTry free for 7 days- 2 connectors at once
- 2 accounts across them
- 1 seat
- Unlimited conversations
Jira is where your team writes down the work, and where finding out what is actually in flight takes a filter nobody remembers. This connector lets you ask it from your own AI assistant: what is still open in this sprint, what is assigned to you, and which bugs came in this week.
Connect Jira to Claude, ChatGPT, Grok, Perplexity, Claude Code, Codex, Cursor or Antigravity, with one connection, on the subscription you already pay for.
Read-only: it cannot change anything in this account.
Who it’s for: Mobile apps · Agencies · Sales & support
Without HeyMetra
With HeyMetra
Without HeyMetra
With HeyMetra
Without HeyMetra
With HeyMetra
Without HeyMetra
With HeyMetra
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 is open, what is done and who has it, across the projects on the site you connected.
What is still unfinished in the current sprint, which is usually the first thing anyone wants to know before a standup.
What people said on an issue, so you can catch up on a thread without scrolling through it.
One Atlassian site is one connection on your plan, however many projects and issues it holds. Every plan can connect it.
For one person starting with their main account.
$6$5/mo
billed monthly $60 billed annually, save 17%
Try free for 7 daysTry free for 7 daysMost popular
For a small team running several accounts together.
$19$15.83/mo
billed monthly $190 billed annually, save 17%
Try free for 7 daysTry free for 7 daysFor teams and agencies with many accounts to connect.
$49$40.83/mo
billed monthly $490 billed annually, save 17%
Try free for 7 daysTry free for 7 daysFor organizations with custom scale and security needs.
Contact us
Contact salesNo. This connection asks Atlassian for read permission only, so nothing here can create, edit or move an issue. If you want that, tell us: it was a decision about personal data, and hearing that people want it is what would reopen it.
No. The grant covers the one site you pick when you connect. Connect the site your team works in first, and add the other as a second connection whenever you need it.
Naming a person is a separate permission from reading the work, and older connections were made before it was asked for. Reconnect and the names come back.
The list shows the sites the person signing in can open. Ask a Jira admin to add you to that site, then connect again so Atlassian reads the list afresh.
Jira holds the work that is planned. PostHog shows whether what shipped is being used, and Slack or email is where a sprint's summary goes without anyone copying it across.
Connectors
Add your own connectorAdd custom connector
Settings → Customize → Connectors
Security and login
Developer mode
Settings → Security and login → Developer mode → chatgpt.com/plugins
grok.com/connectors
Bring your own MCPNew Connector → Custom
grok.com/connectors → New Connector → Custom
Plugins
Connector → Add MCP connector → RemoteAdd custom
Plugins → Add custom → Connector → Add MCP connector → Remote
$ claude mcp add --transport http heymetra https://mcp.heymetra.com/mcp
Added HTTP MCP server heymetra
> /mcp
✓ heymetra · connected
1[mcp_servers.heymetra]
2url = "https://mcp.heymetra.com/mcp"
$ codex mcp login heymetra
1{
2 "mcpServers": {
3 "heymetra": { "url": "https://mcp.heymetra.com/mcp" }
4 }
5}
1{
2 "mcpServers": {
3 "heymetra": { "serverUrl": "https://mcp.heymetra.com/mcp" }
4 }
5}
Three steps, all on Atlassian's side. You type nothing into HeyMetra: you sign in, pick the site, and name the connection after it, since that name is what you use when 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, such as acme.atlassian.net and acme-dev.atlassian.net, Atlassian asks which. The one you pick is the one this connection covers, and the others stay out of reach until you connect them too.
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.
Then add HeyMetra where you ask
Three things come up with Jira. A site missing from Atlassian's list, an assignee shown as an id instead of a name, and a request for the assistant to create issues, which this connection does not ask permission for.
Add your site to HeyMetra once, then ask about open issues and new bugs from the assistant you already use.
Or read the same steps on GitHub: zeisoft/jira-mcp.