Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Atlassian Rovo MCP for Microsoft Copilot Cowork show me my open Jira issues"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A reproducible Microsoft 365 app package, Jira project-tracking skill, and technical investigation of Dynamic Client Registration (DCR) behavior in Microsoft 365 Copilot Cowork.
An earlier Cowork article said that connectors for DCR-enabled MCP servers could omit the manifest authorization object. That path did not produce a usable connection in this reproduction. The working package uses:
dcr/register in m365agents.yml to register a client with Atlassian and create an authentication configuration in the Microsoft Enterprise Token Store.
OAuthPluginVault.referenceId in appPackage/manifest.json to bind the connector to that stored configuration.
Microsoft's dedicated DCR documentation, updated in August 2026, now describes this explicit auth-config pattern. This repository records the documentation drift, evidence boundaries, refresh-token gap, and CIMD questions without claiming that automatic runtime DCR fails in every tenant.
Related MCP server: MCP Atlassian Server
appPackage/: Cowork plugin, static MCP tool descriptions, and Jira skill.
m365agents.yml: DCR registration, packaging, update, and publication lifecycle.
docs/: Docusaurus investigation and reproduction wiki.
scripts/check-oauth-metadata.ps1: live OAuth discovery-chain check.
REPRO_RESULTS.md: dated observed results and unresolved validation.
npm install
Copy-Item env/.env.dev.example env/.env.dev
atk auth login m365
atk provision --env dev --interactive false
atk validate --env dev --interactive false
npm run buildProvision only in a test tenant. Generated environment files can contain deployment identifiers and are excluded from Git.
The full wiki is published at dayour.github.io/atlassian_cowork. Start with the DCR finding and controlled test matrix.
The full build and installation guide explains the DCR fix, provisioning-time registration, manifest binding, environment configuration, ZIP packaging, Personal installation, manual upload, and tenant publication. It distinguishes verified behavior from untested refresh and distribution scenarios. Each independent publisher must provision their own app and authentication configuration.
Download the provisioning template, complete source ZIP, and checksums from Release v1.1.2. The same template is distributed as @dayour/atlassian-cowork through GitHub Packages. See download and extraction instructions. These are source distributions, not preconfigured Teams installation ZIPs. GitHub's npm registry requires authentication; the public release assets provide an alternative download route.
Explicit Toolkit DCR registration: verified.
Atlassian consent and authorization-code callback: verified.
Authenticated Rovo MCP call: reported working by the project owner.
Automatic DCR with omitted authorization: not yet isolated in a clean A/B title test.
Refresh-token issuance and post-expiry renewal: not yet captured.
Cowork CIMD configuration path: no public Microsoft guidance identified.
MIT. This is an independent interoperability reproduction and is not an official Microsoft or Atlassian project.
This server cannot be deployed
Connect to Atlassian Jira, Confluence, Loom, and more to search, create, and manage your work.
Permissioned access to Outlook, OneDrive and Teams via the user's own Microsoft account
One place to build, share, and govern the skills and tools your AI agents use at work.
Search & install 6,500+ AI agent skills from skills-hub.ai inside any MCP tool.
