GeneratePress and GenerateBlocks abilities for MCP. Manage theme settings, elements, global styles, page meta, and caches.
This PHP MCP server exposes 8 WordPress theme/block management tools with partial schema coverage. All tools have descriptions (10-120 chars, mostly adequate), and input schemas are present with typed parameters. However, schemas lack depth: most parameters have minimal descriptions (1-5 words), no enums for constrained values (e.g., block_type, status), and no documented output schemas. Error handling is absent, no recovery guidance, no validation messages. Naming is clear (verb_noun pattern: get_, update_, clear_, synchronize_, upsert_), but parameter descriptions are sparse.
Clear and optionally warm GenerateBlocks dynamic CSS cache for specified posts or globally
Return current GenerateBlocks Pro Global Styles in their native stored representation
Upsert supplied GenerateBlocks Global Styles and explicitly delete named selectors
Retrieve page meta values for a post by ID
Retrieve GeneratePress theme options
Update page meta values for a post
Update GeneratePress theme options
No output schemas documented. Tools return data but LLMs cannot predict field names, types, or structure. Downstream tool chaining is impossible without trial-and-error.
Parameter descriptions are minimal (1-5 words). E.g., 'Array of post IDs to clear cache for (null for global)' lacks format guidance, valid ranges, or examples. LLMs cannot validate inputs.
No enums for constrained parameters. 'block_type' accepts 11 values (hook, content-template, etc.) but is defined as free-form string. 'status' accepts 'publish' or 'draft' but no enum. LLMs will hallucinate invalid values.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 61 | 2026-07-28+ | v2 |
Idempotently persist one native GeneratePress Block Element with display conditions
No error handling or recovery guidance. Destructive operations (clear-cache, synchronize-global-styles, update-*) lack confirmation steps or dry-run modes. Agents cannot safely retry on failure.
STDIO transport only. Server is not remotely accessible and cannot be used by hosted MCP clients. Requires local process spawning.