MCP WordPress CrunchTools

A secure MCP (Model Context Protocol) server for WordPress content management. Designed for developers publishing about their work.

Overview

This MCP server is designed to be:

• Secure by default - Comprehensive input validation, credential protection, and SSRF prevention
• No third-party services - Runs locally via stdio, your credentials never leave your machine
• Cross-platform - Works on Linux, macOS, and Windows
• Automatically updated - GitHub Actions monitor for CVEs and update dependencies
• Containerized - Available at quay.io/crunchtools/mcp-wordpress

Naming Convention

| Component | Name | |-----------|------| | GitHub repo | crunchtools/mcp-wordpress | | Container | quay.io/crunchtools/mcp-wordpress | | Python package (PyPI) | mcp-wordpress-crunchtools | | CLI command | mcp-wordpress-crunchtools | | Module import | mcp_wordpress_crunchtools |

Features

• 30 Tools for posts, pages, media, and comments
• Security-focused: Credentials protected, input validation, SSRF prevention
• Developer workflow: Scheduled publishing, revisions, search
• Easy integration: Works with Claude Code and other MCP clients

Installation

With uvx (recommended)

uvx mcp-wordpress-crunchtools

With pip

pip install mcp-wordpress-crunchtools
mcp-wordpress-crunchtools

With Container

# Create a shared upload directory (required before first run)
mkdir -p ~/.local/share/mcp-uploads-downloads

podman run -v ~/.local/share/mcp-uploads-downloads:/tmp/mcp-uploads:z \
  -e WORDPRESS_URL=https://example.com \
  -e WORDPRESS_USERNAME=admin \
  -e WORDPRESS_APP_PASSWORD='xxxx xxxx xxxx xxxx' \
  quay.io/crunchtools/mcp-wordpress

SELinux note: Use :z (lowercase, shared) instead of :Z (uppercase, private). MCP servers run as long-lived stdio processes. With :Z, files copied into the directory after container start won't have the container's private MCS label and will be invisible inside the container. The :z flag sets a shared container_file_t context that all containers and the host can read/write.

Tip: Use the same shared directory (~/.local/share/mcp-uploads-downloads/) across multiple MCP container servers (e.g., mcp-wordpress and mcp-gemini) so generated files are immediately available for upload without copying.

From source

git clone https://github.com/crunchtools/mcp-wordpress.git
cd mcp-wordpress
uv sync --all-extras
uv run mcp-wordpress-crunchtools

Configuration

Set these environment variables:

| Variable | Description | Example | |----------|-------------|---------| | WORDPRESS_URL | WordPress site URL | https://example.com | | WORDPRESS_USERNAME | WordPress username | admin | | WORDPRESS_APP_PASSWORD | Application password | xxxx xxxx xxxx xxxx | | MCP_UPLOAD_DIR | Upload directory inside container (optional) | /tmp/mcp-uploads (default) |

Creating an Application Password

1. Log in to WordPress admin
2. Go to Users → Profile
3. Scroll to Application Passwords
4. Enter a name (e.g., "MCP Server") and click Add New
5. Copy the generated password (shown once)

Usage with Claude Code

Using uvx (recommended)

claude mcp add mcp-wordpress-crunchtools \
    --env WORDPRESS_URL=https://example.com \
    --env WORDPRESS_USERNAME=admin \
    --env WORDPRESS_APP_PASSWORD="xxxx xxxx xxxx xxxx" \
    -- uvx mcp-wordpress-crunchtools

Using pip

pip install mcp-wordpress-crunchtools

claude mcp add mcp-wordpress-crunchtools \
    --env WORDPRESS_URL=https://example.com \
    --env WORDPRESS_USERNAME=admin \
    --env WORDPRESS_APP_PASSWORD="xxxx xxxx xxxx xxxx" \
    -- mcp-wordpress-crunchtools

Using Container

# Create a shared upload directory (required before first run)
mkdir -p ~/.local/share/mcp-uploads-downloads

claude

... [View full README on GitHub](https://github.com/crunchtools/mcp-wordpress#readme)