WordPress Block Catalog
FreeNot checkedA read-only MCP server that provides verified WordPress block definitions and markup across product environments, enabling search, comparison, generation, and v
About
A read-only MCP server that provides verified WordPress block definitions and markup across product environments, enabling search, comparison, generation, and validation of blocks.
README
Give agents and developer tools verified WordPress block definitions and markup for the exact public product environment they target.
WordPress Block Catalogue MCP is a read-only Model Context Protocol server for finding, comparing, generating, and validating blocks shipped by WordPress, Gutenberg, WooCommerce, and Jetpack. It keeps source metadata, PHP registration, editor registration, and runtime verification as separate observations so clients do not have to guess from source files.
Capabilities
- Resolve block definitions through explicit product and version layers.
- Search blocks and inspect attributes, supports, relationships, variations, availability, and provenance.
- Compare one block across environments.
- Generate or validate markup at the strongest verified evidence level.
- Report drift between source metadata, the PHP registry, and the editor registry.
- Reject non-public sources and provenance from the public delivery artefact.
Requirements
- Node.js 20 or newer
- npm
The package is not published to npm. Clone the repository and run it from the working tree.
Quick start
git clone https://github.com/danielk-am/wp-block-catalog-mcp.git
cd wp-block-catalog-mcp
npm ci
npm run verify
Start the stdio MCP server with the committed public catalogue and runtime evidence:
WP_BLOCK_CATALOG_PATH="$PWD/catalog/public.release.generated.json" \
WP_BLOCK_DEFAULT_ENVIRONMENT="[email protected]" \
WP_BLOCK_RUNTIME_PATHS="$PWD/runtime/wordpress-7.0.2-post-editor.reconciled.json:$PWD/runtime/wordpress-7.0.2-gutenberg-23.6.2-post-editor.reconciled.json:$PWD/runtime/wordpress-7.0.2-woocommerce-10.9.4-post-editor.reconciled.json:$PWD/runtime/wordpress-7.0.2-jetpack-16.0.1-disconnected-post-editor.reconciled.json" \
WP_BLOCK_VERIFICATION_PATHS="$PWD/runtime/wordpress-7.0.2.verified-markup.json:$PWD/runtime/wordpress-7.0.2-gutenberg-23.6.2.verified-markup.json:$PWD/runtime/wordpress-7.0.2-woocommerce-10.9.4.verified-markup.json:$PWD/runtime/wordpress-7.0.2-jetpack-16.0.1-disconnected.verified-markup.json" \
npm start
For an MCP client, use absolute paths:
{
"mcpServers": {
"wp-block-catalog": {
"command": "node",
"args": ["/absolute/path/wp-block-catalog-mcp/dist/mcp/server.js"],
"env": {
"WP_BLOCK_CATALOG_PATH": "/absolute/path/wp-block-catalog-mcp/catalog/public.release.generated.json",
"WP_BLOCK_DEFAULT_ENVIRONMENT": "[email protected]",
"WP_BLOCK_RUNTIME_PATHS": "/absolute/path/wp-block-catalog-mcp/runtime/wordpress-7.0.2-post-editor.reconciled.json:/absolute/path/wp-block-catalog-mcp/runtime/wordpress-7.0.2-gutenberg-23.6.2-post-editor.reconciled.json:/absolute/path/wp-block-catalog-mcp/runtime/wordpress-7.0.2-woocommerce-10.9.4-post-editor.reconciled.json:/absolute/path/wp-block-catalog-mcp/runtime/wordpress-7.0.2-jetpack-16.0.1-disconnected-post-editor.reconciled.json",
"WP_BLOCK_VERIFICATION_PATHS": "/absolute/path/wp-block-catalog-mcp/runtime/wordpress-7.0.2.verified-markup.json:/absolute/path/wp-block-catalog-mcp/runtime/wordpress-7.0.2-gutenberg-23.6.2.verified-markup.json:/absolute/path/wp-block-catalog-mcp/runtime/wordpress-7.0.2-woocommerce-10.9.4.verified-markup.json:/absolute/path/wp-block-catalog-mcp/runtime/wordpress-7.0.2-jetpack-16.0.1-disconnected.verified-markup.json"
}
}
}
}
*_PATHS uses the operating system path delimiter, : on macOS and Linux or
; on Windows. Singular *_PATH and plural *_PATHS settings can be
combined. Duplicate environment bundles or verification record identities
stop the server at startup.
AI client setup
Use the public catalogue definition above under the same wp-block-catalog name in each client:
- Claude Code stores user-scoped servers in its user configuration. Check the result with
claude mcp get wp-block-catalog. - Claude Desktop stores the definition under
mcpServersinclaude_desktop_config.json. - Codex stores the definition in
~/.codex/config.toml. Codex CLI, the desktop app, and the IDE extension share this configuration. Check it withcodex mcp get wp-block-catalog. - VS Code and VSCodium store the same server object under
serversin the usermcp.json. Their--add-mcpcommand accepts the definition as JSON. - Gemini CLI stores the definition under
mcpServersin~/.gemini/settings.json. Check it withgemini mcp listfrom a trusted folder.
Restart desktop and IDE clients after changing their user configuration. The public repository does not contain the separate WordPress.com private catalogue.
Supported environments
| Environment | Server registry | Client registry | Verified evidence |
|---|---|---|---|
| WordPress 7.0.2 | 110 blocks | 109 blocks | Static, deprecated, and dynamic |
| WordPress 7.0.2 with Gutenberg 23.6.2 | 160 blocks | 116 blocks | Static, deprecated, and dynamic |
| WordPress 7.0.2 with WooCommerce 10.9.4 | 285 blocks | 264 blocks | Dynamic |
| WordPress 7.0.2 with Jetpack 16.0.1, disconnected | 110 blocks | 109 blocks | Core static smoke |
See runtime captures for capture details and the catalogue audit for product-specific acceptance cases.
MCP tools and resources
Primary tools:
list_environmentssearch_blocksget_blockcompare_block_versionsgenerate_markupvalidate_markupget_verification_evidenceget_runtime_drift
Compatibility aliases:
get_block_schemaget_block_markuplist_block_attributessearch_variations
Resources:
wp-block-catalog://manifestwp-block-catalog://blocks/{environment}/{name}
Evidence model
The catalogue retains three observations independently:
- metadata from an allowlisted path at a pinned source commit;
- the final PHP block registry from the matching product environment;
- the client block registry from the real editor.
Static markup is verified by running the registered save implementation, parsing its output, and running WordPress validation. Deprecated markup is verified through fixture matching, migration, current save, parsing, and validation. Dynamic markup is verified through the registered PHP render callback.
The architecture decision explains why disagreements remain visible.
Rebuilding the catalogue
Place exact source checkouts under .checkouts/ as declared in
build/public.json, then run:
npm run catalog:build
npm run catalog:health
The build stops when a checkout differs from its manifest commit. Product adapters scan only declared include paths and never select duplicate definitions by scan order.
Check the four supported public stable channels:
npm run check:sources
The command exits 0 when every pin is current, 10 when a supported update
exists, and 20 when the check is indeterminate. It never falls back to a
branch head.
Verify a release candidate against a saved previous public release:
npm run catalog:release -- /path/to/previous-public.json
This command rebuilds from the exact checkouts, compares the result with the committed delivery artefact, checks freshness, and rejects unexplained removals.
Capturing the Jetpack profile
Install Chromium once:
npx playwright install chromium
Capture the disconnected Jetpack environment through a local wp-env
instance:
WP_BLOCK_CATALOG_ADMIN_USER="<local-wp-env-admin>" \
WP_BLOCK_CATALOG_ADMIN_PASSWORD="<local-wp-env-password>" \
npm run capture:jetpack -- \
--config .wp-env.jetpack.json \
--profile profiles/wordpress-7.0.2-jetpack-16.0.1-disconnected-post-editor.json \
--environment environments/wordpress-7.0.2-jetpack-16.0.1.json \
--output-dir /tmp/wp-block-catalog-jetpack-capture
The wrapper validates the public disconnected profile, captures the PHP and editor registries plus a Paragraph save-and-validate probe, destroys the isolated environment, then publishes the raw evidence.
Public data boundary
This repository contains only public source manifests, public runtime evidence, and the public delivery artefact. The delivery layer rejects non-public sources, definitions, environments, paths, revisions, provenance, and gate details.
Do not add private source checkouts, captures, catalogues, logs, or credentials to this repository. Use synthetic fixtures when testing the privacy boundary.
Development
Run the complete local gate:
npm ci
npm run verify
npm audit --omit=dev
git diff --check
Read AGENTS.md before changing source manifests, resolution rules, or verification labels.
Status
Version 0.1.4 is the initial public-only repository snapshot. It includes four public environments and a committed deterministic release artefact.
License
No open-source license has been granted yet. Public visibility does not grant permission to copy, modify, or redistribute the code.
Installing WordPress Block Catalog
This server has no published package — it is built from source. Open the repository and follow its README.
▸ github.com/danielk-am/wp-block-catalog-mcpFAQ
Is WordPress Block Catalog MCP free?
Yes, WordPress Block Catalog MCP is free — one-click install via Unyly at no cost.
Does WordPress Block Catalog need an API key?
No, WordPress Block Catalog runs without API keys or environment variables.
Is WordPress Block Catalog hosted or self-hosted?
Self-hosted: the server runs locally on your machine via the install command above.
How do I install WordPress Block Catalog in Claude Desktop, Claude Code or Cursor?
Open WordPress Block Catalog on unyly.org, pick your client tab (Claude Desktop, Claude Code, Cursor) and press Install — the config is generated automatically, no JSON editing.
Related MCPs
GitHub
PRs, issues, code search, CI status
by GitHubFilesystem
Secure file operations with configurable access controls.
Memory
Knowledge graph-based persistent memory system.
Template MCP Server
A CLI tool to create a new Model Context Protocol server project with TypeScript support, dual transport options, and an extensible structure
by mcpdotdirectCompare WordPress Block Catalog with
Not sure what to pick?
Find your stack in 60 seconds
Author?
Embed badge for your README
Browse similar
All development MCPs
