Respira WordPress MCP Server

A catalog of 319 MCP tools and 277 WordPress Abilities across 17 page builders. The AI infrastructure layer for WordPress.
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.

Website • Docs • Plugin • MCP setup • Skills • Support

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.

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.

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

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

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

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

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

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": "respira_your-api-key",
      "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.

17 supported page builders

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

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

What the tools cover

The full reference lives in the docs. The families: