An MCP server for interacting with Strapi CMS.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mm-strapi-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Strapi MCP Server An MCP server for interacting with Strapi CMS. ## Installation You can install the server using pip: ```bash pip install strapi-mcp-server ``` ## Configuration Before using the server, you need to create a configuration file at `~/.mcp/strapi-mcp-server.config.json`. 1. Create the directory: ```bash mkdir -p ~/.mcp ``` 2. Create the configuration file: ```bash touch ~/.mcp/strapi-mcp-server.config.json ``` 3. Add your Strapi server details to the file. You can add multiple servers. ```json { "prodserver": { "api_url": "https://your-strapi-instance.com", "api_key": "your-strapi-api-key" }, "localserver": { "api_url": "http://localhost:1337", "api_key": "your-local-api-key" } } ``` ## Usage Once installed and configured, you can run the server from your terminal: ```bash strapi-mcp-server ``` This will start the MCP server, and you can then interact with it using an MCP client.
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.