The WP DevDocs MCP server, built by pluginslab, provides wp-devdocs-mcp is a local MCP server that gives an AI coding assistant a verified WordPress hook database to query instead of recalling hook names from training data. It is community-built and best for Search.
by pluginslab
About
wp-devdocs-mcp is a local MCP server that gives an AI coding assistant a verified WordPress hook database to query instead of recalling hook names from training data. It parses the actual source of WordPress core, WooCommerce, Gutenberg, or any plugin you point it at — including private and proprietary ones no model has ever seen — and builds a searchable index of every PHP action and filter (do_action, apply_filters, and their _ref_array variants), every JS hook (addAction, addFilter, applyFilters, doAction), every block registration (registerBlockType, registerBlockVariation), and JS API usage across wp.blocks, wp.blockEditor and wp.data. Since v1.1.0 it also parses handbook markdown into searchable pages. For each hook the assistant gets the exact name with dynamic-name detection for patterns like woocommerce_thankyou_{$payment_method}, the parameter list and count, file path and line number, the enclosing function and class, the docblock, and a code window of eight lines before and four after. The problem it solves is specific: models invent plausible hooks such as woocommerce_email_after_order_details that do not exist, reach for deprecated namespaces like wp.editor.InspectorControls instead of wp.blockEditor.InspectorControls, and miss newer HPOS-era hooks entirely. In an agentic loop that writes and tests its own code, one hallucinated hook name sends the agent debugging something that was never going to work.
Trust verdict
How grades are computed →Grade A (94/100, reliable) from 1 measured signal, based on repository evidence. Only one signal stands behind it, so treat the grade as provisional.
What was measured
- Repository maintenance100/100 · weight 20
The repository has been pushed to or released within the last six months. — last push 2026-05-18, last release 2026-03-11 (v1.1.2).
- Source verification100/100 · weight 25
The repository URL was confirmed to resolve against the live GitHub API and is not archived.
- Provenance65/100 · weight 10
Community-built. That is not a mark against it — most of the ecosystem is community-built — but there is no vendor accountable for keeping it working.
- Listing ↔ repository match100/100 · weight 5
The listing name lines up with the linked repository pluginslab/wp-devdocs-mcp.
What could not be measured
These contributed nothing to the score — not a penalty, not a zero. They are why the confidence reads the way it does.
- Live MCP handshakeunknown
No remote endpoint to handshake — this server installs and runs locally over stdio, so there is nothing to probe from the outside.
- Measured uptimeunknown
No probe history recorded for this server yet.
- Tool-schema stabilityunknown
Drift is a difference between two successive checks, and this server has none recorded.
Installation
npm install -g wp-devdocs-mcpwp-devdocs-mcp confirmed live on the npm registry — checked August 17, 2026.
Categories
Frequently Asked Questions
What is WP DevDocs MCP Server?
Who built WP DevDocs MCP Server?
Is WP DevDocs MCP Server free?
How do I install WP DevDocs MCP Server?
What does WP DevDocs MCP Server integrate with?
Repo Health
Local/stdio install — runs on your machine, so there is no remote endpoint to verify live. Trust signal below is from the source repo.
- Last commit
- 4mo ago
- Last release
- v1.1.2 · 6mo ago
- Install
- npm
Quick Info
- Install Type
- npm
- Author
- pluginslab
- Categories
- 2
- Integrations
- 5
Related Servers
Everything
Reference/test server with prompts, resources, and tools. Perfect for testing MCP implementations.
Git
Tools to read, search, and manipulate Git repositories. Full Git operations support.
Sequential Thinking MCP Server
a single structured-reasoning tool that lets a model plan, revise and branch its own chain of thought instead of answering in one shot. Published by Anthropic as part of the official modelcontextprotocol/servers monorepo (89,000+ stars, actively maintained), it exposes exactly one tool — sequential_thinking — and that tool is the whole product. Each call carries a `thought` string plus bookkeeping fields: `thoughtNumber`, `totalThoughts`, and `nextThoughtNeeded`, which the model flips to false when it is done. The interesting fields are the optional ones. `isRevision` and `revisesThought` let the model go back and correct an earlier step rather than plowing ahead on a bad assumption; `branchFromThought` and `branchId` let it fork into an alternative line of reasoning and carry both forward; `needsMoreThoughts` lets it extend past its own original estimate when a problem turns out to be deeper than it looked. In practice you never call the tool by hand. You connect the server to an MCP host and ask a question that deserves more than one pass — plan a PostgreSQL 14 to 16 migration and revise if downtime exceeds five minutes, work out why a deploy only fails in production, compare three architectures and branch when an assumption breaks. You can tell it is working when the host inspector shows repeated sequential_thinking calls with a rising `thoughtNumber` rather than a single response. Install with `npx -y @modelcontextprotocol/server-sequential-thinking` — note the hyphenated package name, which differs from both the `sequentialthinking` directory in the repo and the Docker image `mcp/sequentialthinking`, a mismatch that breaks a lot of copied configs. A Docker image is published alongside the npm package, and the README carries one-click VS Code install buttons for both transports. Set `DISABLE_THOUGHT_LOGGING=true` if you do not want every thought written to the server log.
21st.dev Magic
Create crafted UI components inspired by the best 21st.dev design engineers.
Apify MCP Server
The Apify MCP server gives AI agents access to 6,000+ ready-made cloud scrapers, crawlers, and automation tools on the Apify Store — no infrastructure required. Connect to Apify Actors that extract data from social media platforms (Instagram, TikTok, LinkedIn), search engines (Google, Bing), e-commerce sites (Amazon, eBay), maps (Google Maps), and virtually any website. Each Actor runs in the cloud with managed proxies, browser fingerprinting, and anti-bot bypass built in. Use the Apify MCP server to query Actors by task, stream results directly into your AI context, run custom scraping Actors from your Apify account, and chain multiple data extraction steps in a single workflow. Supports tool filtering to expose only the Actors you need, and integrates with Apify's RAG web browser Actor for retrieval-augmented generation use cases.
Sponsored
Better Stack
Free PlanGet alerted when your APIs, browser tests, payment pipelines, or MCP server dependencies go down. Used by 100K+ developers.
Start monitoring free →