WordPress MCP Custom Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WP_URL | Yes | WordPress site URL | |
| WP_USER | Yes | WordPress username | |
| WP_APP_PASS | Yes | WordPress application password | |
| WP_PROJECT_ROOT | No | Project root for file tools (optional) | |
| PROJECT_PROFILE_PATH | No | Custom profile location (optional) |
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
| Name | Description |
|---|---|
| content.list.v1C | List WordPress posts with optional Polylang language filter. |
| content.publish.v1C | Create multilingual WordPress post variants via Polylang. |
| content.update_fields.v1C | Update ACF fields for a WordPress post/page. |
| site.request.v1C | Universal WP REST request to /wp-json path with write safety guards. |
| site.update_option.v1B | Update wp_options via custom endpoint. Allowed keys: blog_public, blogdescription, blogname. |
| seo.set_meta.v1C | Update Yoast SEO title and/or meta description via custom endpoint. |
| project.files.list.v1C | List files inside WP_PROJECT_ROOT recursively. |
| project.files.read.v1C | Read text file from WP_PROJECT_ROOT. |
| project.files.write.v1C | Write text file to WP_PROJECT_ROOT. |
| validation.w3c.validate_urls_raw.v1C | Validate live URLs through W3C Nu Validator using fetched raw HTML. |
| validation.w3c.validate_pages.v1C | Validate provided raw HTML pages through W3C Nu Validator. |
| validation.w3c.validate_and_recheck.v1C | Run baseline and after validation for provided raw HTML pages. |
| validation.w3c.autofix_safe.v1C | Run safe file autofix and W3C before/after validation on raw HTML pages. |
| playbook.list.v1B | List text playbooks/checklists for MCP-guided SEO workflows. |
| playbook.read.v1C | Read a playbook/checklist text file by playbook_id. |
| checklist.seo_landing_audit.v1B | Run a standard SEO landing QA checklist for one URL. |
| checklist.w3c_validate_and_fix_plan.v1C | Run W3C validation and build a fix plan for typical landing/template issues. |
| checklist.multilang_publish.v1C | Run multilingual publish checklist with dry-run and optional post-publish checks. |
| benchmark.compare_ab.v1A | Compare prompt-only vs MCP runs and write benchmark-summary.md for developer demos. |
| list_postsC | DEPRECATED alias for content.list.v1. |
| create_post_multilangC | DEPRECATED alias for content.publish.v1. |
| update_acf_fieldsA | DEPRECATED alias for content.update_fields.v1. |
| wp_requestD | DEPRECATED alias for site.request.v1. |
| update_optionC | DEPRECATED alias for site.update_option.v1. |
| update_yoastC | DEPRECATED alias for seo.set_meta.v1. |
| list_project_filesC | DEPRECATED alias for project.files.list.v1. |
| read_project_fileB | DEPRECATED alias for project.files.read.v1. |
| write_project_fileA | DEPRECATED alias for project.files.write.v1. |
| w3c_validate_live_urls_rawC | DEPRECATED alias for validation.w3c.validate_urls_raw.v1. |
| w3c_validate_pagesC | DEPRECATED alias for validation.w3c.validate_pages.v1. |
| w3c_validate_and_recheckD | DEPRECATED alias for validation.w3c.validate_and_recheck.v1. |
| w3c_autofix_safeD | DEPRECATED alias for validation.w3c.autofix_safe.v1. |
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 32 tools
The tool set has 32 tools, but many are deprecated aliases for the same underlying operations. There are also overlapping validation tools (validate_urls_raw vs validate_pages vs validate_and_recheck vs autofix_safe) that are quite similar in purpose, and overlapping checklist tools. The deprecated aliases create significant ambiguity about which tool to use.
The set mixes namespace-dotted versioned names (content.list.v1, site.request.v1) with deprecated snake_case aliases (list_posts, wp_request). Even within the main names, there's inconsistent structure: some use domain.action form (content.publish.v1) while others use flat action form (read_project_file, benchmark.compare_ab.v1).
32 tools is excessive for what is genuinely a moderate-scope WordPress automation server. Critically, roughly half of the tools (13+) are deprecated aliases that should have been removed, meaning only about 19 are real and roughly half of those are legitimate. The deprecation burden inflates the count enormously.
The core surface covers content publishing, ACF updates, project file management, site options, SEO meta, W3C validation, playbooks, and benchmarks. However, there are notable gaps: no tool to update existing posts (only list and publish new), no get single post, and no delete. Content update appears limited to ACF fields rather than general post editing.