Operate WPOS from your own agent over the Model Context Protocol.
WPOS is built on the Model Context Protocol (MCP). That means it is not just a
product you use through a UI. It is also a set of tools your own agent can drive.
Internally, WPOS exposes WordPress operations as MCP tools, which is how it
builds widgets, edits content, and manages sites in a structured, reviewable
way.
Your agent operates WPOS over MCP
These docs are also served as an MCP server, so your own Claude or Cursor can
load them and operate WPOS with full knowledge of how it works.
This documentation is available to AI agents as structured Markdown and as an MCP
server. Point your agent at it and it can answer questions about WPOS and help you
operate it, citing these pages directly.
Every page in these docs is also available as plain Markdown by adding .md to
the URL, which keeps token usage low for any agent reading them.
If your team already works in Claude or Cursor, MCP means WPOS fits into that
workflow rather than sitting beside it. The same memory that powers the
Command Center, your Playbook,
Skills, and Patterns, is what your agent
operates against.
