Connect Atlassian (Jira & Confluence)
The Atlassian connector uses Atlassian's Rovo MCP server, so skills can search and update Jira, Confluence, and Compass with each person's own Atlassian access.
What you need
- Atlassian accounts for the people who will use it. Each person connects their own account, and tools run with that account's permissions.
- A Harriet role that can manage provisioning; the Add connector button is disabled otherwise. See roles and permissions.
- No OAuth app registration on your side. Unlike Slack and Asana, this template asks for no credentials at install.
Atlassian's own guide is at Getting started with the Atlassian Remote MCP Server.
Install the connector
- Open Connectors. Then select Add connector to open the catalog.
- Pick Atlassian (Jira & Confluence). The card carries a Hosted badge: Atlassian runs the MCP server and Harriet connects to it over HTTPS. The wizard shows the notice "Users connect their accounts under Profile → Integrations after this skill is assigned."
- Step through the fields. The wizard reports "No extra fields required." for this template, so there is nothing to fill in.
- Select Install Atlassian (Jira & Confluence). Harriet creates the connector and syncs its tool list from the Rovo server.
- Create a skill, or skip. Pick a published use case and Harriet creates the skill with the connector attached, or choose Skip — connector only and attach it later from skill authoring.
Server URL and tool access live in Integration settings after install; restrict individual tools under tool permissions.
Authorize
Authorization is per person. Each person connects their Atlassian account under Profile → Integrations the first time they need the connector, and every tool call then runs with their permissions. See per-user OAuth connections.
Because tools run with each person's Atlassian permissions, two people running the same skill can see different results. A page or project someone cannot open in Atlassian stays invisible to their skills too.
Tools you get
The tool list is synced from Atlassian's Rovo MCP server at install. Per the catalog entry, it spans searching and updating Jira, Confluence, and Compass. Review the exact synced list in Integration settings, since Atlassian controls what its server exposes.
Try it
Assign a skill that uses this connector, then ask: "Summarize the open issues in our support project and draft a status update for the team's Confluence space."