A
licenseNot graded
qualityD
maintenanceEnables AI assistants to connect to Strapi CMS for browsing, creating, editing, publishing, and managing content through natural language.
9 npm
MIT
strapi-mcp
Related Servers
Alternatives to strapi-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with Strapi CMS instances through REST API operations. Supports content management, media uploads, schema introspection, and multiple server configurations with JWT authentication.9 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides access to Strapi CMS content through the MCP protocol, allowing users to create, read, update, and delete content entries via Claude.1,425 npm25MIT
- AlicenseAqualityBmaintenanceA Model Context Protocol server that enables AI assistants to interact with Strapi CMS instances through a standardized interface, supporting content types and REST API operations.5235 npm75MIT
- AlicenseAqualityDmaintenanceMCP server for Strapi CMS content and media management.157 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact directly with Strapi v5 CMS content through full CRUD operations, media uploads, and content type exploration using Strapi's Document Service API.286 npm1MIT
TDQS
A4.4/5.0
Scored across 20 tools
Disambiguation5/5
Every tool targets a distinct aspect of Strapi CMS: content entries, media, locales, schemas, bulk operations, etc. No two tools have overlapping purposes; even similar ones like get_entry and get_localized_entry are clearly differentiated by locale.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern using lowercase snake_case (e.g., create_entry, delete_media, list_content_types). This predictability makes it easy for an agent to infer functionality from names.
Tool Count5/5
With 20 tools, the server covers the full spectrum of Strapi operations—CRUD, media management, localization, schema inspection, bulk actions—without being overly numerous or sparse. Each tool serves a clear purpose.
Completeness5/5
The tool surface is comprehensive: full lifecycle for entries (create, read, update, delete, publish, unpublish, draft discard), media (upload, list, delete), locale support, schema discovery, and even bulk operations. No obvious gaps for typical CMS workflows.
Maintenance
ActivityInactive
ResponsivenessNo issues