Allows an AI client to manage WordPress content including posts, pages, media, and comments through a secure, local interface.
Also known as crunchtools/mcp-wordpress, mcp-wordpress, mcp-wordpress-crunchtools
- Stars
- 1
- Tools
- 33
- Downloads, 30 days
- 1,114
- Latest version
- 0.4.1
- Last commit
- Nov 14, 2026
- License
- AGPL-3.0
What is WordPress MCP?
WordPress allows an AI client to manage WordPress content including posts, pages, media, and comments through a secure, local interface. It exposes 33 tools, such as wordpress_get_site_info, wordpress_test_connection, wordpress_list_posts.
Summary generated from the project's README
About WordPress MCP server
Managing WordPress content through an AI client is what this MCP server enables for developers and publishers. It provides a secure, local interface to interact with your website using 33 specialized tools that cover posts, pages, media, and comments. By running locally via stdio, your credentials remain on your machine and are never sent to third-party services.
Users can set up the server using uvx, pip, or a containerized approach with Podman. To connect to a site, you must provide the WORDPRESS_URL, WORDPRESS_USERNAME, and a WORDPRESS_APP_PASSWORD via environment variables. The server is designed with security in mind, featuring SSRF prevention, input validation, and credential protection to ensure safe interactions with your WordPress REST API.
This tool stands out by offering granular editing capabilities. Instead of resending entire posts, the edit_post and edit_page tools allow for replacing specific text within the source. It also supports advanced workflows like scheduled publishing, managing revisions, and moderating comments through specific tools like wordpress_moderate_comment.
What you can do with it
- 1Perform targeted text editsYou can instruct an AI to update specific sections of a page without rewriting the entire document.
- 2Moderate site discussionsAn AI can filter through pending comments to approve or spam them.
Written from the project's README. Every use case is checked against a quote from it.
How to install WordPress MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall WordPress MCP in Claude Code
$ claude mcp add mcp-wordpress -- uvx mcp-wordpress-crunchtoolsInstall WordPress MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp-wordpress": {
"command": "uvx",
"args": [
"mcp-wordpress-crunchtools"
]
}
}
}Install WordPress MCP in VS Code
.vscode/mcp.json
{
"servers": {
"mcp-wordpress": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-wordpress-crunchtools"
]
}
}
}Install WordPress MCP in VS Code CLI
$ code --add-mcp '{"name":"mcp-wordpress","type":"stdio","command":"uvx","args":["mcp-wordpress-crunchtools"]}'Install WordPress MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mcp-wordpress": {
"command": "uvx",
"args": [
"mcp-wordpress-crunchtools"
]
}
}
}Install WordPress MCP in Codex
$ codex mcp add mcp-wordpress -- uvx mcp-wordpress-crunchtoolsInstall WordPress MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp-wordpress] command = "uvx" args = ["mcp-wordpress-crunchtools"]
Install WordPress MCP in Gemini CLI
$ gemini mcp add -s user mcp-wordpress uvx -- mcp-wordpress-crunchtoolsInstall WordPress MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp-wordpress": {
"command": "uvx",
"args": [
"mcp-wordpress-crunchtools"
]
}
}
}WordPress MCP tools 33
Detected from the READMEwordpress_get_site_infowordpress_test_connectionwordpress_list_postswordpress_get_postwordpress_search_postswordpress_create_postwordpress_update_postwordpress_edit_postwordpress_edit_draftwordpress_delete_postwordpress_list_revisionswordpress_get_revision
| wordpress_get_site_info | — | |
| wordpress_test_connection | — | |
| wordpress_list_posts | — | |
| wordpress_get_post | — | |
| wordpress_search_posts | — | |
| wordpress_create_post | — | |
| wordpress_update_post | — | |
| wordpress_edit_post | — | |
| wordpress_edit_draft | — | |
| wordpress_delete_post | — | |
| wordpress_list_revisions | — | |
| wordpress_get_revision | — |
Show all 33 toolsShow fewer tools
wordpress_list_categorieswordpress_list_tagswordpress_list_pageswordpress_get_pagewordpress_create_pagewordpress_update_pagewordpress_edit_pagewordpress_delete_pagewordpress_list_page_revisionswordpress_list_mediawordpress_get_mediawordpress_upload_mediawordpress_update_mediawordpress_delete_mediawordpress_get_media_urlwordpress_list_commentswordpress_get_commentwordpress_create_commentwordpress_update_commentwordpress_delete_commentwordpress_moderate_comment
| wordpress_list_categories | — | |
| wordpress_list_tags | — | |
| wordpress_list_pages | — | |
| wordpress_get_page | — | |
| wordpress_create_page | — | |
| wordpress_update_page | — | |
| wordpress_edit_page | — | |
| wordpress_delete_page | — | |
| wordpress_list_page_revisions | — | |
| wordpress_list_media | — | |
| wordpress_get_media | — | |
| wordpress_upload_media | — | |
| wordpress_update_media | — | |
| wordpress_delete_media | — | |
| wordpress_get_media_url | — | |
| wordpress_list_comments | — | |
| wordpress_get_comment | — | |
| wordpress_create_comment | — | |
| wordpress_update_comment | — | |
| wordpress_delete_comment | — | |
| wordpress_moderate_comment | — |
Automated checks
Ran Nov 13, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablecrunchtools/mcp-wordpress is public and reachablegithub.com/crunchtools/mcp-wordpress ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Sigstore attestation for mcp-wordpress-crunchtoolspypi.org/project/mcp-wordpress-crunchtools/ ↗Pass
- Open source license (OSI)AGPL-3.0spdx.org/licenses/AGPL-3.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-12github.com/crunchtools/mcp-wordpress ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from mcp-wordpress-crunchtoolsPass
- No critical advisory in the package or its dependencies65 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model33 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubMCP 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 - 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
- 33 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:zflag sets a sharedcontainer_file_tcontext 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
- Log in to WordPress admin
- Go to Users → Profile
- Scroll to Application Passwords
- Enter a name (e.g., "MCP Server") and click Add New
- 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 mcp add mcp-wordpress-crunchtools \
--env WORDPRESS_URL=https://example.com \
--env WORDPRESS_USERNAME=admin \
--env WORDPRESS_APP_PASSWORD="xxxx xxxx xxxx xxxx" \
-- podman run -i --rm \
-v ~/.local/share/mcp-uploads-downloads:/tmp/mcp-uploads:z \
-e WORDPRESS_URL \
-e WORDPRESS_USERNAME \
-e WORDPRESS_APP_PASSWORD \
quay.io/crunchtools/mcp-wordpress
Available Tools
Site Tools
| Tool | Description |
|---|---|
wordpress_get_site_info |
Get site title, description, URL, timezone |
wordpress_test_connection |
Verify API credentials work |
Editing Model
Reads return the source the editor saved (context=edit), never the rendered page, so what
an agent reads is safe to write back. Changes go through the edit_* tools: the agent sends
the exact text to replace and its replacement, the server applies it to the current source,
and the post never round-trips through the agent. The post and page update and edit tools
take an optional expected_version (the version get_post or get_page returned); when
it is given, the write is refused if the item changed since. update_* refuses content that
is rendered output. edit_draft edits only draft or pending posts, so a gateway can grant
revision rights without the power to change published posts.
Post Tools
| Tool | Description |
|---|---|
wordpress_list_posts |
List posts with filtering (status, category, search) |
wordpress_get_post |
Get single post by ID with its saved source (block markup included) and version |
wordpress_search_posts |
Search posts by keyword |
wordpress_create_post |
Create new post (supports scheduling) |
wordpress_update_post |
Update existing post; refuses rendered HTML, and a stale expected_version when given |
wordpress_edit_post |
Replace text in a post's source without resending the post |
wordpress_edit_draft |
Same as edit_post, for draft or pending posts only; refuses any other status |
wordpress_delete_post |
Delete/trash a post |
wordpress_list_revisions |
List revisions for a post |
wordpress_get_revision |
Get specific revision content |
wordpress_list_categories |
List available categories |
wordpress_list_tags |
List available tags |
Page Tools
| Tool | Description |
|---|---|
wordpress_list_pages |
List pages with filtering |
wordpress_get_page |
Get single page by ID with its saved source and version |
wordpress_create_page |
Create new page |
wordpress_update_page |
Update existing page; refuses rendered HTML, and a stale expected_version when given |
wordpress_edit_page |
Replace text in a page's source without resending the page |
wordpress_delete_page |
Delete/trash a page |
wordpress_list_page_revisions |
List page revisions |
Media Tools
| Tool | Description |
|---|---|
wordpress_list_media |
List media items |
wordpress_get_media |
Get media item details |
wordpress_upload_media |
Upload file from local path |
wordpress_update_media |
Update media metadata |
wordpress_delete_media |
Delete media item |
wordpress_get_media_url |
Get public URL for media |
Comment Tools
| Tool | Description |
|---|---|
wordpress_list_comments |
List comments with filtering |
wordpress_get_comment |
Get single comment |
wordpress_create_comment |
Add a comment to a post |
wordpress_update_comment |
Update comment content/status |
wordpress_delete_comment |
Delete a comment |
wordpress_moderate_comment |
Approve, hold, spam, or trash |
Examples
Create a Draft Post
Create a new WordPress post titled "My Technical Article" with the content below. Keep it as a draft.
Schedule a Post
Update post ID 123 to publish on December 25, 2024 at 10:00 AM.
Upload an Image
Upload this image to WordPress and set the alt text to "Architecture diagram".
Find and Moderate Comments
List all comments in "hold" status and approve the legitimate ones.
Security
- Credential Protection: All credentials stored as
SecretStr, never logged - SSRF Prevention: REST API path hardcoded, cannot be overridden
- Input Validation: All inputs validated via Pydantic models
- Rate Limiting: Handles WordPress rate limits gracefully
- TLS Enforcement: All requests use HTTPS with certificate validation
- Size Limits: Response size limited to 10MB to prevent memory issues
- Timeout: All requests timeout after 30 seconds
Development
# Install dev dependencies
uv sync --all-extras
# Run tests
uv run pytest
# Run linting
uv run ruff check src tests
# Run type checking
uv run mypy src
# Format code
uv run ruff format src tests
License
AGPL-3.0-or-later
Credits
Built by crunchtools.com
WordPress MCP questions
How do I add WordPress MCP to Claude Code?
Run claude mcp add mcp-wordpress -- uvx mcp-wordpress-crunchtools in your terminal. Add --scope user to make it available in every project.
How do I add WordPress MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does WordPress MCP provide?
It exposes 33 tools, including wordpress_get_site_info, wordpress_test_connection, wordpress_list_posts, wordpress_get_post, wordpress_search_posts.
How do I set up authentication for the WordPress MCP server?
You need to create an Application Password in your WordPress admin under Users → Profile, then provide the URL, username, and password as environment variables.
Is my data sent to third-party services?
No, the server runs locally via stdio and your credentials never leave your machine.
Can I schedule posts using this server?
Yes, the server supports creating posts with scheduled publishing.