Connect Codex (and other MCP-capable clients) to WordPress.com using OAuth 2.1 + PKCE, then run site/content/account workflows through the official WordPress.com MCP server.
- Connect WordPress.com through MCP in Codex-compatible clients.
- Verify access with site and post discovery checks.
- Troubleshoot common OAuth and MCP session issues.
- Publish posts via WordPress.com REST API when MCP tools are read-only.
SKILL.md: Main workflow and operational guidance.references/endpoints.md: Canonical MCP/OAuth/REST endpoints.agents/openai.yaml: Agent metadata and default prompt.scripts/publish_post.py: REST API fallback script for post publishing.
- Read
SKILL.md. - Complete OAuth 2.1 + PKCE with the endpoints in
references/endpoints.md. - Verify tools with:
wpcom-mcp-user-siteswpcom-mcp-posts-search
- If write tools are unavailable in MCP, use:
scripts/publish_post.py
WPCOM_ACCESS_TOKEN='<token>' \
python3 scripts/publish_post.py \
--site tomwillmot.com \
--title "Hello from Codex" \
--content "<p>Published via REST API fallback.</p>" \
--status publishMIT