All integrations

Run agents with Atlassian (Jira / Confluence)

Connect Atlassian (Jira / Confluence) once, and every run that names it works in Atlassian (Jira / Confluence) on the account you connected.

Connect Atlassian (Jira / Confluence)Opens Settings → Connections in the console.

What an agent can do in Atlassian (Jira / Confluence)

Work with Jira and Confluence: search, create and update Jira issues and Confluence pages, and manage project content in real time.

Jobs on Rush that use Atlassian (Jira / Confluence)

How Atlassian (Jira / Confluence) connects

Atlassian (Jira / Confluence) is a remote MCP server, published by Atlassian, at https://mcp.atlassian.com/v2/mcp. Connecting it signs in through the MCP OAuth flow on Atlassian (Jira / Confluence)'s side.

From Atlassian: Atlassian (Jira / Confluence)'s MCP documentation · source code.

Connect it once in the console under Settings → Connections, or from your server with POST /me/connections. The sign-in finishes in a browser signed in to the console as the same person, and a link not finished within 10 minutes expires.

After that, a run that names atlassian in connections, or runs a saved agent that names it, gets it; your connections reach no run that does not name them.

POST https://api.phoenix.so/me/connections

{
  "type": "mcp",
  "name": "Atlassian",
  "url": "https://mcp.atlassian.com/v2/mcp"
}

Whose Atlassian (Jira / Confluence) account the agent uses

Your Atlassian (Jira / Confluence) connection is personal: it belongs to the person who signed in. A run started in the console uses that person's Atlassian (Jira / Confluence), and a run started with an API key uses the Atlassian (Jira / Confluence) of the member who created the key.

To act for your own app's users, make each user an agent from your template and show them, signed in to your app, the sign-in link POST /o/{org}/agents/{agent}/connections returns. They sign in to their own Atlassian (Jira / Confluence), and that agent's runs use their account and nothing else: never yours, never another user's.

More Project Management integrations

Frequently asked questions

How do I connect Atlassian (Jira / Confluence) to Rush?

Open Settings → Connections in the console and connect Atlassian (Jira / Confluence), or send POST /me/connections with {"type":"mcp","name":"Atlassian","url":"https://mcp.atlassian.com/v2/mcp"} and open the authorize_url it returns while signed in to the console. The connection reads pending until the sign-in finishes, then connected.

Does every run get my Atlassian (Jira / Confluence) account?

No. A run gets your Atlassian (Jira / Confluence) connection only when it names it in connections ("connections": ["atlassian"]), or runs a saved agent that names it. A saved agent names its connections once, and every run of it gets them.

What can an agent do in Atlassian (Jira / Confluence)?

Work with Jira and Confluence: search, create and update Jira issues and Confluence pages, and manage project content in real time. 9 published jobs use it; this page lists them.

Can my app's users connect their own Atlassian (Jira / Confluence)?

Yes. Make each user an agent from your template, and they sign in to their own Atlassian (Jira / Confluence) through the link POST /o/{org}/agents/{agent}/connections returns. That agent's runs use their account alone.

Keep reading