Can AI agents automate Strapi?

Strapi is automatable today through its Content API. Strapi 5 generates REST endpoints that list, create, update, and delete documents for each content type. The GraphQL plugin, once installed, exposes queries and mutations at /graphql and does not upload media. Content API requests authenticate with an API token sent as Authorization bearer, or with a Users & Permissions JWT sent as Authorization Bearer. API tokens are separate from Admin tokens. The official @strapi/client package is a JavaScript and TypeScript client for collections, single types, and files. Strapi 5.47.0 or later includes an MCP server at /mcp. It stays off until config/server sets mcp.enabled to true. Clients send a Strapi Admin token as a bearer token, and that token's permissions decide which content and media tools appear. Content tools can create, read, update, delete, publish, and unpublish entries. Media tools from 5.54.0 can list and change assets, and they cannot upload a new file. The strapi CLI can develop and start a project, manage admin users, and export, import, or transfer data. Export writes an encrypted tar archive by default, or an unencrypted directory. Webhooks can POST entry and media events. The Community Edition is MIT Expat when ee/ is not used and there is no Strapi Cloud account. Enterprise Edition code under ee/ is not MIT. Strapi Cloud and Enterprise are paid offerings on the product site. https://docs.strapi.io/llms.txt is a first-party documentation index. Zapier, Make, Power Automate, and n8n were not assessed. Computer-use viability is unassessed. API scores 8. MCP scores 7. CLI scores 6. API is the best path because a content API token calls generated REST endpoints directly, including file upload, without enabling the MCP server.

Best path today: api · Overall automatability: 8/10