Respira WordPress MCP

io.github.webmycPublished by GitHub account webmycv8.7.7Updated Nov 7, 2026

AI-native WordPress editing across 19 page builders. 283 tools, 387 with WooCommerce. Safe writes.

VerifiedSTDIODesktop onlyDeveloper ToolsBusiness & Commerce

Overview

AI-generated overview

Local MCP server that lets an assistant edit WordPress sites across 19 page builders, with 283 tools (387 with WooCommerce).

What you can do
  • Edit WordPress content and pages across 19 supported page builders
  • Use a large tool set (283 tools, 387 with WooCommerce) for site editing tasks
  • Perform writes described as safe
  • Work with either a single site or a multi-site configuration
When to use it
Useful when you want an assistant to make structured edits to WordPress sites and pages, including builder-based layouts, rather than only drafting text. Consider it if you manage one or several WordPress sites and want those changes driven from a local MCP client.
Requirements
Runs as a local stdio process from the npm package @respira/wordpress-mcp-server, so Node.js is needed. Configuration comes from either RESPIRA_CONFIG_B64 (base64 multi-site config) or RESPIRA_CONFIG_FILE (path to a config file), or from the single-site pair WORDPRESS_URL and WORDPRESS_API_KEY. Desktop client only; no web-hosted option.
Before you install
Requires secrets: RESPIRA_CONFIG_B64 or WORDPRESS_API_KEY, which grant editing access to your WordPress sites. The server can write to site content, so review changes before they go live. The multi-site config may contain credentials for several sites. No tool list is published, so verify exactly which write operations are exposed before installing.

Installation

In SourceWeft

  1. Open Respira WordPress MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the server did not start.

Version history

45
  1. v8.7.7LatestNov 7, 2026
  2. v8.7.6Nov 5, 2026
  3. v8.7.5Nov 4, 2026
  4. v8.7.3Nov 3, 2026
  5. v8.7.2Nov 1, 2026
  6. v8.7.1Oct 30, 2026
  7. v8.7.0Oct 30, 2026
  8. v8.6.9Oct 21, 2026
  9. v8.6.8Oct 19, 2026
  10. v8.6.7Oct 19, 2026
  11. v8.6.6Oct 18, 2026
  12. v8.6.4Oct 18, 2026
  13. v8.6.3Oct 18, 2026
  14. v8.6.2Oct 15, 2026
  15. v8.6.1Oct 15, 2026
  16. v8.6.0Oct 15, 2026
  17. v8.5.0Oct 13, 2026
  18. v8.4.19Oct 9, 2026
  19. v8.4.18Oct 8, 2026
  20. v8.4.17Oct 7, 2026
  21. v8.4.16Oct 4, 2026
  22. v8.4.15Oct 3, 2026
  23. v8.4.14Oct 2, 2026
  24. v8.4.11Oct 2, 2026
  25. v8.4.10Oct 1, 2026
  26. v8.4.8Sep 30, 2026
  27. v8.4.7Sep 30, 2026
  28. v8.4.6Sep 29, 2026
  29. v8.4.5Sep 29, 2026
  30. v8.4.4Sep 29, 2026
  31. v8.4.3Sep 27, 2026
  32. v8.4.1Sep 27, 2026
  33. v8.3.39Sep 25, 2026
  34. v8.3.38Sep 24, 2026
  35. v8.3.37Sep 24, 2026
  36. v8.3.36Sep 24, 2026
  37. v8.3.35Sep 23, 2026
  38. v8.3.34Sep 22, 2026
  39. v8.3.33Sep 22, 2026
  40. v8.3.32Sep 20, 2026
  41. v8.3.31Sep 19, 2026
  42. v8.3.28Sep 19, 2026
  43. v8.3.27Sep 18, 2026
  44. v8.3.26Sep 17, 2026
  45. v8.3.25Sep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.