Atlassian Rovo

Catalog name rovo. Atlassian’s Rovo MCP server, for Jira and Confluence.

What it’s for

The story lives in Jira, the specification lives in Confluence, and the agent that has to build it lives in your container with neither. So you paste the ticket in, then the acceptance criteria, then the linked page you forgot. This connector removes that errand: the agent reads the issue itself, follows what it links to, and puts its result back where the team looks for it.

It writes as well as reads, with the rights of the account you sign in with. That is worth a thought before you sign in as someone who can close a release.

Add it

At init, or to an existing workbench:

monoceros init acme --with-mcp-servers=rovo

monoceros add-mcp-server acme rovo

Then apply:

monoceros apply acme

Signing in

There is no key to fill. The server authenticates interactively, so the yml entry is one line and the sign-in happens once from inside the container:

mcpServers:
  - name: rovo

How you complete it depends on the agent, and the container opens the browser on your host for you. The full table is in Servers that sign in.

If your company does not allow OAuth apps, this connector is not your route. Use the Atlassian feature instead: twg reaches the same Jira and Confluence with an API token, from the container’s shell.

Where it runs

Remote (http), at https://mcp.atlassian.com/v1/mcp. The request leaves the container, and what the agent asks for is the agent’s decision rather than Monoceros’.

Verify it

monoceros check acme

MCP servers
  rovo → Claude Code
      signs in interactively; authenticate once inside the container

That line means the server is registered with every agent and is waiting for a sign-in. The check holds no grant of its own, so it cannot tell you whether you have already signed in; ask the agent for a Jira issue and see whether it comes back with one.

Remove it

monoceros remove-mcp-server acme rovo