AgentStack
MCP verified MIT Self-run

Mcp Wordpress Setup

mcp-arturseo-geo-mcp-wordpress-setup · by arturseo-geo

Step-by-step setup guide for the WordPress MCP server with Claude Code — Application Passwords, REST API config, critical bin entry point bug workaround (v3.1.13), and verified .mcp.json configuration. By TheGEOLab.net

No reviews yet
0 installs
13 views
0.0% view→install

Install

$ agentstack add mcp-arturseo-geo-mcp-wordpress-setup

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Mcp Wordpress Setup? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

WordPress MCP Server Setup for Claude Code

> Built by Artur Ferreira @ The GEO Lab · 𝕏 @TheGEO\Lab · LinkedIn · Reddit

[](https://github.com/arturseo-geo/mcp-wordpress-setup/blob/main/CONTRIBUTING.md)

Step-by-step guide to configure the mcp-wordpress MCP server with Claude Code, giving Claude full access to manage your WordPress site through the REST API — posts, pages, media, SEO, caching, and more.

Includes a critical workaround for a bug in mcp-wordpress v3.1.13 where the published bin entry point fails to start.

Who This Is For

  • Claude Code users who want to manage WordPress from their CLI
  • WordPress developers setting up MCP for the first time
  • Anyone who tried mcp-wordpress and got a silent failure (the bin bug)

What This Covers

  • Prerequisites — Node.js version requirements, Claude Code installation
  • Application Password creation — step-by-step WordPress admin walkthrough
  • .mcp.json configuration — verified working config with correct paths
  • Critical bin bug workaround — why mcp-wordpress binary fails silently in v3.1.13 and how to point to dist/index.js instead
  • Path discovery — commands to find your Node.js binary and mcp-wordpress install location
  • Verification — how to confirm the MCP server is running
  • Production-tested — patterns used in production at thegeolab.net

Quick Start

# 1. Install mcp-wordpress
npm install -g mcp-wordpress

# 2. Create Application Password in WordPress admin
#    Users > Profile > Application Passwords

# 3. Add to ~/.mcp.json (IMPORTANT: use dist/index.js, not the bin script)
{
  "mcpServers": {
    "wordpress": {
      "command": "/path/to/node",
      "args": ["/path/to/node_modules/mcp-wordpress/dist/index.js"],
      "env": {
        "WORDPRESS_SITE_URL": "https://your-site.com",
        "WORDPRESS_USERNAME": "your-username",
        "WORDPRESS_APP_PASSWORD": "xxxx xxxx xxxx xxxx xxxx xxxx"
      }
    }
  }
}
# 4. Find your paths
which node                                          # Node binary
echo "$(npm root -g)/mcp-wordpress/dist/index.js"  # mcp-wordpress entry point

The Bin Bug (v3.1.13)

The published binary (bin/mcp-wordpress.js) contains an isMainModule check that fails when Node invokes the file through the bin symlink. As a result, calling mcp-wordpress directly will silently do nothing — main() never executes.

Fix: Point your MCP config to dist/index.js instead of the binary. This is reflected in the config above.

Related Repos


Built and maintained by Artur Ferreira · thegeolab.net · [MIT License](LICENSE)

Source & license

This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.