Buy a domain, provision hosting, deploy a site, and set its DNS — one official server covering the whole chain, now through three search-and-execute tools.
WordPress
Publish and manage a WordPress site from an agent over the REST API — posts, pages, media, plugins, themes.
Quick answer
What it does
Wraps the WordPress REST API: `wp_create_post` / `wp_update_post` / `wp_delete_post`, the matching page family, `wp_list_media` and media metadata, taxonomy CRUD, comment moderation, `wp_list_plugins` and activate/deactivate, theme listing and activation, and `wp_get_settings` / `wp_update_settings`.
Best for
- Drafting and publishing posts and pages
- Managing several WordPress sites from one server
- Media library metadata cleanup
- Comment moderation at volume
Not for
- Teams that require a vendor-maintained server
- Page-builder layouts (Elementor, Divi) that live outside the REST API
Source: top-mcps.com/mcp/wordpress — verified Sep 2026
Setup recipe
Pick your client, then follow the three steps.
- 1
Install
claude_desktop_config.jsonjson{ "mcpServers": { "wordpress": { "command": "npx", "args": [ "-y", "@cavort-it-systems/wordpress-mcp" ], "env": { "WORDPRESS_SITE_URL": "${WORDPRESS_SITE_URL}", "WORDPRESS_USERNAME": "${WORDPRESS_USERNAME}", "WORDPRESS_PASSWORD": "${WORDPRESS_PASSWORD}" } } } }Paste under mcpServers. Fully quit and reopen Claude after editing.
CLI or .mcp.jsonshell# export WORDPRESS_SITE_URL=https://example.com # export WORDPRESS_USERNAME=admin # export WORDPRESS_PASSWORD=xxxx xxxx xxxx xxxx claude mcp add wordpress -- npx -y @cavort-it-systems/wordpress-mcpRun from your repo. Commit .mcp.json to share with your team.
.cursor/mcp.jsonjson{ "mcpServers": { "wordpress": { "command": "npx", "args": [ "-y", "@cavort-it-systems/wordpress-mcp" ], "env": { "WORDPRESS_SITE_URL": "${WORDPRESS_SITE_URL}", "WORDPRESS_USERNAME": "${WORDPRESS_USERNAME}", "WORDPRESS_PASSWORD": "${WORDPRESS_PASSWORD}" } } } }Global path: ~/.cursor/mcp.json. Reload window after editing.
.vscode/mcp.jsonjsonc{ "servers": { "wordpress": { "command": "npx", "args": [ "-y", "@cavort-it-systems/wordpress-mcp" ], "env": { "WORDPRESS_SITE_URL": "${WORDPRESS_SITE_URL}", "WORDPRESS_USERNAME": "${WORDPRESS_USERNAME}", "WORDPRESS_PASSWORD": "${WORDPRESS_PASSWORD}" } } } }VS Code uses the "servers" key (not "mcpServers").
~/.codeium/windsurf/mcp_config.jsonjson{ "mcpServers": { "wordpress": { "command": "npx", "args": [ "-y", "@cavort-it-systems/wordpress-mcp" ], "env": { "WORDPRESS_SITE_URL": "${WORDPRESS_SITE_URL}", "WORDPRESS_USERNAME": "${WORDPRESS_USERNAME}", "WORDPRESS_PASSWORD": "${WORDPRESS_PASSWORD}" } } } }Open via Cascade → hammer icon → Configure.
cline_mcp_settings.jsonjson{ "mcpServers": { "wordpress": { "command": "npx", "args": [ "-y", "@cavort-it-systems/wordpress-mcp" ], "env": { "WORDPRESS_SITE_URL": "${WORDPRESS_SITE_URL}", "WORDPRESS_USERNAME": "${WORDPRESS_USERNAME}", "WORDPRESS_PASSWORD": "${WORDPRESS_PASSWORD}" } } } }Open via the Cline sidebar → MCP Servers → Edit.
~/.continue/config.jsonjson{ "experimental": { "modelContextProtocolServers": [ { "transport": { "type": "stdio", "command": "npx", "args": [ "-y", "@cavort-it-systems/wordpress-mcp" ], "env": { "WORDPRESS_SITE_URL": "${WORDPRESS_SITE_URL}", "WORDPRESS_USERNAME": "${WORDPRESS_USERNAME}", "WORDPRESS_PASSWORD": "${WORDPRESS_PASSWORD}" } } } ] } }Continue uses modelContextProtocolServers with a transport block.
~/.codex/config.tomlshell# ~/.codex/config.toml [mcp_servers.wordpress] command = "npx" args = [ "-y", "@cavort-it-systems/wordpress-mcp", ] env = { WORDPRESS_SITE_URL = "${WORDPRESS_SITE_URL}", WORDPRESS_USERNAME = "${WORDPRESS_USERNAME}", WORDPRESS_PASSWORD = "${WORDPRESS_PASSWORD}" }Codex uses TOML. Each server is a [mcp_servers.<name>] subtable.
~/.config/zed/settings.jsonjsonc{ "context_servers": { "wordpress": { "command": { "path": "npx", "args": [ "-y", "@cavort-it-systems/wordpress-mcp" ] }, "env": { "WORDPRESS_SITE_URL": "${WORDPRESS_SITE_URL}", "WORDPRESS_USERNAME": "${WORDPRESS_USERNAME}", "WORDPRESS_PASSWORD": "${WORDPRESS_PASSWORD}" } } } }Zed calls them "context_servers". Settings live-reload on save.
ChatGPT → Apps directorynoneWordPress doesn't ship a hosted HTTPS endpoint today. ChatGPT supports remote MCP servers only — to use this server in ChatGPT you'll need to deploy it to a public HTTPS URL first (e.g. via Cloudflare Workers or Vercel) or wait for an official remote build.
- 2
Set required secrets
Set
WORDPRESS_SITE_URL,WORDPRESS_USERNAME,WORDPRESS_PASSWORDin your shell environment before launching your MCP client. - 3
Try a minimum working prompt
Minimum working prompt pending verification. Try any prompt from the MCP’s README once installed.
Tools & permissions
Showing 12 of 200 tools the server reported. The rest are real, just not listed here.
| Tool | Description | Args | Side effects |
|---|---|---|---|
list_sites | List the WordPress sites this server manages. Every other tool needs one of these ids. | — | Read |
wp_list_posts | List posts with optional filters. | — | Read |
wp_create_post | Create a post. | — | Write |
wp_update_post | Update an existing post. | — | Write |
wp_delete_post | Trash a post, or delete permanently with force=true. | — | Write |
wp_create_page | Create a page. | — | Write |
wp_list_media | List media library items. | — | Read |
wp_update_media | Update media title, alt text and caption. | — | Write |
wp_list_plugins | List installed plugins. | — | Read |
wp_activate_plugin | Activate an installed plugin (routes via the companion plugin). | — | Write |
wp_activate_theme | Switch the active theme. | — | Write |
wp_update_settings | Update site title, tagline, timezone and date format. | — | Write |
Security & scope
- Access scope
- Read + write
- Sandbox
- No sandbox. Point it at a staging site first — this server can change the active theme on a live site.
- Gotchas
- An application password inherits the WordPress user's full capabilities. Create a dedicated user with the narrowest role that still does the job rather than using an administrator.
- `wp_activate_theme` and the plugin activate/deactivate tools change what visitors see immediately, with no preview and no undo.
- `wp_delete_post` trashes by default but takes `force=true` for a permanent delete. Make sure the agent never has a reason to pass it.
Agent prompt pack
— copy into Claude, Cursor, or ChatGPT.Recommend the best MCP servers for [task: e.g. website builders work] in [client: Claude]. Constraints: - Prefer tools that are [official | open-source | read-only] — pick what matters for my use case. - Exclude MCPs that require [e.g. a paid plan, OAuth-only flows, remote-only transport]. - Return at most 3 picks, ranked. For each pick include: 1. One-sentence rationale. 2. The ready-to-paste install snippet for my client. 3. Any required secrets I need to create before installing. Cross-check the top-mcps.com listing: https://top-mcps.com/top-mcps-for-website-builders
Compare WordPress MCP vs [Webflow MCP] for the following job: [describe the job, e.g. "let an agent create GitHub issues on bug triage"]. Judge them on: - Setup time and complexity (what a new user hits first). - Auth model (none / API key / OAuth 2.1) and credential risk. - Transport (stdio / Streamable HTTP / SSE) and where the server runs. - Required secrets and the blast radius if they leak. - Operational risk in an unattended agent loop. - Which one is "good enough" for a weekend prototype vs. production. End with one sentence: which should I pick for my scenario, which is: [my scenario]. References: - https://top-mcps.com/mcp/wordpress - top-mcps.com listing for Webflow
Install the WordPress MCP server for my [client: Claude] at the default config path for that client. Use the exact install snippet published at https://top-mcps.com/mcp/wordpress (fetch https://top-mcps.com/mcp/wordpress.json for the canonical server.json if you can read URLs). Before finishing: 1. Create the required secrets (WORDPRESS_SITE_URL, WORDPRESS_USERNAME, WORDPRESS_PASSWORD) and put them in the appropriate env block — do not hard-code them. 2. Restart or reload the client so it picks up the new server. 3. Verify the server is connected (green / running state) and at least one tool is listed. 4. If anything fails, read the client's MCP logs and report the exact error — do not silently retry. Confirm when done and list the tools the server now exposes.
Frequently asked questions
What changed
— 1 update tracked.Refreshed install snippets and fact sheet; verified for 2026.
More Website Builders MCPs
Other tools in the same category worth evaluating.
Edit a live Webflow site from an agent — CMS collections, pages, and the Designer canvas over OAuth.
Model, write and publish structured content from an agent — 73 tools across entries, assets and content types.
Compared with WordPress
Side-by-side breakdowns for the choices people most often weigh against this MCP.
Exploring Top MCPs for Website Builders and CMS? See all Website Builders MCPs →