respira-wordpress-mcp

<p align="center"> <a href="https://www.respira.press"> <img src="https://www.respira.press/og/respira-home-og.jpg" alt="Respira for WordPress" width="100%"> </a> </p> <h1 align="center">Respira WordPress MCP Server</h1> <p align="center"> <strong>MCP tools and WordPress Abilities across 19 page builders. The AI infrastructure layer for WordPress.</strong><br> Element-level editing, full page creation, HTML and Figma to native builder conversion, design directions, site memory, accessibility and security scanning, per-tool governance, snapshots and rollback. </p> <p align="center"> <a href="https://www.npmjs.com/package/@respira/wordpress-mcp-server"><img src="https://img.shields.io/npm/v/@respira/wordpress-mcp-server.svg?style=flat-square&color=10b981" alt="npm version"></a> <a href="https://www.npmjs.com/package/@respira/wordpress-mcp-server"><img src="https://img.shields.io/npm/dm/@respira/wordpress-mcp-server.svg?style=flat-square" alt="npm downloads"></a> <a href="https://www.respira.press/tools"><img src="https://img.shields.io/badge/tools-live%20catalog-10b981?style=flat-square" alt="Tool catalog"></a> <img src="https://img.shields.io/badge/builders-19-10b981?style=flat-square" alt="19 page builders"> <img src="https://img.shields.io/badge/TypeScript-100%25-blue?style=flat-square&logo=typescript&logoColor=white" alt="TypeScript"> </p> <p align="center"> <a href="https://www.respira.press">Website</a> • <a href="https://www.respira.press/docs">Docs</a> • <a href="https://www.respira.press/plugin">Plugin</a> • <a href="https://www.respira.press/mcp">MCP setup</a> • <a href="https://www.respira.press/skills">Skills</a> • <a href="https://www.respira.press/support">Support</a> </p>

---

What this repo is, what it isn't

This repository is the public listing for the Respira WordPress MCP server. The server source ships on npm as @respira/wordpress-mcp-server. That wrapper code is MIT-licensed and you are welcome to read, fork, or vendor it.

The server is a client for the Respira WordPress plugin, not a standalone product. To do real work it needs:

• The Respira for WordPress plugin installed on your site
• A valid Respira API key bound to a license

The plugin is not open source. It is distributed under a commercial license. Free trial at respira.press, no card required. Paid plans start at 9 EUR a month.

In short: the wrapper you npx -y is open. The product behind it is not, and that is deliberate. If you want a self-contained "AI edits WordPress" stack with no commercial dependency, this is not it. The plugin is built and maintained full time by one person, and the license fees are how that happens.

For security reports see SECURITY.md.

---

What makes Respira different

Most WordPress MCP servers wrap the REST API. They can create posts and pages, but they cannot touch page builder content, which is where the actual site lives.

Respira ships a WordPress plugin that gives an AI agent native access to the builder's own data structures, plus the safety rails that make writing to a live site survivable.

| Capability | Respira | REST API wrappers | |---|---|---| | Page builder support | 19 builders | None | | Element-level find / update / move / remove | Yes | No | | Build full pages from a declarative structure | Yes | No | | Convert HTML or Figma to native builder output | Yes | No | | Design directions (site-wide art direction) | Yes | No | | Site memory that persists across agent sessions | Yes | No | | Accessibility scan and auto-fix | Yes | No | | Security audit and core hardening | Yes | No | | Snapshot before every write, rollback anytime | Yes | No | | Duplicate-before-edit safety | Yes | No | | Per-tool governance from wp-admin | Yes | No | | WordPress Abilities API and WebMCP | Yes | Rare | | WooCommerce (products, orders, inventory, storefront) | Yes (add-on) | No |

---

Quick start

1. Install the WordPress plugin

Download from respira.press/plugin, upload to WordPress, activate, then go to Respira > API Keys and generate a key.

2. Connect your AI tool

The fastest path is the generated command at respira.press/dashboard/mcp, which fills in your site and key for you. Manual configs below.

<details> <summary><b>Claude Code</b></summary>

claude mcp add respira-wordpress -- npx -y @respira/wordpress-mcp-server

</details> <details> <summary><b>Claude Desktop</b></summary>

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{
  "mcpServers": {
    "respira-wordpress": {
      "command": "npx",
      "args": ["-y", "@respira/wordpress-mcp-server"]
    }
  }
}

</details> <details> <summary><b>Cursor</b></summary>

Create .cursor/mcp.json in your project:

{
  "mcpServers": {
    "respira-wordpress": {
      "command": "npx",
      "args": ["-y", "@respira/wordpress-mcp-server"]
    }
  }
}

</details> <details> <summary><b>Codex, Windsurf, and other clients</b></summary>

Same shape as above. Codex uses TOML in ~/.codex/config.toml:

[mcp_servers.respira-wordpress]
command = "npx"
args = ["-y", "@respira/wordpress-mcp-server"]

Or let add-mcp detect your tool:

npx add-mcp "npx -y @respira/wordpress-mcp-server"

</details> <details> <summary><b>ChatGPT and remote clients</b></summary>

Respira also runs as a hosted remote MCP server with OAuth, so no local Node process is needed. Setup instructions per client are at respira.press/mcp.

