ABOUT

Built by Operators, for Operators

We got tired of switching between 15 tabs to manage WordPress. So we built a bridge between AI and your CMS.

Why MCPWP?

WordPress powers 40% of the web, but managing it still means clicking through endless admin screens. We believed there had to be a better way.

MCPWP was born from a simple idea: what if you could just tell your AI assistant what you want, and it would handle the WordPress part? No more copy-pasting between tools. No more hunting for the right settings page. Just describe what you need in plain English, and your site updates itself.

We built MCPWP using the Model Context Protocol (MCP) โ€” an open standard that lets AI assistants interact with external tools. This means MCPWP works with Claude, Cursor, and any MCP-compatible client.

OUR PRINCIPLES

What We Believe

๐ŸŒ

Open Standards

Built on MCP, not proprietary APIs. Your AI client, your choice.

โšก

WordPress Native

Pure REST API. No external dependencies. Works with any hosting.

๐Ÿ› ๏ธ

Developer First

Clean endpoints, comprehensive docs, sensible defaults.

This Site Was Built With MCPWP

Every page you’re reading was created, styled, and published using our own plugin’s MCP tools. We don’t just build it โ€” we use it every day.