contentstack-mcp
Related Servers
Alternatives to contentstack-mcp
- AlicenseCqualityDmaintenanceUpdate, create, delete content, content-models and assets in your Contentful Space4069 npm62MIT
Related Servers
- AlicenseAqualityDmaintenanceMCP server for Strapi CMS content and media management.159 npmMIT
- MIT
- FlicenseNot gradedqualityDmaintenanceA transport wrapper that exposes Contentstack MCP tools over HTTP instead of stdio to enable remote access and horizontal scaling. It acts as a proxy for the Contentstack MCP package, allowing browser-based and networked clients to interact with various Contentstack APIs.-

elmapicms-mcp-serverofficial
AlicenseBqualityBmaintenanceAn MCP server that connects AI agents like Cursor and Claude Code to your ElmapiCMS instance. Manage collections, fields, content entries, and assets programmatically through natural language.188 npm7MIT- AlicenseCqualityDmaintenanceA Storyblok MCP Server built on TypeScript with more than 130+ Actions1008MIT

Contentfulofficial
AlicenseNot gradedqualityAmaintenanceA Model Context Protocol (MCP) server that provides AI assistants with comprehensive tools to interact with Contentful APIs.139 npm61MIT
TDQS
Scored across 15 tools
Each tool has a clearly distinct purpose targeting specific resources (content types, entries, global fields) and actions (create, get, update, delete, publish/unpublish). There is no overlap or ambiguity; for example, get_all_content_types vs. get_content_type are clearly differentiated by scope.
All tools follow a consistent verb_noun pattern with underscores (e.g., create_content_type, get_entries, update_global_field). The naming is predictable and uniform across all 15 tools, making it easy for agents to understand and use them.
With 15 tools, this server is well-scoped for content management operations. Each tool earns its place by covering essential CRUD and lifecycle actions for content types, entries, and global fields, without being overly bloated or sparse.
The tool surface provides complete CRUD and lifecycle coverage for the content management domain. It includes create, get, update, and delete for all core resources (content types, entries, global fields), plus publishing/unpublishing for entries, with no obvious gaps that would hinder agent workflows.