create_content_type
Creates a new content type with the specified schema, options, field rules, and taxonomies.
LABSCO SUMMARY
Writing an entry and putting it live are different calls here, which is what makes this usable for real editorial work rather than only for seeding data.
update_entry can revise a live entry without shipping the change, and unpublish_entry pulls a page out of an environment and locale without deleting anything behind it. The depth sits on the read side: get_entries carries the filtering, ordering, field-trimming and include flags of the underlying query surface, so a narrow read stays narrow instead of returning a whole content type. The thin spot is global fields — create_global_field and update_global_field exist and get_all_global_fields lists them, but there is no single-field read and no delete, so a global field, once created, can only be revised.
What it is
A Contentstack management client covering the content model, the entries written against it, the global fields shared between them, and publishing as a separate act.
What you get
- Content types across their full lifecycle: create_content_type takes title, uid, schema, options, field_rules and taxonomies; update_content_type revises title, schema, options and field_rules on an existing uid; delete_content_type removes it.
- Model reads at either grain: get_content_type returns a single type by uid and can pull in the global field schema, while get_all_content_types pages with limit and skip and can include branch info, counts and referenced content type uids.
- Entries addressed by content type: create_entry writes a new entry under a content_type_uid, update_entry revises it by entry_uid, and delete_entry removes it.
- Entry reads with the query surface exposed rather than flattened: get_entry takes a locale and can pull referenced entries, and get_entries filters through query, orders with asc or desc, trims the payload with only and except, pages with limit and skip, and can include count, schema, metadata, owner and publish details.
- Publishing as its own call: publish_entry pushes an entry to a named environment and locale, and unpublish_entry withdraws it from that same pair.
- Global fields shared across types: create_global_field and update_global_field take title, uid and schema, and get_all_global_fields pages through them with branch info and counts.
Requirements
A Contentstack account and the credentials issued for it, supplied as CONTENTSTACK_API_KEY and CONTENTSTACK_MANAGEMENT_TOKEN.
Setup effort
One command plus a key — npx @drossman/contentstack-mcp, then supply credentials
USE CASES
01
Shaping a content type before anything is written against it
Define the content type and the global fields it reuses, then adjust the shape while it is still cheap to change.
02
Writing entries and putting one live
Create entries against a type, read back what is there, and publish a specific entry to a named environment and locale rather than everything at once.
03
Pulling something back
Take an entry off an environment without deleting it, or remove it outright once you are sure.
15 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
create_entry
Creates a new entry for a specified content type.
create_global_field
Creates a new global field with the specified title, UID, and schema.
delete_content_type
Deletes a content type identified by its UID.
delete_entry
Deletes an entry identified by its UID and content type UID.
get_all_content_types
Retrieves a list of all content types, with options for pagination and including additional details like global field schema and counts.
get_all_global_fields
Retrieves a list of all global fields, with options for pagination and including branch information.
get_content_type
Retrieves a specific content type by its UID, optionally including the global field schema.
get_entries
Retrieves entries for a specified content type, with extensive options for filtering, sorting, pagination, and including related data.
get_entry
Retrieves a specific entry by its content type UID and entry UID, with options for locale and including references.
publish_entry
Publishes an entry to a specified environment and locale.
unpublish_entry
Unpublishes an entry from a specified environment and locale.
update_content_type
Updates an existing content type identified by its UID. Allows modification of title, schema, options, and field rules.
update_entry
Updates an existing entry identified by its UID and content type UID.
update_global_field
Updates an existing global field identified by its UID. Allows modification of title and schema.
BEFORE YOU INSTALL
What to know first
Tools you get
15 tools when we connected. They include publish_entry, which puts content live in an environment. The five items under Available Resources are resources, not tools, and direct asset manipulation and bulk operations are not built yet.
Requires
- npx on PATH
- Node.js
- CONTENTSTACK_API_KEY in your environment
- CONTENTSTACK_MANAGEMENT_TOKEN in your environment
Where it runs
Both documented clients run the server on your machine.
CONTEXT COST
Moderate Standing cost
Rated by the size of the 15 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx @drossman/contentstack-mcpMCP Clients
Claude Desktop, Cursor
JSON
{
"mcpServers": {
"contentstack": {
"command": "npx",
"args": [
"-y",
"@drossman/contentstack-mcp"
],
"env": {
"CONTENTSTACK_API_KEY": "<YOUR_CONTENTSTACK_API_KEY>",
"CONTENTSTACK_MANAGEMENT_TOKEN": "<YOUR_CONTENTSTACK_MANAGEMENT_TOKEN>"
}
}
}
}
