Connect Magento to Microsoft Copilot via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Magento (Adobe Commerce), paste your credentials, mint an MCP API key — done. No Docker, no git clone, no local server.

Magento (Adobe Commerce) + Microsoft Copilot

Drive Magento 2 / Adobe Commerce from any AI agent: products, categories, orders, customers, stock. 48 tools, Bearer admin-token auth, per-store base URL.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

MAGENTO_BASE_URL, MAGENTO_ACCESS_TOKEN

Step 1 — Get credentials

Setup:

1. As Magento admin → System → Integrations → Add New Integration.
2. Name + email, then on the API tab pick scopes: at minimum Catalog (Products + Categories + Stock), Customers, Sales (Orders + Invoices + Shipments). For the newer tools also grant Sales (Credit Memos), Carts, Marketing (Cart Price Rules) and Stores (Product attributes), and Content (Pages + Blocks) for the CMS tools.
3. Activate the integration → grant access. Magento generates an Access Token (this is the long-lived bearer token).
4. Set:
   • MAGENTO_BASE_URL = your storefront base URL (e.g. https://shop.example.com)
   • MAGENTO_ACCESS_TOKEN = the integration access token
   • There is no store view setting: requests go to the default store view, the guest cart tools take the store view code as their storeCode parameter (default unless you pass another code from magento_list_store_views), and CMS pages and blocks always use all

Authentication: Authorization: Bearer ${MAGENTO_ACCESS_TOKEN}.

…(continued in the in-app connector instructions)

Promotions, prices and stock per source: cart price rules and their coupon codes (find, read, create and change rules; add a code or generate a batch), special prices per SKU, store and period (read and schedule), Multi-Source Inventory stock per source (read and set), options of select attributes such as color or size (list and add), product changes in a chosen scope (magento_update_product_in_scope, all for the values every store view inherits), shopping carts (find open carts, for example to follow up abandoned baskets) and credit memos (read). These tools install switched on and need the extra API resources from point 2; before every change the AI shows you what it will write and waits for your yes.

Already installed? The new tools reach a connector you installed earlier through its catalog update: open the connector in AnythingMCP and, under Catalog update available, check the list of new tools and click Apply update. Your credentials and any tools you added yourself stay as they are.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Microsoft Copilot

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.

1. In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
2. Enter a Server name (for example AnythingMCP), a Server description that says what the connector does, and the Server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server.
3. Under authentication, choose API key, set Type to Header and the header name to X-API-Key, then select Create.
4. In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
5. Try it in the agent's Test pane: ask for something that needs the Magento (Adobe Commerce) tools.
6. Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.

Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.

Available tools

FAQ

Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.

What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.

The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT
• Connect to Cursor
• Connect to Gemini
• Connect to Meta Muse