Summary
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.
Guided setup
Connect Strapi 5 to Claude, ChatGPT or Copilot in 2 minutes
Start a free trial on AnythingMCP Cloud, connect Strapi 5 in the guided setup, then add your MCP URL to your AI assistant. No code and no server to run.
No credit card · 7-day trial · Self-host alternative available
Try asking
Example prompts for Strapi 5
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 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
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.
Setup
Setting up takes about 2 minutes. You need a Strapi 5 instance and a read-only Content API token.
- Set
STRAPI_URLto the root URL of your Strapi instance, for examplehttps://cms.example.com, without/apiat the end. - 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. - Install the connector and run
strapi_healthto check that Strapi is reachable. Then runstrapi_list_documentson a collection you know, such asarticles: only that shows the token works, becausestrapi_healthdoes 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.
Prerequisites: STRAPI_URL, STRAPI_API_TOKEN
Install the connector locally
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
Open http://localhost:3000/connectors/store, pick Strapi 5 and paste in the env vars listed under Prerequisites.
Available tools
| Tool | What it does |
|---|---|
strapi_health | Check whether the configured Strapi 5 process is reachable |
strapi_list_documents | List documents from one Strapi 5 collection type, with field selection, deep filters, sorting, page-based pagination, relation population… |
strapi_get_document | Retrieve one document from a Strapi 5 collection type by its documentId, optionally selecting scalar fields, populating relations or media… |
Next steps
Was this guide helpful?