</details>

3. Add your site

Run the wizard:

npx @respira/wordpress-mcp-server --setup

Or write ~/.respira/config.json yourself:

{
  "sites": [
    {
      "id": "my-site",
      "name": "My WordPress Site",
      "url": "https://yoursite.com",
      "apiKey": "resp…[redacted]",
      "default": true
    }
  ]
}

Restart your AI tool and start editing.

Hitting a client tool limit?

Some MCP clients cap the number of active tools, often at 100. Respira advertises far more than that, so add enabledTools to your config and only those appear in the listing:

{
  "sites": [{ "...": "..." }],
  "preferences": {
    "enabledTools": [
      "respira_read_page",
      "respira_update_page",
      "respira_list_pages",
      "respira_find_element",
      "respira_update_element",
      "respira_build_page",
      "respira_get_site_context",
      "respira_get_builder_info"
    ]
  }
}

Site management tools (respira_list_sites, respira_switch_site, respira_get_active_site) are always included. Unlisted tools still work if called directly. The filter only controls what is advertised.

On top of that, the server filters the tool list by what your site actually runs. A Divi site with no WooCommerce does not see the commerce tools. Detection fails open: if it cannot tell, you get the full list.

---

19 supported page builders

level is Respira's write depth, not the builder's quality.

| Builder | Level | Notes | |---|---|---| | Bricks | Deep | Global classes, theme styles, ACSS, components, query loops, BEM linting | | Elementor | Full | Native API, runtime control registry | | Divi | Full | Divi 4 and Divi 5, 40+ module definitions on Divi 5 | | Oxygen | Full | Classic and Oxygen 6 | | Gutenberg | Full | Block registry, FSE templates, patterns, navigation | | Flatsome | Full | Round-trip shortcode editing, 55-element intelligence | | Beaver Builder | Smart | Tree utility, static schemas | | Breakdance | Smart | Tree utility, static schemas | | Brizy | Smart | Tree utility | | WPBakery | Smart | Tree utility | | Spectra | Smart | Block target | | Kadence Blocks | Smart | Block target | | GenerateBlocks | Smart | Block target | | GreenShift | Smart | Block target | | Visual Composer | Smart | Limited write | | Thrive Architect | Smart | Text edits | | SeedProd | Smart | Audit only | | YOOtheme Pro | Full | Layouts read and written in YOOtheme's own format, saved through its builder | | Avada | Full | Avada Builder shortcodes, global palette and typography, Layouts and Library (plugin 9.2.6+) |

Mixed-builder sites are handled per page, not per site.

---

What the tools cover

The full reference lives in the docs. The families:

| Family | What it does | |---|---| | Pages, posts, custom posts | Read and write with builder-aware payloads, outlines, duplicates, translations | | Element operations | Find, update, move, duplicate, reorder, remove single elements by ID, type, class, or content text | | Page building | respira_build_page from a declarative structure, plus one-line widget shortcuts (heading, button, image, form, slider, pricing table, and more) | | Conversion | HTML to native builder with CSS extraction, responsive mapping, and a fidelity score. Figma to Bricks, Divi, Elementor, or Gutenberg via the bundled skills | | Design directions | Save, apply, activate, export a site-wide art direction. Preview before commit, apply the same direction to another site | | Design tokens | Create, update, import DTCG tokens, sync a design system into the theme | | Site memory | respira_remember, respira_forget, respira_list_memory. Facts about the site that survive between agent sessions | | Playbooks | Named, reusable procedures an agent can create, fetch, and run | | Snapshots | Automatic before every write, diff two snapshots, restore any of them | | Analysis | SEO, AEO, readability, RankMath, structured data, images, Core Web Vitals, PageSpeed | | SEO plugins | Title, description, focus keyword, canonical and robots written into Yoast SEO, Rank Math, SEOPress or All in One SEO 4 in that plugin's own fields, and read back. Yoast term SEO and Search Appearance tools | | Updates and backups | List pending updates and install only the versions a person saw. Guarded plugin update: a fresh backup through Duplicator, BackWPup or UpdraftPlus first, four health checks after, the previous version put back from wordpress.org if one fails, and a receipt | | Builder migrations | 16 free migration skills, for example Elementor to Bricks, Divi to Bricks, WPBakery to Gutenberg | | Access control | Access profiles (Everything, Content, Observe for read only), per-tool switches, and Publish only keys limited to drafts and SEO fields. They hold on every connection | | Accessibility | Scan a page, list scans, apply fixes | | Security | Security audit, validation, core hardening, debug log reading | | Theme and templates | FSE templates, template parts, patterns, navigation, theme builder templates, theme file read and write | | Site structure | Custom post types, taxonomies, ACF field groups, menus, mega menus, terms | | Media | Upload, sideload from URL, batch metadata updates, Openverse stock image search with auto-attribution | | Bulk operations | Up to 100 pages per call, with mandatory snapshots | | Multi-site | List, switch, and act on many sites from one config | | WooCommerce | Store tools in the paid add-on: catalog, pricing, inventory, orders, storefront design |

All tools use respira_* names. The legacy wordpress_* aliases are deprecated and will be removed.

What the numbers mean

The current counts are on the live tools catalog, counted from the code