The Problem
WordPress powers 43% of the web. It has 500+ hooks, thousands of plugins, and major page builders, each with their own proprietary architecture. When an AI agent tries to modify a WordPress site, it is blind. It does not know which hooks fire where, which plugins conflict, or how a page builder injects its CSS.
MCP-WP is an architectural prototype for solving this problem. A Model Context Protocol server backed by LangGraph agent orchestration and Pinecone vector retrieval, designed to give AI agents structured visibility into WordPress architecture.
27 Agent Personas, 7 LangGraph Types
The system defines 27 agent personas in Postgres, built on 7 distinct LangGraph agent types. Each persona has a defined role and shared memory via Pinecone. The orchestration harness and realtime Cursor-to-Pinecone sync layer are live and production-ready.
5 Research
Scanning WordPress core, plugins, and Divi patterns
8 Implementation
Building MCP tools, tests, and documentation
2 Optimization
Performance tuning and code quality enforcement
12 Monitoring
System health, coordination, and anomaly detection
All orchestrated through LangGraph with shared Pinecone memory: 2,442 vectors across 67 indexed conversations. Every agent persona can recall what any other has learned.
Development Status
The orchestration harness and Cursor-to-Pinecone sync are production-ready. Performance scoring and revision loops are stubbed and in development. The agent personas are defined and tested individually; full autonomous coordination across the complete fleet is the next milestone.
Three Layers Deep
The architecture stacks three intelligence layers, each feeding the next.
Layer 1
Site Knowledge Graph
A knowledge graph that maps every theme, plugin, hook, and dependency on the target site.
Layer 2
Orchestration Hub
The decision engine. Site analysis, conflict detection, and deployment coordination.
Layer 3
Multi-AI Coordination
Designed for coordination across Claude, Cursor, and Copilot. Each model contributes its strengths to the final output.
Every Major Builder. Structured Analysis.
The scope of the mapping effort: every major WordPress page builder, analyzed and standardized into one protocol.
Across these major builders, the system catalogs WordPress hooks (action hooks, filter hooks, and builder-specific patterns), CSS injection methods, and conflict pattern types. Every pattern is classified with auto-severity rating and mapped to a standardized MCP interface.
27
Agent Personas
7
LangGraph Agent Types
2,442
Pinecone Vectors
<2s
Response Time
Live
Orchestration Harness
What I Learned
The WordPress ecosystem is a fractal of complexity. Every page builder reinvents the wheel. Divi has its own hook system. Elementor wraps widgets in proprietary containers. Oxygen bypasses the theme layer entirely. Standardizing that chaos into a protocol an AI agent can navigate taught me that knowledge graphs are not optional ... they are the foundation. Without a knowledge graph mapping the relationships between hooks, plugins, and templates, vector search alone returned plausible but wrong answers.
Multi-agent architectures need strict coordination or they diverge fast. The monitoring layer (12 of the 27 personas) exists because earlier versions let research and implementation agents drift out of sync. Adding a coordination protocol with shared Pinecone memory and explicit task handoff addressed that drift.
The honest takeaway: building the orchestration harness and sync layer was the valuable engineering work. The agent personas are defined and individually tested, but the full autonomous scoring and revision pipeline is still in progress. The architecture is sound; the execution is ongoing.
April 2026 . -JJ