原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

AlphaBridge MCP for WordPress

作者:CultureClub-dev版本 4.10.0i★ 0i在云端运行官方网站 ↗
注册名称io.github.CultureClub-dev/alphabridge-mcp

安装方法

What it does

WordPress MCP server plugin for Claude, ChatGPT and more. Reads by default, one switch to write.

  • Connects 在云端运行
  • Account or key Sign in to the service when you connect (OAuth)
  • Category 其他

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度0/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度12/1230 天内有发布或代码更新得满分
仍在响应8/8上次检查时云端端点有响应
使用分20/100

质量: 基础检查通过 5/5 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

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

用一句话让 AI 帮你安装

请帮我安装 AlphaBridge MCP for WordPress。按照 https://mcp.popnx.com/i/cultureclub-dev-alphabridge-mcp.md 操作,先把命令给我看,等我同意后再运行。

粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文

通过 5/5 项检查 · 你的提问会经过开发者的服务器(connect.alphabridge-mcp.com) · ✓ 命令已检查 2026年11月13日

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude · 约 2 分钟

不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加

  1. 打开 Claude 的 Connectors 页面

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  2. 点击“Add” → “Custom” → “Web”,填写这 2 项

    把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue

    Name · 名称AlphaBridge MCP for WordPress
    Remote MCP server URL · 地址https://connect.alphabridge-mcp.com/mcp

    在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add

  3. 在聊天中开启

    +ConnectorsAlphaBridge MCP for WordPress

  4. 试一试

    用 AlphaBridge MCP for WordPress 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 AlphaBridge MCP for WordPress,或回答中出现 AlphaBridge MCP for WordPress 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

能否连接 ChatGPT 取决于方案

完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页

  1. 在网页版 ChatGPT 打开添加 MCP 的页面

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. 填写名称和地址

    输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin

    Name · 名称AlphaBridge MCP for WordPress
    Connection · 地址https://connect.alphabridge-mcp.com/mcp
  3. 在聊天中选择 AlphaBridge MCP for WordPress

    开启新聊天,输入前先从插件列表中选择 AlphaBridge MCP for WordPress

  4. 试一试

    用 AlphaBridge MCP for WordPress 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 ChatGPT 说正在使用 AlphaBridge MCP for WordPress,或回答中出现 AlphaBridge MCP for WordPress 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Claude Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 打开终端

    Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell

  2. 粘贴这条命令并按 Enter

    claude mcp add --transport http --scope user alphabridge https://connect.alphabridge-mcp.com/mcp
  3. 在 Claude Code 中输入 /mcp

    应能看到 AlphaBridge MCP for WordPress 在列表中并显示已连接

  4. 试一试

    用 AlphaBridge MCP for WordPress 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude Code 说正在使用 AlphaBridge MCP for WordPress,或回答中出现 AlphaBridge MCP for WordPress 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Cursor · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 Cursor

    在 Cursor 中打开

    Cursor 会请你确认安装,点击 Install

  2. 在 Cursor 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 AlphaBridge MCP for WordPress 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Cursor 说正在使用 AlphaBridge MCP for WordPress,或回答中出现 AlphaBridge MCP for WordPress 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同

可连接 VS Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 VS Code

    在 VS Code 中打开

    VS Code 会请你确认安装,点击 Install

  2. 在 VS Code 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 AlphaBridge MCP for WordPress 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 VS Code 说正在使用 AlphaBridge MCP for WordPress,或回答中出现 AlphaBridge MCP for WordPress 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

通过网页连接的应用使用的地址

地址https://connect.alphabridge-mcp.com/mcp

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 AlphaBridge MCP for WordPress 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

通过网页连接

Claude Code

claude mcp add --transport http --scope user alphabridge https://connect.alphabridge-mcp.com/mcp

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "alphabridge": {
      "url": "https://connect.alphabridge-mcp.com/mcp"
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "alphabridge": {
      "type": "http",
      "url": "https://connect.alphabridge-mcp.com/mcp"
    }
  }
}

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

一览

