Connect Atlassian (Jira / Confluence) to Copilot Studio
Search, read and write Atlassian (Jira / Confluence) from Copilot Studio. Arlet links the two through one MCP connection and takes care of keys and authentication.
Arlet makes Atlassian's official MCP server (Rovo MCP) available from the AI client you already use. There is no app to create on the Atlassian side. Signing in completes the connection.
The AI can search, create, update and transition Jira issues, and search, read, create and update Confluence pages. The available tools are those provided by Atlassian's official server, and what can be read or written is exactly what your Atlassian account can. If your organization admin restricts connecting domains, ask them to allow Arlet's domain.
How to connect Atlassian (Jira / Confluence) to Copilot Studio
- 1
In the Arlet dashboard, open Integrations → Add an integration and choose Atlassian (Jira / Confluence). Sign in with Link Atlassian (Jira / Confluence), name the connection and click Create.
- 2
Sign in to Copilot Studio with your work account, create a new agent (or open an existing one), and in the Build tab choose Tools → + → Add → Model Context Protocol (MCP) in the right panel.
- 3
In the Add MCP server form, enter "Arlet" as the Server name, https://mcp.arlet.dev/mcp/ as the Server URL, choose OAuth 2.0 for Authentication and "Dynamic (detected)" for Configuration type, then click Add. No Client ID / Secret is needed.
- 4
On the Select a connection screen, choose Create new connection → Create, then sign in with Google on the Arlet authorization screen and click Allow. Click Add to attach the tool to the agent, then Publish to use it from Microsoft 365 Copilot.
Requires a Microsoft work account and a Copilot Studio license (or trial). MCP is available only for agents using generative orchestration and not in Copilot Studio in Teams.
What you can do
Atlassian (Jira / Confluence) tools that Copilot Studio can call.
searchJiraIssuesUsingJqlSearch Jira issues with JQL.
getJiraIssueGet one issue in full, including description, status, assignee and custom fields.
createJiraIssueCreate an issue.
editJiraIssueUpdate an issue.
transitionJiraIssueMove an issue to another status.
addOrEditJiraIssueCommentAdd or edit a comment on an issue.
listJiraProjectsList projects.
listJiraBoardSprintsList the sprints of a board.
getJiraBoardSprintDataGet the issues and progress of a sprint.
searchConfluenceSearch Confluence pages and blog posts with CQL.
getConfluenceContentRead a page's content.
createConfluenceContentCreate a page.
updateConfluenceContentUpdate a page.
listConfluenceSpacesList spaces.
createConfluenceCommentComment on a page.
discoverDescribe what you need in plain language to find the matching Jira or Confluence tool.
The tool list follows what Atlassian (Jira / Confluence)'s official MCP server provides and may change.
Example uses
Report on the sprint
Tally the current sprint's issues by status and write a progress report naming what is late and who owns it.
Turn meeting notes into issues
Pull decisions and action items out of notes and file them as Jira issues with the right project, assignee and labels.
Trace a spec decision
Search Confluence pages and Jira issues together to explain why a feature ended up the way it did.
Write release notes
Collect the issues completed this week and create a release-notes page in Confluence.
Prompts you can use as-is
- List the issues in the current sprint that have been In Progress for more than 3 days, with assignees
- Extract the action items from these meeting notes and create issues in the PROJ project with assignees
- Find the Confluence page and related Jira issues where we decided the payment redesign spec, and explain the history
- Summarize the issues marked Done this week and create a release-notes page in the Releases space in Confluence
