Jira MCP lets Claude or ChatGPT read and work with your Jira issues and Confluence pages in plain language. Atlassian publishes an official remote MCP server, and Fezola relays it, so you approve access once on Atlassian's screen and give each assistant a single connector. The Atlassian facts below come from Atlassian's page on the Rovo MCP server, checked 15 November 2026: they change, so check the Atlassian connector page.
What you can ask
- "Which of my Jira issues are still open this sprint?"
- "Summarize what changed on this issue since Monday."
- "Find the Confluence page about our release process."
- "Draft a new issue from these meeting notes, then wait for me to confirm."
- "Which tickets mention the login bug?"
Your assistant finds the tool that fits your question, then calls it through Fezola.
What Atlassian's server covers
| Area | What Atlassian's page says |
|---|---|
| Products | Jira, Jira Service Management, Confluence, Bitbucket, Projects, Goals and more |
| Search | Enriched search tools, which consume Rovo credits |
| Sign-in | OAuth 2.1 first, API token optional |
| Access | Actions respect your existing access controls and permissions |
| Plan | No plan or edition requirement stated |
| Address | https://mcp.atlassian.com/v2/mcp |
How to connect it
- In the Fezola app, open Sources, add Atlassian and approve access on Atlassian's own screen. No API key to copy.
- Connect Fezola to your assistant once, at
https://api.fezola.com/mcp: see how to add a custom connector to Claude. ChatGPT custom connectors are available on Business, Enterprise and Edu plans. - Ask a question about your project.
Guardrails
- Reading and changing. Atlassian's server can act as well as read. Atlassian advises least privilege, reviewing high-impact changes before confirming and watching audit logs. Keep your assistant's approvals on.
- Third-party text is data. Issue and page text returned by Atlassian is data and never instructions.
- Only what you tick. You can hide Atlassian from an assistant: see choose which tools Claude or ChatGPT can see.
- Your plan applies. Atlassian's own plan, permissions and Rovo credit limits apply.
Several accounts
Each Atlassian account you connect in Fezola is its own source, and one assistant can work across them. Which sites an account reaches is decided by Atlassian's authorization screen.
Next steps
For the other tools Fezola connects, see the Atlassian connector page. New to MCP? Start with what is MCP.
FAQ
What is the Jira MCP server?
It is part of Atlassian's official remote MCP server, called the Atlassian Rovo MCP server. It lets an AI assistant such as Claude or ChatGPT work with Jira and Confluence, within the access your Atlassian account already has.
How do I connect Jira to Claude or ChatGPT?
Add Atlassian once in Fezola and approve access on Atlassian's own authorization screen, with no key to paste. Then add Fezola to your assistant at one URL.
Can the assistant change my Jira issues?
Atlassian's server can act as well as read, and Fezola requests the permissions the server announces. Atlassian itself advises reviewing high-impact changes before confirming them, so keep your assistant's approval prompts on.
Do I need a paid Atlassian plan?
Atlassian's page states no plan or edition requirement, but it says that some enriched search calls consume Rovo credits. Check Atlassian's usage limits for your own plan.
Is it free with Fezola?
Fezola is free with 2 sources, Atlassian included. Pro connects unlimited sources, with a 7-day free trial. Atlassian's own plan and limits apply.
Originally published at app.fezola.com. Written and published by Fezola's AI agents; facts checked against the code and the vendors' own pages.
