Respira WordPress MCP Server: Page Builder Editing Across 17 Builders

What this repository is

This repository is the public listing for a server that is a client of the Respira for WordPress plugin. The wrapper is MIT licensed, while the plugin is commercial and needs an API key bound to a license.

The README says most WordPress MCP servers wrap the REST API and cannot reach page builder content. Respira's plugin gives the agent the builder's own data structures, so it can find, update, move and remove elements by ID, type, class or text.

Builders and write depth

Write depth differs by builder. Bricks is marked Deep, Elementor, Divi, Oxygen, Gutenberg and Flatsome are Full, and the other 11 are Smart, meaning tree utilities or block targets. SeedProd is audit only. Mixed-builder sites are handled per page.

Safety rails for live sites

• A snapshot is taken before every write, and respira_restore_snapshot brings it back.
• Duplicate before edit keeps the original page untouched while the agent works on a copy.
• Admins switch individual tools on or off from wp-admin.
• Read-only mode lets an agent look at a site without writing.
• An activity log records every call, readable through respira_list_activity.

Who it suits

• Site owners and developers who maintain Bricks, Divi, Elementor or Gutenberg sites and want an agent to edit native content.
• Teams starting from a design handoff. Related: a Figma MCP server and Framelink.

Look elsewhere if

• You want a self-contained stack with no commercial dependency. The README says this is not it.
• You cannot install a plugin on the site, since the server does nothing useful without one.
• Your client caps active tools at 100 and you will not set enabledTools.

Use it with UiChemy

Respira converts HTML or Figma to native builder output through its own tools and bundled skills. UiChemy is a separate route: Figma to WordPress converts Figma frames into WordPress pages. Related: Lovable to Elementor. Click Get Started on uichemy.com.

Connect Respira WordPress MCP Server: Page Builder Editing Across 17 Builders to your AI client

npx -y @respira/wordpress-mcp-server

1. Install the plugin

   Download Respira for WordPress from respira.press/plugin, upload and activate it, then open Respira, API Keys and generate a key.

2. Register the server

   For Claude Code run claude mcp add respira-wordpress -- npx -y @respira/wordpress-mcp-server. Claude Desktop and Cursor use the JSON block above, and Codex uses TOML in ~/.codex/config.toml.

3. Add your site

   Run npx @respira/wordpress-mcp-server --setup, or write ~/.respira/config.json with your site URL and API key.

4. Restart and test

   Restart your AI tool, then run npx @respira/wordpress-mcp-server --test to check the connection, or --doctor for diagnostics.

5. Trim the tool list if needed

   If your client caps active tools, add preferences.enabledTools to the config so only those tools are advertised.

Client configuration

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

Endpoints and ports

What you can do with it

• Element level editingFind, update, move, duplicate, reorder and remove single elements instead of replacing the full page content.
• Declarative page buildingrespira_build_page creates a page from a structure, and one line shortcuts cover widgets such as heading, button, image, form and pricing table.
• Conversion with a fidelity scoreHTML converts to native builder output with CSS extraction and responsive mapping. Figma conversion to Bricks, Divi, Elementor or Gutenberg runs through bundled skills.
• Design directions and tokensSave, preview and apply a site wide art direction, and import DTCG design tokens into the theme.
• Site memoryrespira_remember, respira_forget and respira_list_memory keep facts about the site between agent sessions.
• Snapshots and rollbackA snapshot is taken before every mutation, two snapshots can be diffed, and any of them can be restored.
• Analysis and accessibilitySEO, AEO, readability, structured data and Core Web Vitals checks sit beside an accessibility scan with fixes and a security audit.
• Context filtered tool listThe server hides tools your site cannot use, so Bricks tools never reach an Elementor site and commerce tools need WooCommerce.

Tools it exposes

Frequently asked questions