Hosted clients

Microsoft Copilot

Add ShopMCP to a Copilot Studio agent with OAuth dynamic discovery, then create an authenticated connection for your Microsoft tenant.

Before you start

Use a work or school Microsoft tenant with access to Copilot Studio and permission to add tools.
Connect at least one platform in ShopMCP under Settings → Integrations.
Confirm that your Power Platform environment permits custom MCP servers and the required data connection.

This guide is for a Copilot Studio MCP tool. Consumer Copilot and personal Microsoft accounts cannot add a private MCP server this way.

1. Add the ShopMCP server

In Copilot Studio, open the target agent, go to Tools, choose Add a tool, then create a new Model Context Protocol tool.

Server name: ShopMCP
Server description: Ecommerce, ads, analytics, lifecycle, finance, and operations tools connected through ShopMCP.
Server URL: https://my.shop-mcp.app/api/mcp

text
https://my.shop-mcp.app/api/mcp

2. Choose OAuth dynamic discovery

For authentication, choose OAuth 2.0, then Dynamic discovery. ShopMCP publishes protected resource, authorization-server, and dynamic client registration metadata, so you do not need to create or paste a client ID or client secret.

Microsoft's current Copilot Studio guidance describes DCR with discovery as the simplest OAuth setup when the server supports it.

3. Create the connection

Create the MCP tool, continue to Create a new connection, and add it to the agent. When Microsoft opens the authentication flow, sign in to ShopMCP, verify the workspace name on the consent screen, and approve access.

ShopMCP recognizes the Microsoft callback and issues the Copilot connection profile. That profile exposes a curated read-only tool surface by default; it does not inherit write access merely because another ShopMCP client can write.

4. Test from the agent

Use ShopMCP to summarize yesterday's orders, refunds, and top products.
Pull last week's GA4 traffic by channel and call out anything unusual.

Publish or test the agent according to your tenant's Copilot Studio workflow.

API-key fallback

If your Copilot Studio environment cannot use dynamic discovery, create a dedicated Microsoft Copilot connection in ShopMCP Settings → Connections. In Copilot Studio, keep the server URL as https://my.shop-mcp.app/api/mcp and configure:

Authentication: API key
Key type: Query
Query parameter: token
Value: smcp_xxxxxxxxxxxxxxxxxxxx

Copy only the value after ?token=. Do not paste the credential-bearing URL into the Server URL field, screenshots, source control, or shared documentation.

Microsoft 365 packaged agent

For tenant pilots that need ShopMCP to appear as a packaged Microsoft 365 Copilot agent, use the operator package in ops/microsoft-copilot. It contains the agent instructions, curated tool selection, and side-load runbook. This is a different distribution path from the Copilot Studio tool above.

Troubleshooting

Dynamic discovery fails — confirm the URL is exactly https://my.shop-mcp.app/api/mcp with no query string, choose OAuth 2.0 → Dynamic discovery, and recreate the draft tool.
No ShopMCP tools appear — confirm the approved ShopMCP workspace has at least one connected integration and that the Copilot connection is active in the correct Power Platform environment.
The agent is blocked by policy — ask a Microsoft 365 or Power Platform admin to review connector and data-loss prevention policies for the environment that hosts the agent.
A tool returns a billing or device message — open the ShopMCP workspace and resolve the billing, plan, or device approval prompt before retrying in Copilot.