Clearon WordPress MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WP_AUTH | No | WordPress authentication credentials (e.g., 'username:application_password'). | |
| WP_USER | No | WordPress username used with WP_APP_PASSWORD. | |
| WP_APP_PASSWORD | No | WordPress application password used with WP_USER. | |
| OPENCLAW_LOCAL_SECRETS | No | Path to a local secrets JSON file containing clearonWordPress.wpAuth. If omitted, defaults to ~/.openclaw/secrets/local.json. | |
| CLEARON_WP_MCP_LOG_LEVEL | No | Log level for troubleshooting. Use 'info' or 'debug'. | info |
| CLEARON_WP_MCP_WORKSPACE | No | Absolute path to the workspace root. Payload and image paths must resolve inside this root. Set when the process is not already started from that workspace. |
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 |
|---|---|
| get_server_healthB | Report local server health, auth mode, and endpoint basics. |
| get_auth_modeA | Report which WordPress auth source the server will use. |
| get_endpoint_configA | Report the target WordPress base URL and REST endpoint configuration. |
| get_postB | Fetch a WordPress post by id or slug. |
| find_postsB | Find WordPress posts by slug or title and optionally filter by status. |
| upsert_post_from_payloadC | Create or update a Clearon WordPress post from an existing payload JSON file. |
| upload_mediaC | Upload a local asset to WordPress media library. |
| set_featured_imageB | Disabled direct mutation tool. Use a reviewed payload workflow instead. |
| upsert_share_blockC | Disabled direct mutation tool. Use a reviewed payload workflow instead. |
| set_social_metaB | Disabled direct mutation tool. Use a reviewed payload workflow instead. |
| publish_nowB | Publish an existing prepared post immediately from a reviewed payload, with the same safety gates and verification used by payload upserts. |
| audit_slug_stateB | Audit the live state of a slug and expose duplicate candidates. |
| resolve_duplicate_postsB | Explicitly clean up duplicate posts by trashing, deleting, or downgrading them. |
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 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.