Amplify's AI Assistant can be added to a Microsoft Copilot Studio agent as a custom tool using the Model Context Protocol (MCP). Once connected, the agent can answer questions about Amplify data — initiatives, benefits, costs, RAID items, tasks — using the permissions of whoever authenticates the connection.

Setup has two parts:

1. In Amplify — collect the MCP connection details (Administrator).
2. In Copilot Studio — add Amplify as an MCP tool on the agent, then connect (Agent maker / Copilot Studio access).

Prerequisites

• Administrator privileges in Amplify.
• Access to Microsoft Copilot Studio, with permission to edit the target agent and add tools.
• The agent must already exist and be built on the standard harness.

Step 1: Collect the MCP connection details in Amplify

All of the values Copilot Studio asks for are found in one place in Amplify.

1. Click your avatar in the top right corner.
2. Click Administration in the menu.
3. Go to Authentication in the side menu.
4. Scroll to the AI Assistant (MCP) OAuth section.

From this section, gather the following:

MCP Server URL

Copy the MCP Server URL. You will paste this into Copilot Studio as the Server URL in Step 2.

Allow DCR

Turn on Allow DCR (Dynamic Client Registration). This lets Copilot Studio register itself with Amplify automatically, rather than you creating and pasting credentials by hand — this maps to the Dynamic discovery (or Dynamic) OAuth 2.0 option in Copilot Studio.

Leave this enabled for the life of the connection. Turning it off later can break the connector's ability to refresh its registration.

Client ID / Client Secret

Only needed if you use the Manual OAuth 2.0 option in Copilot Studio instead of Dynamic discovery (not recommended — see Step 2). If asked, copy these from this section. Treat the client secret like a password — paste it straight into Copilot Studio, do not email it or store it in a shared document.

Redirect Whitelist URL

Confirm the following URL is on the Redirect Whitelist, then click Save:

https://global.consent.azure-apim.net/redirect

Most instances already have this from setting up the Microsoft 365 Copilot federated connector. If your instance doesn't have it yet, add it now. If Copilot Studio displays a separate callback URL during Step 2 (this can happen with the Dynamic, non-discovery option), add that URL here too.

Step 2: Add Amplify as an MCP tool in Copilot Studio

1. Open the agent in Copilot Studio and go to the Tools page.
2. Select Add a tool.
3. Select New tool.
4. Select Model Context Protocol. The MCP onboarding wizard appears.
5. Fill in:
   • Server name — a name your agent maker will recognise, e.g. Amplify.
   • Server description — a short, clear line on what Amplify is used for. The agent orchestrator uses this to decide when to call the tool, so be specific (e.g. "Amplify strategy execution platform — initiatives, benefits, costs, RAID items, tasks").
   • Server URL — the Amplify MCP Server URL from Step 1.
6. Under Authentication, select OAuth 2.0.
7. For Type, select Dynamic discovery (this is the option that matches Amplify's Allow DCR setting, and needs no manual client credentials).
8. Select Create to add the server.
9. Select Next. The Add tool dialog appears.
10. On the connection picker, select Create new connection (this may show as a Not connected status first — click it, then choose Create new connection).
11. Sign in on the Amplify login page that appears, and approve access.
12. Select Add to agent to finish.

Amplify's tools now appear in the agent's Tools list.

Step 3: Test the tool

1. Open the Test / Preview pane for the agent.
2. Ask a question that needs Amplify data, e.g. "What initiatives are currently at risk?"
3. Check the activity/trace panel to confirm the Amplify tool was invoked and returned data.

Access is read-only, and the agent only returns the Amplify data visible to whichever Amplify account authenticated the connection in Step 2. Connecting in Copilot Studio does not grant access to data that account could not already see in Amplify.

Troubleshooting

• The Model Context Protocol option isn't available when adding a tool. The agent may be on the newer GitHub Copilot harness, which doesn't yet expose this configuration wizard. Confirm which harness the agent uses.
• Sign-in works but the connection fails at the end. Almost always the redirect/callback URL. Return to the AI Assistant (MCP) OAuth section in Amplify and confirm https://global.consent.azure-apim.net/redirect is in the Redirect Whitelist. If Copilot Studio showed a different callback URL during setup, add that too.
• Registration or token errors. Confirm Allow DCR is still enabled in Amplify. If you're using the Manual OAuth option instead, confirm the Client ID and Client Secret in Copilot Studio match the current values in Amplify.
• The agent connects but returns no Amplify data, or the wrong data. Check the permissions of the Amplify account used to authenticate the connection in Step 2 — the agent can only return what that account can see.

If the problem persists, contact Amplify Support with the agent name, the Amplify instance URL, and the exact error message shown. Do not include the client secret.