Configure and expose the Dynamics 365 Commerce MCP server (public preview) so Copilot Studio, ChatGPT, and Azure AI Foundry agents can browse catalog, build carts, and complete checkout against a Commerce Scale Unit
domain: learn.microsoft.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm prerequisites: a Dynamics 365 Commerce environment with at least one Commerce Scale Unit on version 10.0.48 or later, and Lifecycle Services access to manage that environment
Enable the Commerce MCP server (public preview) against your Commerce Scale Unit so it exposes catalog, cart, discount, inventory-lookup, and checkout tools
Connect a compliant MCP client -- Microsoft Copilot Studio, ChatGPT, Azure AI Foundry, or a custom agent host -- to the MCP server endpoint
Scope tool access to match the connecting agent's security role and environment context, since the MCP server exposes tools based on that context rather than a single fixed permission set
Test the full agent journey end to end: product discovery, cart building, in-store inventory checks, discount application, checkout, and order tracking
Monitor the preview program's release notes closely, since capabilities and required Commerce Scale Unit versions are actively evolving
Known gotchas
This is a public preview feature -- expect breaking changes and do not treat it as production-stable without your own fallback path
Tool access follows the connecting agent's security role, so a misconfigured role can either over-expose sensitive commerce data or block legitimate agent actions -- test both directions
This is a Dynamics 365-specific integration; it does not interoperate automatically with ACP, UCP, or other commerce protocols without additional bridging work
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?