💬
You talk to AI
"Update all Contact Us buttons to say Get Started and make them green."
Natural language in Claude Code or Cursor
Tech Explained
What is MCP?
MCP (Model Context Protocol) is the language AI coding assistants use to talk to tools. Respira speaks MCP, which is how Claude Code, Cursor, and Windsurf can safely edit your WordPress sites.
Think of MCP as a translator. Your AI speaks English. WordPress speaks PHP and databases. MCP translates between them so they can work together.
The Simple Version
🔄
MCP translates
AI asks for site context, finds pages, creates duplicates, and applies updates through tools.
MCP protocol and typed tool calls
🔧
Respira executes
Respira plugin receives requests, edits duplicates, and returns clean results.
WordPress REST API and duplicate-before-edit
✅
You review and approve
You check changes in WordPress admin and publish only what you want.
Your decision, your control
You do not need to understand MCP to use Respira. This page is for curious users and technical evaluators.
How MCP Works (Technical Version)
AI Assistant
Claude Code, Cursor, Windsurf
Natural language instructions
⟷ MCP Protocol
MCP Server
Respira MCP Server (TypeScript)
Translates tools into API calls
⟷ REST API
WordPress Plugin
Respira Plugin (PHP)
Executes safely on duplicates
WordPress Site
Your live site
Original pages remain protected
Standardized Protocol
MCP is an open standard. Any MCP-compatible AI can connect without one-off integrations per assistant.
Tool Discovery
AI sees available tools automatically. Add WooCommerce add-on and new e-commerce tools appear automatically.
Context Sharing
Respira provides page-builder context, modules, and site structure so AI does not guess blindly.
Type Safety
Tools define input and output schemas, so the assistant knows exactly what it can call and what it gets back.
Why MCP Matters
🔌 Works With Any AI
Respira works with Claude Code, Cursor, Windsurf, Cline, VS Code Continue, and future MCP-compatible assistants.
Without MCP: custom integration per AI tool, fragile and expensive to maintain.
🎯 Context-Aware AI
Respira gives AI rich site context so it can reason about your actual WordPress setup.
Without MCP: weaker discovery and more "guess-based" edits.
🛡️ Safety Boundaries
Duplicate-first rules are inside the tools AI calls. This creates enforceable safety boundaries.
Without MCP: no robust middle layer for safe write operations.
📚 Auto-Discovery
When capabilities change, assistants discover updates from the server automatically.
Without MCP: static mappings and fast documentation drift.
WordPress AI
Registered as WordPress Ability
Respira is registered as an official WordPress Ability in the WordPress AI ecosystem, discoverable through the MCP Adapter path.
Discoverable
WordPress AI tools can discover Respira capabilities after plugin setup.
Ecosystem Integration
Respira is aligned with the broader WordPress AI architecture direction.
Future-Proof
As MCP adoption grows, Respira stays compatible across assistants.
MCP vs Other Approaches
| Approach | How It Works | Pros | Cons |
|---|---|---|---|
| MCP (Respira) | AI talks to MCP server, server talks to WordPress | Context-aware, multi-assistant compatible, safety by design | Requires MCP server process (provided by Respira) |
| Direct API Access | AI calls WordPress REST endpoints directly | Simple setup | No built-in safety workflow or builder intelligence |
| Browser-side (WebMCP) | AI controls browser sessions in wp-admin | Visual context | Often slower and tied to active browser sessions |
| Custom Integrations | Per-assistant proprietary connectors | Can be tailored tightly | High maintenance, brittle with assistant updates |
50+ Core Tools + WooCommerce Add-on Tools
When AI connects through Respira, it receives a clear tool catalog grouped by capability. With the WooCommerce add-on, extra commerce tools are auto-discovered.
📄 Content
List pages and posts, read content, create duplicates, update drafts, publish.
🎨 Page Builders
Detect builder, parse structure, inject updates, validate before save.
🖼️ Media
List media, upload images, set featured images, optimize assets.
🔍 SEO and Performance
Analyze metadata and structure, check CWV signals, suggest fixes.
🛒 WooCommerce Add-on
Product CRUD, variations, order status flows, stock operations, coupons, customers, and sales reports via license-gated tools.
⚙️ Site Management
User, menu, taxonomy, option, and plugin operations with safeguards.
WooCommerce MCP Abilities (Add-on)
Respira exposes dedicated WooCommerce MCP tools such as woocommerce_list_products, woocommerce_create_product, woocommerce_list_orders, woocommerce_update_order_status, woocommerce_get_stock_status, and woocommerce_sales_report. These tools are registered only when the WooCommerce add-on is installed and licensed.
For Developers
MCP Server Implementation
Respira MCP server is TypeScript-based and follows MCP SDK patterns.
npm install @respira/wordpress-mcp-serverTool Definition Example
server.registerTool('wordpress_list_pages', schemaAndHandler);
// Tool is declared with typed input schema.
// Server maps tool call to /wp-json/respira-press/v1 endpoints.Common Questions About MCP
Do I need to understand MCP to use Respira?
No. Install the plugin, connect your AI, and start editing. MCP stays in the background.
What AI tools support MCP?
Claude Code, Cursor, Windsurf, Cline, VS Code Continue, and other MCP-compatible assistants.
Is MCP secure?
MCP is a protocol. Security comes from implementation. Respira uses authentication, validation, permissions, and duplicate-first safeguards.
What is the difference between MCP and REST API?
WordPress REST API exposes operations. MCP helps assistants discover and call those operations in a standard way.
Can AI call WordPress REST API directly instead?
It can, but then you lose discovery, context layers, and safety boundaries baked into Respira's MCP tools.
What WooCommerce abilities are available through MCP?
With the WooCommerce add-on enabled, MCP exposes product, variation, order, inventory, coupon, customer, and reporting tools. They are license-gated and auto-discovered by the assistant when active.
Will this work with future AI assistants?
Yes. If a new assistant supports MCP, it can integrate with Respira.
Ready to Try Respira?
You do not need to understand MCP to use Respira. It works behind the scenes so you can focus on safe edits.
7-day free trial. No credit card required. EUR 19/year after trial.