Compared · wordpress
7 WordPress MCP servers. Which one to use.
Every WordPress server we index, with whether its source is still reachable and whether we hold a screening verdict. None currently carry a source-liveness flag.
Scope: 7 servers indexed from the MCP registry as of 2026-07-25. Servers whose authors never published to the registry are not listed here, so treat this as the registry's view rather than a complete census.
| Server | Publisher | Source | Screened | Quality | Install |
|---|---|---|---|---|---|
| Respira WordPress MCP | io.github.webmyc | no flag | REVIEW | 100 | npm @respira/wordpress-mcp-server |
| WP Agent - WordPress publishing & management with Claude | com.getwpagent | no flag | REVIEW | 95 | remote endpoint |
| WPWriter — WordPress AI Content & SEO | com.wpwriter | no flag | REVIEW | 95 | remote endpoint |
| ClearPost: WordPress SEO Agent | com.clearpostplugin | no flag | REVIEW | 85 | remote endpoint |
| Respira WordPress MCP | press.respira | no flag | REVIEW | 83 | npm @respira/wordpress-mcp-server |
| MCP Wordpress | io.github.crunchtools | no flag | REVIEW | 76 | pypi mcp-wordpress-crunchtools |
| io.github.cvrt-jh/wordpress-mcp | io.github.cvrt-jh | no flag | REVIEW | 74 | npm @cavort-it-systems/wordpress-mcp |
“Repo unreachable” means the source returned a not-found from two vantage points, which can also happen when a repository is made private or moved - see source liveness. “Screened” is the advisory verdict on the listing text, never a safety clearance; the methodology spells out what each dimension does and does not test.