Contentful MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONTENTFUL_SPACE_ID | Yes | Your Contentful space ID | |
| CONTENTFUL_ENVIRONMENT | No | Your Contentful environment | develop |
| CONTENTFUL_ACCESS_TOKEN | Yes | Your Contentful access token | |
| CONTENTFUL_PREVIEW_ACCESS_TOKEN | No | Your Contentful preview access token |
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 |
|---|---|
| get-content-typesC | get content types |
| get-entriesC | Get entries for a specific content type |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: get-content-types retrieves metadata about content types, while get-entries fetches actual content entries for a specific type. There is no overlap or ambiguity between these operations.
Both tools follow a consistent verb_noun naming pattern with hyphens (get-content-types and get-entries). The naming is predictable and uniform across the set.
With only 2 tools, the server feels severely under-scoped for a Contentful MCP server, which typically involves content management operations like creating, updating, or deleting entries and content types. This minimal set limits functionality.
The toolset is significantly incomplete for a content management domain. It only provides read operations (get-content-types and get-entries), missing essential CRUD operations such as create, update, or delete for entries and content types, which are core to content management workflows.