wp-headless-mcp

An MCP server that lets AI assistants read, and safely help edit, the content of a WordPress website.

It connects a company's WordPress site (pages, posts, custom post types like projects or services, ACF fields, and Yoast SEO data) to AI clients such as Claude. Then people can ask questions about the site, or get help with its content, in plain language.

Status: feature-complete for its first version and tested against a real WordPress site, with 120 unit tests.

What is MCP?

The Model Context Protocol is an open standard for connecting AI assistants to data and tools. An MCP server describes what it can do as:

• Tools: actions the AI can call, like "search the site" or "list recent projects".
• Resources: content the AI can read, like a specific page or the site's content model.
• Prompts: reusable task templates, like "review this page's SEO".

Any MCP-compatible client (Claude Desktop, Claude Code, the Claude API, and others) can use the same server without custom integration work.

The problem it solves

Many companies already keep their website content in WordPress: services, case studies, team members, FAQs, products. When they build something new on top of it, like a Progressive Web App (PWA), that content is often:

• Hard for AI to use. A chatbot or assistant needs grounded, current answers, not guesses. Wiring an LLM to the WordPress REST API by hand is repetitive and easy to get wrong.
• Locked behind admin screens. Content and marketing staff can't quickly ask "which pages have no meta description?" or "draft a post about our new service".
• Undocumented for developers. PWA developers have to discover post types, ACF field structures, and REST payloads by trial and error.

wp-headless-mcp gives all of these people one well-defined, safe AI gateway to the site.

How it fits with a PWA

                    ┌────────────────────────────┐
                    │     WordPress website      │
                    │  pages · projects · ACF ·  │
                    │  · Yoast SEO               │
                    └─────────────┬──────────────┘
                                  │ REST API
              ┌───────────────────┴───────────────────┐
              │                                       │
     PWA user interface                        wp-headless-mcp
  (reads REST API directly:                  (AI layer: tools,
   pages, lists, images)                     resources, prompts)
                                                      │
                               ┌──────────────────────┼──────────────────────┐
                               │                      │                      │
                      AI assistant in the PWA   Content team in      Developers in
                      (via the PWA backend      Claude Desktop       Claude Code
                       and the Claude API)

The PWA keeps reading content from WordPress directly for its normal screens. The MCP server sits next to it and powers the AI features, plus the tools around the site.

Who it's for

Website visitors (through the PWA)

An AI assistant inside the PWA that answers questions using the company's own content and links to the source page.

• "What services do you offer for product design?"
• "Show me projects you've done for retail companies."
• "How can I get in touch?"

It only sees published, public content and can't change anything.

Content and marketing team

Staff connect Claude Desktop to the site and work with content conversationally.

• "Which projects are missing a featured image or SEO description?"
• "Draft a case study for our latest project in the same style as the others."
• "Update the subtitle on the Acme project." (saved as a draft for review)

Changes are always saved as drafts or pending review. The AI never publishes or deletes content.

PWA developers

Developers connect Cl

... View full README on GitHub