JIRA & CONFLUENCE MCP SERVER

Connect Jira and Confluence to Andromity with the Atlassian MCP server

Use the Atlassian Rovo MCP server with Andromity: search Jira with JQL, update issues and read Confluence pages from your AI coding agent. Sign-in, admin controls and limits.

Server
https://mcp.atlassian.com/v2/mcp
Connects with
Browser sign-in (OAuth)
Category
Productivity

Atlassian’s Rovo MCP server gives MCP clients access to Jira and Confluence Cloud at https://mcp.atlassian.com/v2/mcp. Connected to Andromity, the agent can read the Jira ticket and the Confluence design doc behind a change, then update the ticket when the work is done.

You sign in with your Atlassian account in the browser. The server acts with your existing Jira and Confluence permissions.

What the agent can do with Jira & Confluence

  • Read Jira issues, search them with JQL, and list projects, boards, sprints, comments and transitions.
  • Create and edit Jira issues, move them through workflow transitions, add comments and worklogs, and link issues.
  • Search Confluence with CQL, read pages, and create or update content.
  • Search across Jira, Confluence and connected apps (marked beta by Atlassian).
  • List the Atlassian sites your account can access.

Example prompts

Ask for the work in plain language. Naming the server helps, for example “use the Jira & Confluence MCP server”.

  • Read PROJ-1042 in Jira, implement it, then move the issue to “In Review” with a comment linking this branch.
  • Find the Confluence page about our rate limiting design and check this middleware against it.
  • Search Jira for open bugs in the API project mentioning “timeout” and rank them by how likely this change fixes them.

Connect Jira & Confluence

  1. In VS Code, open Andromity Hub → MCP Servers → Discover. In the terminal app, open /settings → MCP → + Connect an app. Find Jira & Confluence and select Connect.
  2. Sign in with Atlassian in your browser and approve access to your site.
  3. Andromity saves the server to ~/.andromity/mcp.json and connects it.

See Connect an app for how Andromity stores connectors and tokens.

Access and safety

  • The server uses your existing Atlassian permissions; it can’t reach projects or spaces you can’t.
  • Atlassian admins can turn off API-token sign-in, keep an allowlist of client domains, and apply IP allowlists to MCP connections.
  • Jira delete tools and project-management tools are disabled by default.

In an untrusted folder, MCP servers don’t start at all. Read workspace trust and permission modes for the full model.

Limits to know

  • Usage is metered in Rovo credits; Atlassian says search tools consume credits.
  • Atlassian moves v1 traffic to v2 automatically on March 1, 2027. Andromity already uses v2.

Questions

Can Andromity read Jira tickets?
Yes. Through Atlassian’s Rovo MCP server the agent can search Jira with JQL, read issues and comments, and update issues with your permissions.
Does it work with Confluence too?
Yes. The same server searches Confluence with CQL and can read, create and update pages.
Does my Atlassian admin need to approve it?
Admins can restrict which client domains and IP addresses may connect. If your organization uses those controls, ask your admin.

Sources

This guide is based on Jira & Confluence’s own documentation. The app controls its server, so tools can change; check the source for the current list.

Jira & Confluence is a trademark of its owner. Andromity is not affiliated with or endorsed by Jira & Confluence.