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
AINative Strapi MCP Server
Related Servers
Alternatives to AINative Strapi MCP Server
No user-submitted related servers found.
Related Servers
- 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
- 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
- FlicenseNot gradedqualityNot gradedmaintenanceProvides AI agents with full access to Strapi 5.x CMS for managing content types, entries, media, and schemas. It supports full CRUD operations, relation management, and secure authentication for comprehensive content administration.-
- FlicenseNot gradedqualityNot gradedmaintenanceEnables comprehensive management of Storyblok CMS through natural language interactions. Supports story creation and publishing, asset management, component schema updates, release workflows, and content discovery across all major Storyblok APIs.8 npm-
- AlicenseAqualityDmaintenanceConnects any MCP-compatible AI assistant to Strapi CMS for content management, media handling, internationalization, and more through natural language.201MIT
TDQS
A3.5/5.0
Scored across 18 tools
Disambiguation5/5
Every tool has a clearly distinct purpose based on resource type (blog_post, event, tutorial, author, category, tag) and action (create, get, list, publish, update), with no overlapping functionality. The descriptions reinforce this separation, making tool selection unambiguous.
Naming Consistency5/5
All tools follow a strict and predictable pattern: 'strapi_' prefix, then verb (create, get, list, publish, update), then noun (e.g., blog_post, event, tutorial). This consistency is maintained across all 18 tools, making the set highly readable and systematic.
Tool Count4/5
With 18 tools, the count is slightly high but reasonable for a CMS server covering multiple content types (blog posts, events, tutorials) and supporting full CRUD operations plus listing and publishing. It feels comprehensive rather than bloated, though it could be streamlined by reducing redundancy in some list operations.
Completeness5/5
The tool set provides complete CRUD and lifecycle coverage for the core content types (blog posts, events, tutorials), including create, get, update, list, and publish/unpublish actions. It also includes auxiliary resources like authors, categories, and tags, leaving no obvious gaps for typical CMS workflows.
Maintenance
ActivitySlowing
ResponsivenessNo issues