Krosoft Wiki
Auto Light Dark
Krosoft Wiki
Auto Light Dark
Breadcrumbs

Set up Microsoft Copilot Studio

Connect a Microsoft Copilot Studio agent to MCP for Confluence Data Center using a Confluence personal access token (PAT).

Before you start

You need Copilot Studio access, an environment with Dataverse, and MCP for Confluence Data Center installed on your Confluence site. Microsoft’s cloud service must be able to reach the MCP endpoint over HTTPS; a localhost address or a site reachable only from your laptop will not work.

Have your site address and PAT ready. See Connect your MCP client for token creation and connection settings. Requests use the Confluence permissions of the account that owns the PAT. Review who can use the connection before sharing the agent.

1. Add the MCP server

In Copilot Studio, open or create a standard agent. Go to Tools → Add a tool → Model Context Protocol (under Create new). Enter a server name and a short description of the Confluence content it provides.

Set Server URL to:

https://confluence.example.com/confluence/rest/native-mcp/1.0/mcp

Replace https://confluence.example.com/confluence with your Confluence base address, including its context path. Keep /rest/native-mcp/1.0/mcp at the end.

2. Configure authentication

Select API key → Header. Set Header name to Authorization, then select Create.

Choose Create new connection. In the masked credential field, enter Bearer <your-PAT>, including Bearer and one space before the token. Select Create, then Add and configure. Keep the PAT out of chat messages, shared files and screenshots.

3. Verify the connection

Check that the Confluence tools appear. Enable only the tools your agent needs. In Test your agent, ask: “Which Confluence account are you using? Use confluence_get_current_user.” Confirm the expected account, then try a search for a page you can read.

For realistic questions and response formatting, see Example prompts and responses.

If the connection fails

  • Authentication fails: check the PAT, its expiry, and the single Bearer prefix.

  • Endpoint unavailable: check HTTPS reachability from Microsoft, the context path, and your organisation’s connector policies.

  • Copilot Studio keeps loading: check the selected environment has Dataverse and that your account has Copilot Studio access.

A free trial supports testing in Copilot Studio’s chat panel. Publishing to Teams or SharePoint requires the appropriate Microsoft licensing and channel configuration; it is a separate step. See Microsoft’s MCP setup and licensing guidance.