MCP Wordpress

Name: MCP Wordpress
Author: crunchtools

作者：crunchtools版本 0.4.1i★ –i在你的电脑上运行

注册名称io.github.crunchtools/wordpress

安装

概览

作者提供的说明（英文原文）

Secure MCP server for WordPress content management

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
注册中心没有列出需要填写的密钥。

你需要

PyPI已安装 Python 的 uv（用于 uvx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "wordpress": {
      "command": "uvx",
      "args": [
        "mcp-wordpress-crunchtools"
      ]
    }
  }
}

在终端中运行这条命令

claude mcp add wordpress -- uvx mcp-wordpress-crunchtools

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "wordpress": {
      "command": "uvx",
      "args": [
        "mcp-wordpress-crunchtools"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "wordpress": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "mcp-wordpress-crunchtools"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 crunchtools 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32461 个服务器的 0%
发布到注册中心的时间比此分类中其他 32461 个服务器的 3% 更新
基础检查结果等于或优于此分类中其他 32461 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

MCP Wordpress 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.4.1）于8个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, dotnet-mcp

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211昨天更新

安装

dotnet-mcp

作者：Skymly

MCP server for .NET symbols, XAML, source generators, and restricted workspace edit

在你的电脑上运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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 - 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 :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

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

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

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

Tool	Description
`wordpress_get_site_info`	Get site title, description, URL, timezone
`wordpress_test_connection`	Verify API credentials work