Microsoft Copilot

ShopMCP stays the remote MCP server. Copilot Studio creates an agent that can call that server from Microsoft 365 Copilot Chat, subject to your tenant's Power Platform and Copilot policies.

• Copilot Studio MCP tool: best first setup. It supports a Streamable HTTP MCP server and API-key query authentication.
• Microsoft 365 declarative agent: packaged tenant pilot. Use this when an admin wants ShopMCP to appear as a Microsoft 365 Copilot agent. This path uses OAuth for MCP plugins.
• Federated Copilot connector: future distribution path. This is read-only, admin-governed, and currently best treated as a Microsoft partnership or marketplace milestone after real tenant pilots.

In ShopMCP, open Settings → Connections and choose Create Copilot connection. ShopMCP creates a dedicated Microsoft Copilot key with the Copilot profile applied.

• The key is scoped to active connected modules and can be edited like any other additional MCP URL.
• Copilot profile keys expose a curated read-only tool set by default, even if the workspace later enables write tools for another client.
• Copy the full URL when it appears. ShopMCP only shows it once.

text
https://my.shop-mcp.app/api/mcp?token=smcp_xxxxxxxxxxxxxxxxxxxx

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

Choose API key authentication and send the key as a query parameter.

• Type: Query
• Query parameter name: token
• API key value: smcp_xxxxxxxxxxxxxxxxxxxx

If ShopMCP gave you a full URL, copy only the part after ?token= into the API key value field.

After Copilot Studio creates the MCP tool, create a new connection for it and add the tool to your agent. The first time a user runs the agent, Microsoft may ask them to approve or create the connection depending on your tenant policy.

Try a question that matches the modules granted to the Copilot key:

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

ShopMCP also publishes OAuth discovery metadata for MCP clients that require a sign-in flow. Microsoft clients that redirect through the supported Teams, Power Platform, or Agents Toolkit callback URLs receive a dedicated Microsoft Copilot scoped key instead of the workspace primary key.

For tenant pilots that need ShopMCP to appear as a packaged Microsoft 365 Copilot agent, use the ShopMCP operator package in ops/microsoft-copilot. It includes the agent instructions, recommended tool selection, and side-load runbook for Agents Toolkit.

• Import the remote MCP server with https://my.shop-mcp.app/api/mcp.
• Select the curated ShopMCP tools listed in the package instead of importing every available module tool.
• Use OAuth registration for the MCP plugin path, then provision and side-load into a tenant where custom app upload and Copilot access are enabled.

• Copilot can't connect — confirm the server URL is https://my.shop-mcp.app/api/mcp, auth type is API key, key type is Query, and the query parameter is exactly token.
• No ShopMCP tools appear — check that the ShopMCP key can reach at least one connected module in Settings → Connections.
• 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.