What is Respira for WordPress?

Choose your character

You are at the threshold. Pick the role that matches your world, then step into a version of your workflow where change is faster, safer, and easier to trust.

← Back to personas

The Builder

Your Workflow, Extended to WordPress

You ship through prompts, tooling, and flow state.

You want WordPress operations to feel like the rest of your MCP-native stack.

Your call to adventure: extend vibe coding beyond code files into live CMS systems safely.

Featured Scenario: Multi-Page Shipping Policy Patch

Code-focused setup for AI-assisted development

Before: Policy changes require repetitive manual edits across dozens of pages.

After: AI executes a structured batch update and hands you a reviewable approval package.

Ordinary World (Before)

  • WordPress still feels like a manual side quest.
  • Builder edits are brittle without structure awareness.
  • Bulk changes are hard to trust at scale.

Transformed World (After)

  • WordPress tools appear in your MCP workflow.
  • Builder-aware operations target real modules.
  • Duplicate-first approvals keep client sites safe.
01

The Side Quest

CMS work breaks your coding flow and confidence.

02

The Alignment

WordPress tools plug into your MCP-native stack.

03

The Velocity

You ship structural changes without losing control.

88 MCP tools
11 page builders
5-minute setup

Your Workflow, Extended

Respira extends MCP-driven coding workflows into WordPress operations.

Same assistants, same protocol, same conversational control, but tool calls target WordPress resources.

Tech Stack

  • MCP server: TypeScript / Node.js
  • Tool count: 88 (77 WordPress + 11 WooCommerce)
  • Runtime: Node 18+
  • Config: ~/.respira/config.json
  • Clients: Cursor, Claude Code, Windsurf, Claude Desktop
npm install -g @respira/wordpress-mcp-server
respira-mcp configure
respira-mcp add-site

Builder Intelligence

Respira can operate on builder structures rather than naive HTML find/replace.

This allows targeted module changes where supported and safer structured updates across builders.

Supported Builders (11)

  • Divi, Elementor, WPBakery, Oxygen, Bricks, Beaver Builder, Brizy, Visual Composer, Thrive Architect, Breakdance, Gutenberg

Tool Categories

  • Context/Discovery tools
  • Builder tools (detect/extract/inject/update)
  • Pages/Posts CRUD + duplicate
  • Media tools
  • Menus/Taxonomies/CPT/Users/Comments/Options tools
  • Analysis tools (SEO, performance, readability, AEO, structured data)
  • Plugin lifecycle tools (experimental)
  • WooCommerce tools (conditional)

Safety Architecture

Write operations are duplicate-first by default and require approval for publish.

Force edits are intentionally guarded and audited.

  1. AI operation creates duplicate
  2. System returns approval URL
  3. User reviews changes
  4. Approve publishes and keeps backup, reject discards duplicate

Browser Path Also Available

WebMCP in Chrome 146+ exposes the same tool model in-browser for fast non-technical workflows and demos.

Desktop MCP remains better for heavy/batch and code-adjacent operations.

Known Limitations

  • Module-level update support is strongest on Divi and Elementor
  • Some builder transformations require manual cleanup
  • No fully automated rollback API path in current UX
  • Rate limits and stateless calls can affect very large batch runs

Detailed Setup

  1. Install plugin and generate API key in WordPress admin.
  2. Install MCP server via npm/npx.
  3. Configure site URL and key in ~/.respira/config.json.
  4. Register server in Cursor/Claude config.
  5. Run a test prompt: "List all pages on my WordPress site".
{
  "mcpServers": {
    "respira": {
      "command": "npx",
      "args": ["@respira/wordpress-mcp-server"]
    }
  }
}
View Setup Docs

Built by One Person

Respira was built by Mihai, a solo founder from Brașov, Romania.

After 22 years building products for others, Mihai finally had the tools to build what he'd always wanted: a bridge between WordPress (43% of the web) and modern AI.

Not because he became a "real developer." He's what he calls a "gringo vibe coder"—building with AI through feel, not formal training.

Which makes sense when you think about it.

Someone using AI to build... is building AI tools for WordPress.

The name comes from Latin: re-spirare—to breathe again.

The philosophy: simple systems that breathe.

Not complex dashboards. Not hustle-culture "10x your output" bullshit. Just: duplicate before you edit. Approve when ready. Don't break things.

This isn't backed by venture capital. No team of engineers. One person, building in public, driven by a simple belief: AI should make WordPress better—not replace human craft, but amplify it.

Better accessibility. Cleaner code. Faster workflows.

If Respira saves you time or fixes something that matters—that's the whole point.

— Mihai
Brașov, Romania
Newsletter • LinkedIn

Subscribe for product updates and builder notes.

1,214commits
54,885lines of code
3 monthsto v3.0
1 personbuilding