每周下载量i
不在 npm/PyPI 上
许可证i
GPL-2.0
连接方式
在云端运行
传输方式
streamable-http
最新版本i
4.10.0
分类i
其他
发布到注册中心i
2026年10月30日
代码最后更新i
2026年11月19日
最近检查
2026年11月17日
作者
CultureClub-dev
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

通过互联网连接,适用于

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

全部应用及其优缺点 →

它能做什么

服务器要求先登录,才会列出它的工具。

基础检查i

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

  • ✓ 通过

    作者与仓库一致

    注册名称已通过 GitHub 账户 CultureClub-dev 验证,该账户拥有此仓库

  • ✓ 通过

    仍在维护

    代码最后更新于昨天

  • ✓ 通过

    有许可证

    使用 GPL-2.0

  • ✓ 通过

    端点有响应

    在 82 毫秒内响应(HTTP 401)

  • ✓ 通过

    使用 OAuth 登录

    声明支持 OAuth 登录,你的 AI 应用可以带你去登录

  • … 尚未检查

    工具描述中没有隐藏指令

    尚未检查;我们会在检查端点时读取工具列表

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/cultureclub-dev-alphabridge-mcp.svg)](https://mcp.popnx.com/en/servers/cultureclub-dev-alphabridge-mcp)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

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

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

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

常见问题

AlphaBridge MCP for WordPress 安全吗?

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

它需要哪些密钥或代码?

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

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

它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。

它还在维护吗?

GitHub 仓库最后更新于昨天,最新版本(4.10.0)于21天前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。

有什么可以替代它?

同一分类中有:World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

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

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

作者:koala73广泛使用★ 9.1万4天前更新

在云端运行✓ 服务方 · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

作者:openstatusHQ广泛使用★ 92762个月前更新

在云端运行✓ 服务方 · openstatus.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

作者:Klavis-AI正在增长★ 582414个月前更新

在云端运行仓库已归档✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

作者:jitsucom广泛使用★ 51364个月前更新

在云端运行✓ 服务方 · jitsu.com
与相似项目对比
本项
AlphaBridge MCP for WordPress
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
运行位置在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装
需要密钥否否否否否否
可在 Claude 中按 + 添加否否否否否否
基础检查5/54/44/44/41/44/4
许可证GPL-2.0AGPL-3.0AGPL-3.0MITApache-2.0MIT
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

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

AlphaBridge MCP — free plugin

Your WordPress site, managed in conversation. AlphaBridge MCP turns a WordPress site into a native Model Context Protocol server. Claude, ChatGPT and other MCP clients connect over one authenticated HTTPS endpoint. They write and edit posts, pages, media, categories and tags, reply to and moderate comments, set SEO titles and descriptions, manage user accounts, widgets and site settings, change prices, stock and orders in WooCommerce, read the outline of pages built with blocks or a common page builder, and undo a change with one sentence. Every tool checks WordPress capabilities on every single call.

The site only reads until an administrator turns on one switch for write access. Then every tool is on; each connection keeps its access level (full, content only or read only). Switching it off takes one click.

This repository holds the source of the free plugin, published on the WordPress.org plugin directory. It is the same code WordPress.org ships.

  • Plugin page: https://wordpress.org/plugins/alphabridge-mcp/
  • Website & documentation: https://alphabridge-mcp.com
  • Tool reference: https://alphabridge-mcp.com/docs.html
  • Security model: https://alphabridge-mcp.com/security.html

What it does

  • Native MCP endpoint — JSON-RPC 2.0 over HTTP POST at /wp-json/alphabridge/v1/mcp (protocol versions 2024-11-05, 2025-03-26, 2025-06-18 and the stateless 2026-07-28, side by side; the newest one can be switched off). Pure PHP inside WordPress: no Node middleware, no external service, nothing extra to host.
  • 107 structured tools across content, media, taxonomies, comments, widgets, menus, site settings, site info, users, plugins and themes (install, update, activate, delete), WordPress updates, cron and the error log, SEO fields, WooCommerce, maintenance, page builders, search and replace, bulk status changes, a connection check and the abilities of other plugins, each one once an administrator has switched it on.
  • A preview first for what has no way back — wp_update_core, the two ZIP installs and the two deletes run only with the confirm_token from their own preview (HMAC over the tool, the arguments, the account, the access level and the state the preview showed; 10 minutes).
  • Undo — wp_update_post, wp_bulk_update_status, wp_update_site_settings, wp_update_builder_element, wp_search_replace (page-builder pages and option rows), wp_activate_theme, wp_update_post_meta, wp_update_term_meta, wp_update_user_meta, wp_update_media, wp_create_term, wp_update_term, wp_create_menu, wp_add_menu_item, wp_update_widget, wp_add_widget, wp_delete_widget, wp_seo_set, wp_moderate_comment, wp_reply_comment, wp_delete_comment (into the trash), wp_wc_update_product (prices and status, through WooCommerce; the stock stays as it is) and wp_wc_create_coupon (into the trash again, while unused) leave an undo point with the previous values that expires after 7 days; an answer without one says why (undo_note), the deleting tools of terms, menu items, files, users and comments say when they are final, wp_wc_update_order_status says a status change is not undoable, and the meta, media, term, menu, widget, SEO, comment, product and coupon tools read back what was stored (saved_fields); wp_undo_list, wp_undo (with a dry run) and wp_undo_discard work on the account's own points, and a restore checks the rights of the original change again.
  • Page builders — wp_get_builder_layout reads a page as an outline: its elements in page order, with their visible text, link and image fields; elements that cannot be read safely, such as code, forms or unknown elements, are listed as locked, with the reason and without their content.
  • Read: WordPress blocks, Elementor, Beaver Builder, SiteOrigin Page Builder, SeedProd, GenerateBlocks, Kadence Blocks, Spectra, Stackable, Pagelayer, Otter Blocks and CoBlocks (both as plain blocks), WPBakery Page Builder, Divi 4, Avada (Fusion Builder), Flatsome (UX Builder) and Enfold (Avia Layout Builder).
  • Read according to the vendors' documentation: WPBakery Page Builder, Divi 4, Avada, Flatsome and Enfold.
  • Recognised, not read: Brizy, Themify Builder, Zion Builder, Live Composer, Cornerstone, Thrive Architect, Bricks, Breakdance, Oxygen 6, Oxygen Classic, BeTheme (BeBuilder), Visual Composer Website Builder, Divi 5 and Etch.

Where a builder shows its own data and post_content is only a copy — Elementor, Beaver Builder, SiteOrigin Page Builder and Enfold — wp_update_post refuses a change to the content while the builder is active, because it would not show, and says how to change the page instead.

wp_update_builder_element changes the text, link or image of one element right in the builder (WordPress blocks, GenerateBlocks, Kadence Blocks, Spectra, Stackable, Pagelayer, Elementor, Beaver Builder, SiteOrigin Page Builder, SeedProd, WPBakery Page Builder, Divi 4, Avada, Flatsome and Enfold), with a preview by default, an undo point before the write and a read-back after it.

wp_get_post names the builder a post was made with (built_with), wp_list_posts filters by it, and wp_duplicate_post copies a page with its custom fields and builder data (Elementor elements get new ids where the layout can be read, otherwise it is copied unchanged and the answer says so; builder data only for accounts with unfiltered_html).

  • Search and replace — wp_search_replace over posts, postmeta, options and terms, safe for serialized and JSON values, with a dry run per table; on page-builder pages (scope text) only through the builder's writer, with matches in locked places counted in locked_matches. post_ids keeps a run to the posts it names, expected_count writes only when the dry run still fits, protected options are never touched, and changed option rows get an undo point of their own (options_undo_token).
  • Preview protection for a staging site — wp_set_preview_protection (and a section on the page AlphaBridge → Staging) puts the site behind a shared password for visitors: a password page with HTTP 401 instead of every page, feed, search, the sitemaps of SEO plugins and the AJAX answers of plugins for visitors, the public REST API closed to them too, search engine visibility set to discouraged (and written back on switching off), X-Robots-Tag: noindex, nothing cached, the page cache emptied. The MCP endpoint, the sign-in, wp-admin, the REST root the hub reads and signed-in users keep working. Not covered, and said so: files under /wp-content/uploads/, caches outside PHP, what a plugin answers before WordPress has parsed the request (WooCommerce's wc-api, ?download_file=), pingbacks, and a shared password identifies nobody.
  • Staging status — wp_staging_status reports the role a person confirmed for the site (production or staging; unconfirmed counts as production) with a suggestion from what the site shows, never taken as proof, the other site of the pair, the host, the preview protection and a checklist with the next step. On request (check_partner) it asks the other site whether AlphaBridge MCP answers there, only at public addresses and tied to them. The role, the other site and the host are set on the page AlphaBridge → Staging or, for both sites at once, by the hub over alphabridge/v1/staging-pair, which takes a pair back with DELETE and leaves the role. Before the first change, the server instructions have an assistant that can write and may use the tool call it and ask the person whether to work on staging first, saying why and how; the prompt staging_workflow has the steps.
  • Staging first — on a site that counts as the production site, the first writing call a connection makes is paused: nothing runs, and the answer (nothing_changed, staging_hint) has the assistant tell the person why and how and offer to set staging up now; the same call with staging_acknowledged: true runs, and the question comes back after 7 days with the answers staging_reminder: week or never. The setting on the page AlphaBridge → Staging has Ask (the default), Off and Require, which refuses every change until an administrator releases the connection there for 24 hours. The ways back, the preview protection, the caches, comments and the order status are never held; the list grows through ab_mcp_staging_gate_exempt.
  • The card «Staging» on the page AlphaBridge → Staging brings it together: the checklist of wp_staging_status with the next step, the role and the other site, how to make the staging copy with the host's own staging guide where one was read (host.guide in the tool), the preview protection and Staging first with every connection; each user can fold it away.
  • OAuth 2.1 with PKCE — connect from Claude without copying tokens; the consent screen is your own login-protected site and offers Read only, Content and Full access, each described in one sentence, with Full preselected; the switch for write access on the site decides whether the connection may write. Apps register with the site (RFC 7591) or identify themselves with a client metadata document (CIMD), which the site fetches only once a logged-in user who may approve connections opens the consent screen; that can be switched off. Header authentication (Authorization / X-Api-Key) for clients without a Connect button.
  • Answers that name the way — where AlphaBridge's own checks refuse a call or report a failure, the answer says what did not work, why, and what does: the tool that finds an id, the right it takes, the switch, the accepted values. A refusal because write access is off, the access level or the role does not reach, or a tool is switched off adds the steps for the person, a direct link and the request to pass it on kindly and try again; a tool of the separate AlphaBridge MCP Pro is named as such instead of «Unknown tool». Errors WordPress itself reports are passed on as WordPress words them.
  • Free means free — no license keys, no registration, no usage limits, no locked features.

Security model

Handing an AI access to a site should feel safe, so control comes first:

  • Write access off out of the box. A new site, and every site after updating from a version before 4.4.0, starts with *write access off*: assistants can read content, media, terms, comments, settings and the structure of the site. Every tool that creates, changes or deletes is refused, and so is every reading tool noted *only with write access* (in this plugin the readers of user profile fields and of the error log), with an answer that says why and leads to the switch. The main switch *Write access for AI assistants* at the top of AlphaBridge → AI Connection holds for every connection (Claude, ChatGPT, Cursor and all others); an administrator switches it on after confirming, with a ticked box, that changes take effect immediately, that it is at the site owner's own risk and that a current backup exists. The account, the time, the version of that notice and its wording are recorded. Switching on switches every tool on; switching off takes one click.
  • Every connection acts as a real WordPress user; every tool enforces the matching capability, including object-level checks. What that user may not do, the AI cannot do.
  • Scoped connections — read-only or content-only keys with optional expiry, rotatable in one click.
  • Fine-tuning — every tool is on, and switching write access on switches every tool on again; switch single tools or whole groups off, and they va

只显示了开头部分;其余内容请在仓库中阅读