ClawHub

Maverick Wordpress Mcp

Read and write WordPress.com site content through WordPress.com's hosted MCP server. Thin pass-through to WordPress.com's official MCP; the live tool catalog is whatever that server advertises. Use when the user asks about WordPress.com sites, posts, pages, media, comments, or publishing workflows.

Audits

Pass
ClawScanPass

Agentic behavior and permission review.

Static analysisReview

Pattern checks against bundled files.

VirusTotalPass

Multi-engine malware detections and file reputation.

Install

openclaw skills install maverick-wordpress-mcp

WordPress

How to use this skill

This skill is a thin pass-through to WordPress.com's hosted MCP server at https://public-api.wordpress.com/wpcom/v2/mcp/v1. The live server is the source of truth for what tools exist, what they're called, what arguments they take, and any per-server instructions the server publishes.

Always invoke through bash {baseDir}/scripts/invoke.sh — never call mcporter directly. The wrapper seeds the OAuth vault from the env-supplied tokens when needed, then calls mcporter.

Step 1 — Discover the live tool catalog and any server-published usage instructions. Always run this first; do not rely on tool names from memory:

bash {baseDir}/scripts/invoke.sh list maverick-wordpress-mcp --schema

The output includes the server's Instructions: field, if published, and a JSON Schema for every tool's parameters. Treat this as the authoritative reference for the rest of the session.

Step 2 — Call any tool from the catalog using the form maverick-wordpress-mcp.<tool>:

bash {baseDir}/scripts/invoke.sh call maverick-wordpress-mcp.<tool> <arg>=<value> ...

Add --output json for structured output and transport-error envelopes:

bash {baseDir}/scripts/invoke.sh call --output json maverick-wordpress-mcp.<tool> ...

Safety

Write-capable tools can change public or private WordPress.com content. Confirm clear user intent before creating, editing, publishing, unpublishing, deleting, moderating, or uploading content, and read current state before changing it.

Authentication

Credentials are available to the agent runtime through required env vars. The wrapper seeds mcporter's vault as needed before each call. mcporter handles authentication automatically: it reads tokens from the vault, sends them with each request, and refreshes them on expiry.

The only failure mcporter cannot recover from on its own is grant revocation. It manifests as calls persistently failing with auth errors that do not clear on retry; ask the user to re-authorize the integration.

References