WordPress MCP Custom Server
Provides tools for managing WordPress content (listing, publishing, updating posts/pages), site requests and options, SEO meta via Yoast, file operations on the project, W3C validation, playbooks, checklists, and A/B benchmarking.
Provides tools for setting SEO meta fields (seo.set_meta.v1) on WordPress content through the WordPress site integration.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@WordPress MCP Custom Server validate and fix W3C errors on my homepage"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
WordPress MCP Custom Server
WordPress MCP server with:
capability-based versioned tools (
*.v1)backward-compatible aliases (old tool names still work)
unified error contract
request-level observability (
requestId, duration, status)retry/timeout HTTP client for WP + W3C requests
text playbooks/checklists for repeatable execution
A/B benchmark report generator (
benchmark-summary.md)write-safety policy for generic REST writes (allowlist + approval + dry-run)
Installation
cd /Users/yanka/dev/wp-mcp-custom
npm installRelated MCP server: TanukiMCP
Required env
WP_URLWP_USERWP_APP_PASS
Optional:
WP_PROJECT_ROOTfor file toolsPROJECT_PROFILE_PATHfor custom profile location
Project profile
Create project.profile.json in server working directory (or use PROJECT_PROFILE_PATH):
{
"projectType": "wordpress",
"capabilities": ["seo", "content", "site", "validation", "files"],
"limits": {
"listFilesDefault": 200,
"listFilesMax": 2000,
"autofixDefaultMaxFiles": 500,
"autofixMaxFiles": 5000
},
"autofix": {
"defaultPaths": [
"wp-content/themes",
"wp-content/mu-plugins"
]
},
"http": {
"timeoutMs": 15000,
"retries": 2,
"retryDelayMs": 250,
"maxRetryDelayMs": 2000
},
"safety": {
"enabled": true,
"writeMethods": ["POST", "PUT", "DELETE"],
"allowedWritePathPrefixes": [
"/wp/v2/posts",
"/wp/v2/pages",
"/custom/v1/update-option",
"/custom/v1/update-yoast"
],
"requireApprovalPathPrefixes": [
"/wp/v2/settings",
"/wp/v2/users",
"/wp/v2/themes",
"/wp/v2/plugins"
]
}
}Tool naming
Canonical versioned tools:
content.list.v1content.publish.v1content.update_fields.v1site.request.v1site.update_option.v1seo.set_meta.v1project.files.list.v1project.files.read.v1project.files.write.v1validation.w3c.validate_urls_raw.v1validation.w3c.validate_pages.v1validation.w3c.validate_and_recheck.v1validation.w3c.autofix_safe.v1playbook.list.v1playbook.read.v1checklist.seo_landing_audit.v1checklist.w3c_validate_and_fix_plan.v1checklist.multilang_publish.v1benchmark.compare_ab.v1
Backward-compatible aliases still supported:
list_posts,create_post_multilang,update_acf_fieldswp_request,update_option,update_yoastlist_project_files,read_project_file,write_project_filew3c_validate_live_urls_raw,w3c_validate_pages,w3c_validate_and_recheck,w3c_autofix_safe
Playbooks
Stored in /Users/yanka/dev/wp-mcp-custom/playbooks:
seo-landing-checklist-v1.mdw3c-fix-checklist-v1.mdmultilang-publish-v1.md
Use:
playbook.list.v1playbook.read.v1
Safety behavior for site.request.v1
GETrequests are allowed.Write methods are checked against
safety.allowedWritePathPrefixes.Paths in
safety.requireApprovalPathPrefixesrequirerequire_approval=true.dry_run=truereturns preview without sending request.
Benchmark demo report
Use benchmark.compare_ab.v1 with:
runs_prompt_onlyruns_mcpoptional
output_path
Output:
aggregate metrics
per-case comparisons
generated markdown report (
mcp-benchmarks/benchmark-summary.mdby default)
Unified error contract
Every tool error returns:
{
"code": "INVALID_ARGUMENT",
"message": "...",
"details": {},
"retryable": false,
"requestId": "..."
}Tests
npm testNotes
Logs go to stderr as JSON (
tool.start,tool.success,tool.error,server.started).Tool schemas use stricter JSON Schema (
additionalProperties: false) for stable contracts.
Available Tools
32 toolsbenchmark.compare_ab.v1A
Compare prompt-only vs MCP runs and write benchmark-summary.md for developer demos.
Inputs: runs_mcp (required), runs_prompt_only (required), output_path, write_report, +1 more. Returns: object
checklist.multilang_publish.v1C
Run multilingual publish checklist with dry-run and optional post-publish checks.
Inputs: translations (required), status, dry_run, post_publish_checks. Returns: object
checklist.seo_landing_audit.v1B
Run a standard SEO landing QA checklist for one URL.
Inputs: url (required), level, include_messages. Returns: object
checklist.w3c_validate_and_fix_plan.v1C
Run W3C validation and build a fix plan for typical landing/template issues.
Inputs: urls (required), level, paths, max_files, +1 more. Returns: object
content.list.v1C
List WordPress posts with optional Polylang language filter.
Inputs: lang, status, per_page. Returns: object
content.publish.v1C
Create multilingual WordPress post variants via Polylang.
Inputs: translations (required), status. Returns: object
content.update_fields.v1C
Update ACF fields for a WordPress post/page.
Inputs: fields (required), post_id (required). Returns: object
create_post_multilangC
DEPRECATED alias for content.publish.v1.
Inputs: translations (required), status. Returns: object
list_postsC
DEPRECATED alias for content.list.v1.
Inputs: lang, status, per_page. Returns: object
list_project_filesC
DEPRECATED alias for project.files.list.v1.
Inputs: path, limit. Returns: object
playbook.list.v1B
List text playbooks/checklists for MCP-guided SEO workflows.
Inputs: no named parameters. Returns: object
playbook.read.v1C
Read a playbook/checklist text file by playbook_id.
Inputs: playbook_id (required). Returns: object
project.files.list.v1C
List files inside WP_PROJECT_ROOT recursively.
Inputs: path, limit. Returns: object
project.files.read.v1C
Read text file from WP_PROJECT_ROOT.
Inputs: path (required). Returns: object
project.files.write.v1C
Write text file to WP_PROJECT_ROOT.
Inputs: path (required), content (required). Returns: object
read_project_fileB
DEPRECATED alias for project.files.read.v1.
Inputs: path (required). Returns: object
seo.set_meta.v1C
Update Yoast SEO title and/or meta description via custom endpoint.
Inputs: post_id (required), title, description. Returns: object
site.request.v1C
Universal WP REST request to /wp-json path with write safety guards.
Inputs: path (required), method (required), body, dry_run, +1 more. Returns: object
site.update_option.v1B
Update wp_options via custom endpoint. Allowed keys: blog_public, blogdescription, blogname.
Inputs: key (required), value (required). Returns: object
update_acf_fieldsA
DEPRECATED alias for content.update_fields.v1.
Inputs: fields (required), post_id (required). Returns: object
update_optionC
DEPRECATED alias for site.update_option.v1.
Inputs: key (required), value (required). Returns: object
update_yoastC
DEPRECATED alias for seo.set_meta.v1.
Inputs: post_id (required), title, description. Returns: object
validation.w3c.autofix_safe.v1C
Run safe file autofix and W3C before/after validation on raw HTML pages.
Inputs: after_pages (required), baseline_pages (required), level, paths, +1 more. Returns: object
validation.w3c.validate_and_recheck.v1C
Run baseline and after validation for provided raw HTML pages.
Inputs: after_pages (required), baseline_pages (required), level. Returns: object
validation.w3c.validate_pages.v1C
Validate provided raw HTML pages through W3C Nu Validator.
Inputs: pages (required), level. Returns: object
validation.w3c.validate_urls_raw.v1C
Validate live URLs through W3C Nu Validator using fetched raw HTML.
Inputs: urls (required), level. Returns: object
w3c_autofix_safeD
DEPRECATED alias for validation.w3c.autofix_safe.v1.
Inputs: after_pages (required), baseline_pages (required), level, paths, +1 more. Returns: object
w3c_validate_and_recheckD
DEPRECATED alias for validation.w3c.validate_and_recheck.v1.
Inputs: after_pages (required), baseline_pages (required), level. Returns: object
w3c_validate_live_urls_rawC
DEPRECATED alias for validation.w3c.validate_urls_raw.v1.
Inputs: urls (required), level. Returns: object
w3c_validate_pagesC
DEPRECATED alias for validation.w3c.validate_pages.v1.
Inputs: pages (required), level. Returns: object
wp_requestD
DEPRECATED alias for site.request.v1.
Inputs: path (required), method (required), body, dry_run, +1 more. Returns: object
write_project_fileA
DEPRECATED alias for project.files.write.v1.
Inputs: path (required), content (required). Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
WordPress MCP server: publish posts, AI images, SEO and full site management, self-hosted
Security-first WordPress MCP server. 129 tools for Claude, ChatGPT, Gemini. Free on wp.org.
WordPress plugin exposing 60 MCP tools via OAuth 2.1: posts, pages, media, users, comments and SEO.
WordFlux MCP server to publish and schedule content across social platforms and CMS systems.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA comprehensive MCP server for managing WordPress sites through the REST API, featuring 38 tools for content, media, plugin, and theme management. It supports secure Application Password authentication and offers specific compatibility for Divi theme shortcode structures.MIT
- AlicenseNot gradedqualityDmaintenanceA comprehensive MCP server for WordPress automation that enables users to manage content, themes, and site configurations using AI-driven workflows and the WordPress REST API. It provides a wide array of tools for site planning, management, and optimization compatible with tools like Cursor and Claude.1MIT
- AlicenseNot gradedqualityDmaintenanceMCP server for WordPress content management that provides a secure interface for AI assistants to interact with WordPress sites, enabling content creation, editing, and media management without destructive operations.MIT
- AlicenseAqualityBmaintenanceMCP server for publishing to WordPress. 13 tools cover posts, categories, tags, image hosting, featured images, and SEO metadata (Rank Math, etc.) One call runs the full markdown-to-live-URL pipeline.134AGPL 3.0