Payload MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Log level for the server (error, warn, info, http, verbose, debug, silly). Default is info. |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
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 43 tools
All tools are named with 'create' prefix and lack descriptions, making it impossible to distinguish between similar concepts like field types (createTextField vs createArrayField) and hooks (createAfterChangeHook vs createBeforeChangeHook). This leads to high ambiguity and likely misselection by agents.
All tools follow a consistent 'create_xxx' pattern (verb_noun), with 'create' as the sole verb. This uniformity makes the naming predictable despite the lack of descriptions.
43 tools is excessive for a server focused solely on creation operations. Many tools cover highly specific field types and hooks that could be consolidated, resulting in an overly large and unwieldy tool surface for the apparent scope.
The tool set exclusively supports creation operations, with no tools for reading, updating, deleting, or listing entities. This represents a severe gap in lifecycle coverage, making the server incomplete for typical CMS workflows.