# Your Jira and Confluence. One clear answer. Source: https://corespeed.io/integrations/atlassian 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. ## Set up an agent Give your agent this line: `set up https://corespeed.io/SKILL.md (read it raw, e.g. with curl)` It fetches the skill at https://corespeed.io/SKILL.md, adds the CoreSpeed MCP server, signs you in (or up), and keeps the skill for next time. Connect Jira & Confluence after setup. Access follows the connected account and its permissions. Create an account: https://app.corespeed.io/sign-up ## 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. You ask your agent: "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." It calls CoreSpeed: - `atlassian__jira_search`: ok, 512 ms - `atlassian__confluence_search`: ok, 388 ms - `atlassian__confluence_get_page`: ok, 446 ms It reads from: Jira & Confluence. ### Sprint summary: Sprint 14, against the plan. Refund retries are on track. The rounding fix is blocked, and the rollout has no sign-off yet. **Moving** - Refund webhook retries are in progress. **Needs a decision** - Unblock the currency rounding fix before the release. - Name who signs off on the staged rollout. _Illustrative example · Fictional data · No issues or pages changed_ All connectors: https://corespeed.io/docs/connectors ## From the sprint board to the page that explains it Requests you can make once Jira & Confluence is connected. The data is fictional. ### Catch up on the sprint PAY · Sprint 14 · Board and sprint - In progress: Refund webhook retries - Blocked: Currency rounding fix - From the projects you can access ### Read the page behind the work Payments · release plan · Confluence - Scope: Retries and rounding - Open question: Who signs off on the rollout? - Read, not edited ### Hold a transition for review Move an issue to Done · Example approval policy - Policy: Ask before closing an issue - Outcome: The move waits for a person - Approval required Full example: https://corespeed.io/solutions/agent-approvals (Markdown: https://corespeed.io/solutions/agent-approvals.md) ## 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 guides: Claude Code https://corespeed.io/docs/mcp#claude-code · Codex https://corespeed.io/docs/mcp#codex · Cursor https://corespeed.io/docs/mcp#cursor ## Questions ### Does it cover Jira and Confluence in one connection? Yes. One Atlassian connection serves both Jira and Confluence on the connected site. ### Can my agent use JQL? Yes. The Jira search tool takes a JQL query, so your agent can ask for a sprint, an assignee or a status directly. ### Does this send or change anything on its own? No. These examples read context and draft a result. Sending or changing a record is a separate tool call, which approvals can hold for a person. How approvals work: https://corespeed.io/docs/approvals ### Do I have to switch agents? No. CoreSpeed adds tools to the agent you already use: Claude Code, Codex, Cursor, or another MCP client. Each one signs in once. ### Can my agent access every account in our organization? No. Access follows your CoreSpeed identity, each connection's visibility, and the app's own permissions. Personal connections stay private. ### Does this work without connecting an account? No. Connect the app's account first; your CoreSpeed workspace shows what each app needs. The examples on this page use fictional data. All connectors: https://corespeed.io/docs/connectors Every tool and price: https://corespeed.io/catalog/atlassian ## Related pages - [Approval gates for AI agent tool actions](https://corespeed.io/solutions/agent-approvals): Set approval policies for writes through CoreSpeed. Review held tool actions while your team keeps using its preferred agents. - [ClickUp for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/clickup): Bring ClickUp tasks, lists and comments into your agent. Find what is overdue or unassigned and draft the standup. - [Linear for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/linear): Bring Linear issues and project context into your agent. See what is moving and what needs attention. - [Productboard for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/productboard): Bring Productboard features and customer notes into your agent. Draft what customers ask for, tied to the features. - [Trello for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/trello): Bring Trello boards, cards and checklists into your agent. See what is stuck or half done, and draft the board summary. ## Sources - Connectors: https://corespeed.io/docs/connectors - Jira Cloud REST API: https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/ - Confluence Cloud REST API: https://developer.atlassian.com/cloud/confluence/rest/v2/intro/ Reviewed 2026-11-10. ## Links - Product overview: https://corespeed.io/ (Markdown: https://corespeed.io/index.md) - All integrations: https://corespeed.io/integrations (Markdown: https://corespeed.io/integrations.md) - Documentation: https://corespeed.io/docs - Pricing: https://corespeed.io/pricing (Markdown: https://corespeed.io/pricing.md)