MCP: Strapi MCP Server
by Strapi
Built into Strapi 5.47+, this MCP server turns your own content types into agent-callable tools — CRUD, publish and draft control, scoped by Admin token permissions.
Payload's official MCP plugin — exposes every collection and global of a Payload CMS instance as MCP tools at /api/mcp, gated by Payload access control.
Set up this MCP server in your favorite AI agent — copy a ready-made configuration below.
The Payload MCP Plugin is the official Model Context Protocol integration for Payload, the TypeScript-native headless CMS and app framework built on Next.js. It is published from the Payload monorepo as @payloadcms/plugin-mcp, and it turns an existing Payload instance into an MCP server rather than asking you to write one.
Installation is a single plugin entry — plugins: [mcpPlugin({})] in the Payload config — after which every configured collection and global is reachable through a set of generic tools served over Streamable HTTP at /api/mcp. The discovery and CRUD surface is stable: getConfigInfo lists the available slugs, getCollectionSchema and getGlobalSchema describe their shape, and findDocuments, createDocuments, updateDocument, deleteDocuments, findGlobal and updateGlobal operate on them. Individual tools are switched off with plain keys such as tools: { delete: false }.
Access control is the part worth understanding. Results are filtered by Payload's own access rules rather than by a parallel permission model, so an agent sees exactly what the authenticating user would see through the API. Tools, prompts and resources can additionally be gated with code-level access callbacks, and auth-enabled collections can opt into login, auth, forgotPassword, resetPassword, unlock and verify tools. The quick-start URL carries ?overrideAccess=true, which skips access control and is meant for local development only — outside development you remove it and send Payload authorization instead.
File uploads avoid the usual problem of stuffing binary data into tool arguments: getUploadInstructions hands back an HTTP request or a named provider instruction plus a file value, the client sends the file by that route, and then references it from createDocuments or updateDocument.
Beyond the built-ins you can define your own tools, prompts and resources with full TypeScript inference through defineTool, defineCollectionTool, defineGlobalTool and definePrompt, observe or rewrite any completed response with the hooks.afterToolCall hook, and replace the authentication strategy entirely via overrideGetAuthorizedMCP. MIT-licensed and fully open-source.
Covered in the Weekly
by Strapi
Built into Strapi 5.47+, this MCP server turns your own content types into agent-callable tools — CRUD, publish and draft control, scoped by Admin token permissions.
Official AntV MCP server that turns a description of your data into a rendered chart — 26 visualization types from bar and line to sankey, mind-map, fishbone and geographic maps.
by Trigger.dev
Trigger.dev's official MCP server — trigger and monitor background jobs, deploy to any environment, and query runs with TRQL from your coding agent.
by Hugging Face
Hugging Face's official MCP server — search the Hub's models, datasets and Spaces, read repository files, and call thousands of Gradio applications as tools from one remote endpoint.