Connect Wix to Microsoft Copilot via MCP

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

Wix + Microsoft Copilot

Wix website and online business: site details, Wix Stores products, eCommerce orders, contacts, Wix Bookings appointments and services, and blog posts. Wix REST API with an API key, one site per connector.

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:

WIX_API_KEY, WIX_SITE_ID

Step 1 — Get credentials

1. Sign in to Wix as the account owner or a co-owner and open the API Keys Manager (manage.wix.com/account/api-keys). Only owners and co-owners can create keys.
2. Click Generate API key. Give the key access to the site you want to connect (or to all sites) and the permissions for the Wix apps you use: site properties, Wix Stores, eCommerce orders, contacts, Wix Bookings and Wix Blog. Read permissions are enough for every tool except wix_create_contact, which needs permission to manage contacts.
3. Copy the key into WIX_API_KEY.
4. Open the site's dashboard in Wix. The site ID is the UUID after /dashboard/ in the browser address (for example 1a2b3c4d-1234-5678-9abc-1234567890ab). Put it in WIX_SITE_ID and install the connector.
5. Start with wix_get_site_properties: it checks the key and the site ID and tells what kind of site it is (store, restaurant, blog...).

One connector covers one site; add the connector again for another site. A key only works on sites owned by the Wix account that created it.

For a shop, call wix_get_catalog_version once. Wix Stores runs either catalog V3 (newer sites) or catalog V1, and each answers only its own API: on V3_CATALOG use wix_search_products and wix_get_product, on V1_CATALOG use wix_query_products_v1 and wix_get_product_v1. STORES_NOT_INSTALLED means the site has no Wix Stores app. Orders (wix_search_orders, wix_get_order) come from Wix eCommerce and work with both catalog versions.

The Stores, Bookings and Blog tools only work when that app is installed on the site. A 404 from one of them usually means the app is missing, and the 401 error No blog instanceId found means Wix Blog is not installed. A 403 means the key lacks the permission for that app or has no access to the site: edit the key in the API Keys Manager.

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 Wix 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