All characters

AI co-pilot for complex stacks.

MCP-native WordPress operations. Clean API. Plays well with your existing tools.

Before Respira
  • WordPress REST API limited for complex operations
  • No safe write operations for AI
  • Page builder formats not documented
  • Manual PHP for custom workflows
  • Can't compose WordPress with other MCP servers
  • WordPress editing disconnected from dev workflow
with Respira for WordPress
  • 88 WordPress tools via MCP protocol
  • Duplicate-first safety built-in
  • Page builder schemas included
  • REST API wrapper with validation
  • Composes with GitHub, Linear, other MCPs
  • WordPress as part of AI-assisted stack

WordPress in Your MCP Stack

You're already using MCP servers for GitHub, Linear, Supabase, Vercel. WordPress was missing from that stack. Not anymore.

MCP-Native WordPress

@respira/wordpress-mcp-server implements 88 WordPress tools via MCP protocol. Full CRUD for pages/posts, page builder extract/inject, menu operations, media library, user management, taxonomy, SEO/performance analysis, WooCommerce (via add-on). All through standardized MCP protocol.

Builder Schemas Available

Divi, Elementor, and 9 other builders each store content differently. You'd need to learn 11 different formats. Respira provides complete schemas for all 11, validation before injection, type checking, nested structure handling. Ask AI to edit Divi—it knows Divi syntax. Ask AI to edit Elementor—it knows Elementor syntax.

Safety Architecture

Duplicate-before-edit is not optional. Every mutation returns approvals URL. AI can't accidentally publish to production. Rollback is built-in. Every change tracked. Version history maintained. One-click restore.

WebMCP Support

Same 172 tools available in Desktop AI (Claude Code, Cursor, Windsurf) and Browser AI (Claude in Chrome, Gemini in Chrome). One plugin. Two interfaces. Same safety.

See Pricing

Earn

Know what each tool call costs before you quote it.

Earn ships inside the Respira dashboard on every plan. It times every tool call, classifies read vs. write, and rolls up cost per site, per tool, per client. Useful when a 30-minute job replaces an 8-hour one and you need to set a defensible price.

Per site

Cost rolls up by domain. One client, one number. Multi-site agencies see the whole portfolio in one view.

Per tool

See which tools dominate latency and spend so you can scope correctly on the next quote.

Privacy hard line

Metadata only. No prompts, no tool args, no tool results, no WP content. Opt out entirely with one env var.

See how Earn works →