BOIM WordPress Stack MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| format_wpcodebox_snippetB | Format a code snippet for WPCodebox plugin with proper structure and metadata |
| get_wpcodebox_guidelinesB | Get WPCodebox usage guidelines and best practices |
| validate_wpcodebox_snippetC | Validate a snippet structure against WPCodebox requirements |
| generate_gutenberg_blockB | Generate complete Gutenberg block code including block.json, PHP registration, and React components |
| generate_block_variationC | Generate a Gutenberg block variation |
| generate_block_patternC | Generate a Gutenberg block pattern |
| get_gutenberg_standardsB | Get Gutenberg block development standards and best practices |
| generate_gb_blockC | Generate GenerateBlocks-compatible block code |
| generate_gb_stylesC | Generate GenerateBlocks-specific SCSS (compile to CSS for production) |
| generate_gb_templateC | Generate GenerateBlocks template code |
| get_generateblocks_guideB | Get GenerateBlocks development guide and best practices |
| generate_php_functionC | Generate WordPress PHP function following coding standards |
| generate_hookC | Generate WordPress action or filter hook code |
| generate_shortcodeC | Generate WordPress shortcode implementation |
| generate_rest_endpointC | Generate WordPress REST API endpoint |
| format_for_wpcodeboxB | Format any generated code for WPCodebox snippet structure |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| WordPress Coding Standards | WordPress coding standards reference for PHP, JavaScript, and CSS |
| Gutenberg Block Development Patterns | Common Gutenberg block development patterns and examples |
| GenerateBlocks Development Guide | Best practices for GenerateBlocks plugin development |
| WPCodebox Snippet Format | WPCodebox snippet format specifications and structure |
| GeneratePress Theme Guide | GeneratePress theme-specific development guidelines |
TDQS
Scored across 16 tools
Most tools have distinct purposes targeting different WordPress development tasks (e.g., block generation, hooks, REST endpoints), but there is some overlap between 'format_for_wpcodebox' and 'format_wpcodebox_snippet' which could cause confusion as both handle WPCodebox formatting. The 'generate_gb_block' and 'generate_gutenberg_block' tools are clearly separated by targeting different block systems (GenerateBlocks vs core Gutenberg).
Tool names follow a highly consistent verb_noun pattern throughout, with all tools using 'generate_', 'get_', 'format_', or 'validate_' prefixes followed by specific nouns (e.g., 'generate_block_pattern', 'get_gutenberg_standards'). There are no deviations in naming conventions, making the set predictable and easy to navigate.
With 16 tools, the count is slightly high but reasonable for the WordPress development scope, covering multiple frameworks (Gutenberg, GenerateBlocks, WPCodebox) and code types (blocks, hooks, functions, endpoints). It might feel a bit heavy, but each tool appears to serve a specific niche in this specialized domain without obvious redundancy beyond the WPCodebox formatting overlap.
The toolset provides comprehensive coverage for WordPress development tasks, including code generation for blocks, hooks, functions, REST endpoints, and shortcodes, plus formatting/validation for WPCodebox and guides for best practices. There are no apparent gaps; agents can handle full workflows from creation to validation across supported frameworks.