contentstack-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONTENTSTACK_BRANCH | No | Specify branch if using branches | |
| CONTENTSTACK_API_KEY | Yes | Stack API key for authentication | |
| CONTENTSTACK_MANAGEMENT_TOKEN | Yes | Stack-level token with predefined permissions |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_content_typeC | Creates a new content type with the specified schema, options, field rules, and taxonomies. |
| update_content_typeC | Updates an existing content type identified by its UID. Allows modification of title, schema, options, and field rules. |
| delete_content_typeC | Deletes a content type identified by its UID. |
| create_entryC | Creates a new entry for a specified content type. |
| update_entryC | Updates an existing entry identified by its UID and content type UID. |
| delete_entryC | Deletes an entry identified by its UID and content type UID. |
| get_content_typeB | Retrieves a specific content type by its UID, optionally including the global field schema. |
| get_all_content_typesC | Retrieves a list of all content types, with options for pagination and including additional details like global field schema and counts. |
| get_entryA | Retrieves a specific entry by its content type UID and entry UID, with options for locale and including references. |
| get_entriesC | Retrieves entries for a specified content type, with extensive options for filtering, sorting, pagination, and including related data. |
| publish_entryC | Publishes an entry to a specified environment and locale. |
| unpublish_entryC | Unpublishes an entry from a specified environment and locale. |
| create_global_fieldC | Creates a new global field with the specified title, UID, and schema. |
| update_global_fieldB | Updates an existing global field identified by its UID. Allows modification of title and schema. |
| get_all_global_fieldsC | Retrieves a list of all global fields, with options for pagination and including branch information. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| create_content_workflow | Initiates a guided workflow for creating new content for a specified content type. |
| content_analysis | Initiates an analysis of content within a specified content type, providing insights and patterns. |
| migration_planning | Initiates a planning process for migrating content to Contentstack, guiding through key considerations. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| content-types | Retrieves a list of all content types in the stack. |
| assets | Retrieves a list of all assets in the stack. |
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.