Connect Strapi to Microsoft Copilot via MCP

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

Strapi 5 + Microsoft Copilot

Connect to a Strapi 5 instance to check its availability, query documents from collection types, and retrieve individual documents through the read-only REST Content API.

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:

STRAPI_URL, STRAPI_API_TOKEN

Step 1 — Get credentials

Setting up takes about 2 minutes. You need a Strapi 5 instance and a read-only Content API token.

1. Set STRAPI_URL to the root URL of your Strapi instance, for example https://cms.example.com, without /api at the end.
2. In the Strapi admin, open Settings → API Tokens and create a Content API token with read-only access to the collection types the AI should see. Copy it into STRAPI_API_TOKEN. It is sent only in the Authorization Bearer header.
3. Install the connector and run strapi_health to check that Strapi is reachable. Then run strapi_list_documents on a collection you know, such as articles: only that shows the token works, because strapi_health does not check the token or its permissions.

Where Strapi runs: Strapi Cloud and any other publicly reachable Strapi 5 instance work from AnythingMCP Cloud. An instance on a private network, on localhost or at a private IP address works only with self-hosted AnythingMCP, and its host must be allowed through SSRF_ALLOWED_HOSTS, because the outbound guard blocks private address space by default.

What it reads: documents from one collection type at a time. You address a collection type by its plural API ID, such as articles, not by its display name, and the connector cannot discover the collection types for you. strapi_list_documents supports field selection, Strapi filter operators, sorting (field:asc or field:desc), page-based pagination, populate for relations or media, locale for localized content and status for published or draft documents; it keeps Strapi's meta, so pagination information stays available. strapi_get_document fetches one document by its Strapi 5 documentId. Relations, media, components and dynamic zones come back only when populate asks for them.

Read-only: all three tools are GET requests. The connector cannot create, update, publish, unpublish or delete content.

The connector works with the Strapi 5 REST Content API only: it does not support Strapi 4 response shapes or the Admin, Content Manager and Content-Type Builder APIs.

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 Strapi 5 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