Skill Detail

Automattic WordPress Remote MCP

Automattic WordPress Remote MCP connects MCP clients to live WordPress sites using OAuth, JWT, or application passwords. It is aimed at agents that need to read or operate against WordPress content and site features through a maintained remote MCP bridge.

WordPress & CMSMCP
WordPress & CMS MCP Security Reviewed
โญ 131 GitHub stars โฌ‡ 2.5k/wk npm
INSTALL WITH ANY AGENT
npx skills add agentskillexchange/skills --skill automattic-wordpress-remote-mcp Copy
Works best when you want a reusable capability, not another fragile one-off prompt.
At a glance
Tools required
WP_API_URL, WP_API_USERNAME, WP_API_PASSWORD
Install & setup
npm install @automattic/mcp-wordpress-remote
Author
Automattic
Last updated
Apr 6, 2026
Quick brief

Automattic WordPress Remote MCP is a WordPress-focused MCP server maintained by Automattic. Its job is to let an MCP-compatible client connect to a remote WordPress site and work with site content through supported authentication methods including OAuth 2.1 with PKCE, JWT tokens, and legacy WordPress application passwords. That makes it especially useful for editorial workflows, content operations, WooCommerce reporting, and site administration tasks where an agent needs controlled access to a live WordPress environment.

How it works

What this skill actually does

The project is published as the npm package @automattic/mcp-wordpress-remote and the README documents a standard npx -y @automattic/mcp-wordpress-remote launch path with WP_API_URL in the environment. The upstream repository also points users to the WordPress MCP adapter plugin for the site side of the connection. That integration model is important: the remote MCP server runs with the client, while the WordPress site exposes the capabilities the server can use.

This entry belongs in WordPress & CMS because its concrete job-to-be-done is connecting AI assistants to WordPress instances in a supported way. It also maps directly to the MCP framework because the server exposes tools and resources through the MCP protocol rather than through a custom agent-only format. The repository is active, licensed, and backed by a recognized WordPress company, which clears the verified metadata intake gate for a source-backed listing.