Ext Ops Panel
Open dashboard
Comparison

build-with-wordpress vs WordPress MCP

build-with-wordpress is a plugin bundle for AI coding tools published by Automattic. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Claude Code: claude-plugins-community). WordPress MCP is an MCP server published by Servosity. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacebuild-with-wordpressWordPress MCP
Claude Code: claude-plugins-official Listed
Version: 0.0.2
Forks (GitHub): 10
Stars (GitHub): 51
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Listed
Version: 0.0.2
Forks (GitHub): 10
Stars (GitHub): 51
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.5
Forks (GitHub): 12
Stars (GitHub): 59
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

build-with-wordpress vs WordPress MCP
Factbuild-with-wordpressWordPress MCP
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)51 (worse)59 (better)
Forks (GitHub) (differs)10 (worse)12 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (https://github.com/Servosity/msp-skills/releases/download/wordpress-v0.1.5/wordpress-mcp.mcpb)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published5, secrets among them: 2
Parts of the bundle (differs)4Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/automattic/claude-code-wordpress.comgithub.com/servosity/msp-skills
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

build-with-wordpress

In its own words, on Claude Code: claude-plugins-official:

Craft production-grade WordPress sites and applications. Everything from themes and plugins to commerce and deployment.

WordPress MCP

In its own words, on Official MCP Registry:

Publish and manage WordPress pages, posts, media

How to run each

build-with-wordpress As a Claude Code plugin

Claude Code
/plugin install build-with-wordpress@claude-plugins-official

WordPress MCP

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Requires: WORDPRESS_BASIC_AUTH (secret), WORDPRESS_MCP_HTTP_TOKEN (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of build-with-wordpress publish no settings it asks for, so we do not compare settings.

What it can do: build-with-wordpress · What it can do: WordPress MCP · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built