IntegrationsJira & Confluence integration
Your Jira and Confluence.One clear answer.
Connect Jira and Confluence to Claude Code, Codex, Cursor or any MCP agent through CoreSpeed. Your agent searches Jira issues with JQL, reads boards and sprints, and reads the Confluence pages behind the work, then drafts a sprint summary or a release note. It uses your own Atlassian account, and changing an issue or a page is a separate call.
From the sprint boardto the page that explains it.
Requests you can make once Jira & Confluence is connected. The data is fictional.
- Jira & ConfluencePAY · Sprint 14
- PAY-311Refund webhook retriesIn progress
- PAY-318Currency rounding fixBlocked
- PAY-302Payout report exportDone
Catch up on the sprint
From the projects you can access
- Jira & ConfluencePayments space
Release plan · 4.2
- Scope: refund retries and the rounding fix.
- Sign-off: not assigned yet.
- Rollout: staged, one region first.
Read the page behind the work
Read, not edited
Approval requestWaiting
Claude Code for Drew
atlassian__jira_transition_issue
“Move PAY-311 to Done.”
Policy: Ask before closing a Jira issue.
ApproveDeny
Hold a transition for review
Approval required
See the sprint.Read the plan behind it.
Ask your agent to compare the open sprint in Jira with the release plan in Confluence, and to name what is blocked or missing.
Reads fromJira & Confluence
All connectors →Search the current PAY sprint in Jira and read the 4.2 release plan in Confluence. Draft a sprint summary with blockers and open decisions. Do not change any issue or page.
atlassian__jira_searchok
PAY · 11 issues, 1 blocked
Keep your agent.Bring your work.
One CoreSpeed account, across compatible agents.
- 1
Set up CoreSpeed
Give your agent the setup line. It adds CoreSpeed and signs you in.
- 2
Connect Jira & Confluence
Authorize the account and the content you need.
- 3
Start with one task
Ask for a summary, a brief, or a draft. Review the answer.
Setup guidesClaude CodeCodexCursor