Summary
The CMS stops being the place you click through to change one field.
Content modelling is what separates this from a plain API wrapper — you can add a content type and start writing entries into it inside the same conversation, which is the part that usually requires the admin panel. That reach is also the caution, since the same credentials that create an entry can delete a content type.
What it is
A server over Strapi's content and admin APIs with 20 tools spanning entries, relations, media, publishing, content types and components.
What you get
- Entries listed with filtering, pagination, sorting and relation population, then fetched, created, updated and deleted individually
- A content type's schema — its fields, types and relations — before anything is written against it
- Related entries connected to and disconnected from a relation field by id
- Publishing and unpublishing as explicit calls, separate from creating and editing
- Media uploaded inline up to roughly 750KB of file (1MB base64), or from a local path up to 10MB
- Content types created, updated and deleted, and components created, updated and read by schema
Requirements
STRAPI_URL, STRAPI_ADMIN_EMAIL and STRAPI_ADMIN_PASSWORD; creating, updating or deleting a content type additionally needs admin privileges on that account.
Setup effort
One command plus a key — npm install strapi-mcp, then supply credentials