Clearon WordPress MCP
Provides controlled publishing and content management for WordPress sites through the WordPress REST API, including reading and finding posts, creating and updating posts from reviewed payloads, uploading media, scheduling, publishing, and resolving duplicate posts with verification and rollback safeguards.
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., "@Clearon WordPress MCP Dry-run the WordPress payload at ./drafts/my-post.json before publishing."
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.
Clearon WordPress MCP
Local MCP server for controlled Clearon WordPress publishing through the WordPress REST API.
Safety model
Read tools may run directly.
Run
upsert_post_from_payloadindry_runmode before every write.Dry runs surface pending source-integrity review items from
payload.source_auditand warn when the live source-audit report is missing, mismatched, or still blocked; real writes requiresource_audit, re-hash the payload content, and re-check the live source-audit report before writing.Contradictory source-audit states are rejected. A payload or live report cannot be both
ready_for_publish_or_update: trueand still blocked by pending findings orpublish_update_gate.blocked. Approved reports may still retainpublish_update_review_required_findingsas historical evidence.Only an exact slug, a valid
wordpress_post_id, or anexplicit_target_idcan authorize an update, and stored or explicit IDs are rejected when exact-slug evidence points to a different post. Title and near-slug matches produce a conflict for human review.Publishing and scheduling require a featured image. Local media is uploaded and attached before the final public post update.
New posts are created as drafts and promoted only after prerequisites succeed. Existing live posts are not modified until the final combined update.
publish_nowrefuses already-published targets so it cannot silently reset publication dates on a live post.After the final write, the server re-fetches the post and verifies its slug, canonical link, status, featured image, share block, supplied publication date, and featured-image social metadata.
On a later failure, newly created drafts are trashed, newly uploaded media is deleted, and a modified existing post is restored from its pre-write snapshot when verification proves the result is wrong.
Payload and image paths must resolve inside the configured workspace root. Set
CLEARON_WP_MCP_WORKSPACEwhen the process is not already started from that workspace; symlinks cannot escape the resolved root.Image uploads accept JPG, PNG, WebP, and GIF files up to 20 MB and verify the file signature.
Writes are serialized within one MCP process by the payload slug plus any supplied post IDs so slug-based and ID-based writes against the same post do not race. This does not coordinate multiple independently running server processes.
Duplicate cleanup verifies numeric WordPress slug suffixes. Permanent deletion requires
confirm_permanent_delete: true.
Related MCP server: WordPress MCP Server
Tools
Read-only:
get_server_healthget_auth_modeget_endpoint_configget_postfind_postsaudit_slug_state
Writes:
upsert_post_from_payloadupload_mediapublish_nowresolve_duplicate_posts
publish_now is no longer a bare post-ID publish shortcut. It requires both post_id and payload_path, re-runs reviewed payload targeting, proves that the existing target already matches the reviewed payload content, re-checks the live source-audit gate, then publishes with the same verification and rollback path used by upsert_post_from_payload. When publish_at_local is omitted, the server stamps the current local time in WordPress YYYY-MM-DDTHH:mm:ss format.
The legacy direct mutation tools set_featured_image, upsert_share_block, and set_social_meta remain present only as disabled compatibility stubs. They return an error directing callers back to the reviewed payload workflow.
resolve_duplicate_posts supports:
trash: move a duplicate to WordPress trash; recoverabledraft: retain it as a draftprivate: retain it privatelydelete: permanently delete it; requiresconfirm_permanent_delete: true
Payload requirements
Payloads require non-empty title, slug, and content. Slugs must use lowercase letters, numbers, and hyphens. categories and tags, when supplied, must contain positive integer IDs.
Payload dry runs may proceed while source_audit.pending_publish_update_review_findings is non-empty, but non-dry-run writes require source_audit with a revision fingerprint that exactly matches the approved editorial revision when editorial_approval.sha256 is present, otherwise the current payload content fingerprint. They are blocked unless the latest live source-audit report for that slug also matches that same fingerprint, matches the payload title, is ready_for_human_approval, and is ready_for_publish_or_update.
Schedule mode requires a valid future date. Publish and schedule modes require one of:
featured_medialocal_featured_imagean existing featured image on the exact update target
Run and test
cd tools/clearon-wordpress-mcp
npm run syntax
npm test
node server.mjsSafe live smoke test:
CLEARON_WP_MCP_WORKSPACE=/absolute/path/to/workspace \
npm run smoke -- /absolute/path/to/workspace/path/to/payload.jsonThe smoke test initializes the MCP, checks health, and performs only a payload dry run.
Recommended workflow
Call
get_server_healthand confirmauth_modeis notmissing.Call
upsert_post_from_payloadwithmode: "dry_run". If the payload is still markeddraftbut you want dry-run checks for an eventual publish or schedule operation, passintended_mode.Resolve every conflict or warning, including any listed pending source-integrity approvals. Use
explicit_target_idonly after checking the candidate manually.Publish as a draft first for editorial review when practical.
Use
publish,draft, orscheduleonly when the dry run identifies the intended target and image and the live source-audit gate is clear.Use
publish_nowonly for an already prepared exact target post and pass the same reviewed payload path used for the dry run.Review the returned
verificationresult, then callaudit_slug_stateas an independent live-state check.
Authentication
The server checks:
WP_AUTHWP_USERplusWP_APP_PASSWORDclearonWordPress.wpAuthinOPENCLAW_LOCAL_SECRETSor~/.openclaw/secrets/local.json
Credentials are sent only in the WordPress REST authorization header and are not returned by MCP tools or written to logs.
Failure and recovery
A failed local image validation performs no WordPress write.
A failed upload performs no post write.
Cleanup after a failed later step is best-effort: newly uploaded media is deleted, new drafts are trashed, and verified mismatches on existing posts trigger rollback plus a rollback verification read.
If WordPress accepts the final write but all three verification reads fail, the server does not guess or roll back an unknown state. It reports that a manual
audit_slug_stateis required before retrying.If the final write response is lost or times out, the server treats WordPress state as unknown, skips cleanup assumptions, and requires
audit_slug_statebefore retrying.JSON logs go to
stderr. SetCLEARON_WP_MCP_LOG_LEVEL=infoordebugfor troubleshooting.
The server does not modify payload JSON files. WordPress state remains the source of truth and should be verified through audit_slug_state or your own live-state audit path.
Available Tools
13 toolsaudit_slug_stateB
Audit the live state of a slug and expose duplicate candidates.
Inputs: slug (required).
find_postsB
Find WordPress posts by slug or title and optionally filter by status.
Inputs: slug, title, status, context.
get_auth_modeA
Report which WordPress auth source the server will use.
Inputs: no named parameters.
get_endpoint_configA
Report the target WordPress base URL and REST endpoint configuration.
Inputs: no named parameters.
get_postB
Fetch a WordPress post by id or slug.
Inputs: id, slug, context.
get_server_healthB
Report local server health, auth mode, and endpoint basics.
Inputs: no named parameters.
publish_nowB
Publish an existing prepared post immediately from a reviewed payload, with the same safety gates and verification used by payload upserts.
Inputs: post_id (required), payload_path (required), publish_at_local.
resolve_duplicate_postsB
Explicitly clean up duplicate posts by trashing, deleting, or downgrading them.
Inputs: duplicate_action (required), canonical_post_id (required), duplicate_post_ids (required), confirm_permanent_delete.
set_featured_imageB
Disabled direct mutation tool. Use a reviewed payload workflow instead.
Inputs: post_id (required), media_id (required).
set_social_metaB
Disabled direct mutation tool. Use a reviewed payload workflow instead.
Inputs: post_id (required), og_image_type, twitter_use_og, twitter_image_type.
upload_mediaC
Upload a local asset to WordPress media library.
Inputs: path (required), post_id, alt_text, filename.
upsert_post_from_payloadC
Create or update a Clearon WordPress post from an existing payload JSON file.
Inputs: payload_path (required), mode, intended_mode, explicit_target_id.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 13 tools
Most tools map to distinct actions, but get_server_health overlaps with get_auth_mode and get_endpoint_config, and get_post/find_posts have similar retrieval purposes. The three disabled tools set_social_meta, set_featured_image, and upsert_share_block share nearly identical 'use a reviewed payload workflow' descriptions, which adds ambiguity.
The set mostly follows a verb_noun snake_case pattern like get_post, upload_media, audit_slug_state, and resolve_duplicate_posts. Minor deviations such as publish_now and the mix of set_/upsert_ for disabled mutation tools keep it from being fully consistent.
13 tools is a reasonable size for a WordPress publishing server. However, three of those tools are disabled stubs that add clutter rather than functionality, so the effective tool surface is closer to 10.
The active tools cover post retrieval, payload-based upsert/publish, media upload, and duplicate management. Notable gaps remain: no direct way to set featured images or social meta, no general media retrieval, and no delete/update flow outside the payload workflow.
Maintenance
Related MCP Connectors
WordPress plugin exposing 60 MCP tools via OAuth 2.1: posts, pages, media, users, comments and SEO.
Manage WordPress blogs and WooCommerce shops from Claude, ChatGPT, Cursor and other MCP apps.
Publish to self-hosted WordPress from AI agents: markdown, images, SEO, and Notion sync.
Manage social publishing workflows through OpenPost
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables management of WordPress posts and pages including creating, updating, deleting, duplicating, scheduling, and bulk editing content through the WordPress REST API.MIT
- AlicenseNot gradedqualityBmaintenanceEnables interaction with WordPress sites through the WordPress REST API via natural language, supporting single and multi-site management, content and taxonomy operations, media uploads, and more.173 npm100GPL 3.0
- AlicenseAqualityBmaintenanceEnables comprehensive management of WordPress sites including posts, users, media, categories, tags, and site settings via the WordPress REST API.201Apache 2.0
- AlicenseBqualityBmaintenanceEnables reading and managing WordPress sites via the WP REST API, including posts, pages, media, taxonomies, users, and arbitrary REST endpoints, with optional authenticated write operations.1714 npm1MIT