Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.
WordPress MCP
概览
作者提供的说明(英文原文)
Talk to your WordPress site: content, SEO, WooCommerce, page builders, media and speed, with undo.
PopNx MCP 的三大支柱
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
- 用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
- 我们的基础检查i1 项中通过 1 项依据公开信息检查;尚未扫描代码
- 使用情况i尚未统计★ –
它能帮你做什么
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
- 连接方式: 在云端运行
- 传输方式: Streamable HTTP
- 分类: 网店与支付
- 你需要填写:Authorization
安装
选择你使用的 AI 应用,然后复制设置。
安装之前
- 基础检查:1 项中通过 1 项
- 在作者的服务器上运行:你向它提出的内容会经过他们的服务器。
- 需要你自己填写:
Authorization
标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
- 在云端运行无需安装任何东西,通过互联网连接
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
在终端中运行这条命令
claude mcp add --transport http wordpress 'https://{site}/wp-json/wp-mcp/v1/mcp' --header 'Authorization: your-value'运行前请先填写空着的值。
地址中有只有你知道的 {…} 部分(例如你的账户),请复制后自行填写。
或者自己复制设置
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"wordpress": {
"url": "https://{site}/wp-json/wp-mcp/v1/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
地址中有只有你知道的 {…} 部分(例如你的账户),请复制后自行填写。
或者自己复制设置
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"wordpress": {
"type": "http",
"url": "https://{site}/wp-json/wp-mcp/v1/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
你的选择通过 Cookie 保存在这台设备上,无需账户。
需要你填写的值
Authorization机密 HTTP header"Bearer " followed by a key from WordPress MCP settings. Leave empty to sign in with WordPress (OAuth) instead.
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它能做什么
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
- ✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 konkomaji 验证,该账户拥有此仓库
- … 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
- … 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
- – 不适用
端点有响应
这个地址需要填入你自己的账户信息,所以我们无法替你检查
- – 不适用
使用 OAuth 登录
这个地址需要填入你自己的账户信息,所以我们无法替你检查
- … 尚未检查
工具描述中没有隐藏指令
尚未检查;我们会在检查端点时读取工具列表
与“网店与支付”中的其他服务器比较i
- 星标数多于此分类中其他 1754 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 1754 个服务器的 43% 更新
- 基础检查结果等于或优于此分类中其他 1754 个服务器的 100%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
WordPress MCP 安全吗?
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
你需要填写:Authorization
它在我的电脑上运行还是在云端?
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
它还在维护吗?
GitHub 仓库最后更新于–,最新版本(2.0.0)于44天前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
有什么可以替代它?
同一分类中有:Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce
替代选择
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Stripe MCP
MCP server integrating with Stripe - tools for customers, products, payments, and more.
MCP Cn Commerce
8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
WordPress MCP
Turn any WordPress site into a remote MCP server that any AI assistant can read, see, and work on directly, with an undo button. Engine-agnostic SEO (Yoast / Rank Math) · AEO/GEO (JSON-LD, llms.txt, robots, redirects, IndexNow) · complete WooCommerce store operations · page-builder aware editing · site speed auditing and optimisation · live Search Console / GA4 / PageSpeed, all over one authenticated endpoint.
Works with every AI client that speaks MCP
Claude
ChatGPT
Codex
Gemini CLI
Cursor
VS Code
Windsurf
Zed
Cline
Any MCP client
### 🔌 One endpoint, every AI client
WordPress MCP speaks the open Model Context Protocol over standard Streamable HTTP. It isn't tied to any one AI vendor. Install it on a client site and connect whichever assistant you or your team use: Claude, ChatGPT, Codex, Gemini, Cursor, Copilot, or all of them at once. The settings screen generates a ready-to-paste config for each one. The agent can then *see* the real site and *implement* changes itself. No copy-paste, no second OAuth, no guessing which SEO plugin the client runs.
Table of contents
- What it does
- Quick start
- Connect your AI client
- Prompts, resources, search and fetch
- Sign in with WordPress (OAuth)
- Teams, clients and approvals
- Health checks and the connection test
- WP-CLI
- Structured output and live progress
- MCP Registry
- Who it's for
- Why it exists
- What makes it different
- Architecture
- Request lifecycle (the wire)
- Safety: dry run, undo, audit
- Error handling
- Capability model
- Tool catalogue (165)
- Media and images
- Page-builder editing
- Commerce operations
- Engine-agnostic SEO layer
- Technical SEO: links, sitemaps, IndexNow
- AEO / GEO layer
- Performance layer
- Editing WordPress from a coding agent
- Google Site Kit bridge
- Security model
- Protocol compliance
- Workflow: how an agency uses it
- Extending
- Release history
- License
What it does
One plugin, one endpoint, 165 typed tools, plus ready-made prompts and browsable resources. Any MCP client connects once per site and can then do the whole job rather than describe it:
| 📊 Read the real site | What is published, which SEO engine runs, what schema exists, what Search Console actually reports, what is slow, what is out of stock. |
| 👁️ Look at the images | get_image_bytes returns a picture, not a filename, so alt text and product copy come from what is in the photograph. |
| ✍️ Write to the live site | Meta through whatever SEO plugin the client runs, JSON-LD, posts, products, prices, stock, menus, widgets, theme files. |
| 🧩 Edit builder pages safely | Elementor, Gutenberg, Divi and WPBakery pages are edited in their own data structure, not by flattening post_content. |
| 🛒 Run the store | Catalogue, variations, images, bulk repricing, scheduled sales, inventory and coupons. Orders and customer data sit behind their own switch. |
| 🚀 Make the site faster | Audit, apply reversible front-end fixes, clean the database, and prove the change with real Core Web Vitals. |
| ↩️ Take it all back | Writes are journalled. Every change returns an operation_id; one call reverses it. |
Quick start
- Upload the ZIP from Releases via Plugins → Add New → Upload Plugin, or copy the folder to
wp-content/plugins/wordpress-mcp/. - Activate WordPress MCP.
- Open WordPress MCP in the admin menu. Under Connect an AI client, pick your client and copy the snippet. The site's real endpoint and key are already filled in. Claude and ChatGPT need only the URL: you sign in with WordPress when they ask.
- Click Test connection to confirm AI clients can get through. It catches stripped headers, firewalls and caches.
- Toggle the capability groups you need. The defaults are safe. To give someone else access, create a connection key with a preset instead of sharing yours.
Then ask for something real:
*"Audit this site's SEO, show me the ten worst pages, and fix the missing meta descriptions."*
Requires WordPress 5.6+ and PHP 7.4+. WooCommerce and Google Site Kit are optional. Their tools appear only when those plugins are active.
Connect your AI client
| Client | Connects with | Prompts | Resources | Notes |
|---|---|---|---|---|
| Claude Code | claude mcp add + Bearer header | ✅ /mcp__… | ✅ @ | Best for dev work; files + builders |
| Claude web & desktop | Custom connector: sign in with WordPress, or URL with ?key= | ✅ | ✅ | OAuth sign-in built in |
| ChatGPT | Developer mode: OAuth sign-in, or URL with ?key= | No | No | Write tools ask for confirmation; search/fetch built in |
| OpenAI Codex | codex mcp add / config.toml | No | No | CLI and IDE extension share the config |
| Gemini CLI | gemini mcp add / httpUrl | ✅ slash commands | No | Use httpUrl, not url |
| Cursor | mcp.json | ✅ | ✅ | |
| VS Code / Copilot | .vscode/mcp.json | ✅ | ✅ | Key held in VS Code's secret storage |
| Windsurf | mcp_config.json | No | No | 100-tool cap; use ?groups= |
| Zed · Cline · Continue · LM Studio | Config file | varies | varies | |
| Anything else | Streamable HTTP, or mcp-remote for stdio | varies | varies | Any spec-compliant client |
Prompt and resource support depends on the client and changes often. Tools work in every client above.
Every client connects to the same endpoint:
https://client.example.com/wp-json/wp-mcp/v1/mcp
A client can present the key in any of these ways:
| How | When to use it |
|---|---|
Authorization: Bearer header | Any client with a header field. This is the preferred option because it keeps the key out of URLs and logs. |
X-API-Key: header | Clients whose UI has an "API key header" box. |
?key= on the URL | Clients that only accept a URL: Claude web/desktop connectors, ChatGPT developer mode, Continue. |
| Sign in with WordPress (OAuth) | Clients that support MCP sign-in (Claude, ChatGPT and others). Paste the plain URL; no key needed. See below. |
The snippets below use my-site and YOUR_KEY. The settings screen generates them with your real values.
Claude Code
claude mcp add --transport http my-site https://client.example.com/wp-json/wp-mcp/v1/mcp \
--header "Authorization: Bea
只显示了开头部分;其余内容请在仓库中阅读