{"id":337059,"date":"2026-07-30T20:09:47","date_gmt":"2026-07-30T20:09:47","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/alphabridge-mcp\/"},"modified":"2026-10-12T14:40:20","modified_gmt":"2026-10-12T14:40:20","slug":"alphabridge-mcp","status":"publish","type":"plugin","link":"https:\/\/ml.wordpress.org\/plugins\/alphabridge-mcp\/","author":23528922,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"4.6.4","stable_tag":"4.6.4","tested":"7.1.3","requires":"6.5","requires_php":"8.0","requires_plugins":null,"header_name":"AlphaBridge MCP","header_author":"AlphaBridge","header_description":"Connect Claude and other MCP clients directly and securely to WordPress. Native Streamable-HTTP MCP server \u2014 fast, stable, with tool-group switches.","assets_banners_color":"ffffff","last_updated":"2026-10-12 14:40:20","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/www.alphabridge-mcp.com","header_author_uri":"","rating":0,"author_block_rating":0,"active_installs":20,"downloads":1444,"num_ratings":0,"support_threads":2,"support_threads_resolved":1,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"4.2.0":{"tag":"4.2.0","author":"cultureclub","date":"2026-07-30 20:47:58","revision":3629110},"4.2.2":{"tag":"4.2.2","author":"cultureclub","date":"2026-08-26 17:36:48","revision":3667544},"4.2.3":{"tag":"4.2.3","author":"cultureclub","date":"2026-08-28 22:08:38","revision":3670959},"4.3.0":{"tag":"4.3.0","author":"cultureclub","date":"2026-09-14 08:07:28","revision":3694747},"4.3.1":{"tag":"4.3.1","author":"cultureclub","date":"2026-09-15 12:51:12","revision":3697000},"4.3.10":{"tag":"4.3.10","author":"cultureclub","date":"2026-09-30 14:16:56","revision":3721437},"4.3.11":{"tag":"4.3.11","author":"cultureclub","date":"2026-09-30 16:26:12","revision":3721672},"4.3.2":{"tag":"4.3.2","author":"cultureclub","date":"2026-09-16 19:03:07","revision":3699154},"4.3.3":{"tag":"4.3.3","author":"cultureclub","date":"2026-09-22 14:03:08","revision":3707487},"4.3.4":{"tag":"4.3.4","author":"cultureclub","date":"2026-09-26 19:41:12","revision":3714670},"4.3.5":{"tag":"4.3.5","author":"cultureclub","date":"2026-09-27 08:01:18","revision":3715124},"4.3.6":{"tag":"4.3.6","author":"cultureclub","date":"2026-09-28 15:53:17","revision":3717537},"4.3.7":{"tag":"4.3.7","author":"cultureclub","date":"2026-09-29 10:39:50","revision":3718785},"4.3.8":{"tag":"4.3.8","author":"cultureclub","date":"2026-09-30 05:03:46","revision":3720329},"4.3.9":{"tag":"4.3.9","author":"cultureclub","date":"2026-09-30 08:58:40","revision":3720758},"4.4.0":{"tag":"4.4.0","author":"cultureclub","date":"2026-10-02 11:37:34","revision":3724687},"4.5.0":{"tag":"4.5.0","author":"cultureclub","date":"2026-10-02 16:04:05","revision":3725117},"4.5.1":{"tag":"4.5.1","author":"cultureclub","date":"2026-10-03 09:58:56","revision":3726070},"4.5.2":{"tag":"4.5.2","author":"cultureclub","date":"2026-10-06 09:28:58","revision":3730407},"4.5.3":{"tag":"4.5.3","author":"cultureclub","date":"2026-10-06 19:46:49","revision":3731481},"4.6.0":{"tag":"4.6.0","author":"cultureclub","date":"2026-10-07 14:48:19","revision":3732828},"4.6.1":{"tag":"4.6.1","author":"cultureclub","date":"2026-10-07 22:38:35","revision":3733441},"4.6.2":{"tag":"4.6.2","author":"cultureclub","date":"2026-10-08 00:01:56","revision":3733484},"4.6.3":{"tag":"4.6.3","author":"cultureclub","date":"2026-10-12 12:18:32","revision":3741461},"4.6.4":{"tag":"4.6.4","author":"cultureclub","date":"2026-10-12 14:40:20","revision":3741885}},"upgrade_notice":{"4.6.4":"<p>The settings for how apps connect moved into the connect card, each under the app it concerns; Claude&#039;s two ways in sit side by side, nothing folded away. Nothing else changes.<\/p>","4.6.3":"<p>Sign-in from ChatGPT and Codex works behind host firewalls that block app IDs in address form: the site checks this itself and lets apps register instead. The settings for how apps connect sit on one card: two settings and a status line for ChatGPT and Codex. Nothing else changes.<\/p>","4.6.2":"<p>Tools that can publish content now tell AI clients so and count as destructive, so clients can ask you first. Nothing else changes.<\/p>","4.6.1":"<p>ChatGPT can connect to the site directly again while apps with a metadata document are accepted. Nothing else changes.<\/p>","4.6.0":"<p>Switching on write access now asks for two boxes: how write access works, and the Terms of Use (optional with a paid licence). Where write access is on already, it stays on.<\/p>","4.5.3":"<p>On a German site every text of the plugin a person reads is now German: settings page, consent screen, log, and the refusals an assistant passes on. Claude Code gets a ready-made command. Nothing else changes.<\/p>","4.5.0":"<p>The box with Read and Full becomes the main switch \u00abWrite access for AI assistants\u00bb, for every connection. Switching it on switches every tool on; a confirmation of 4.4.0 stays valid. New connections start with the full access level.<\/p>","4.4.0":"<p>After this update AlphaBridge MCP only reads until an administrator switches to Full at the top of Settings \u2192 AlphaBridge MCP, at the site owner&#039;s own risk. In Full, writing Mighty tools are on, also ones that were off before.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3731483,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3731483,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3731483,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3629098,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3629098,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{"blueprint.json":{"filename":"blueprint.json","revision":3741886,"resolution":false,"location":"assets","locale":"","contents":"{\"$schema\":\"https:\\\/\\\/playground.wordpress.net\\\/blueprint-schema.json\",\"landingPage\":\"\\\/wp-admin\\\/options-general.php?page=alphabridge-mcp\",\"preferredVersions\":{\"php\":\"8.3\",\"wp\":\"latest\"},\"phpExtensionBundles\":[\"kitchen-sink\"],\"steps\":[{\"step\":\"login\",\"username\":\"admin\",\"password\":\"password\"},{\"step\":\"installPlugin\",\"pluginData\":{\"resource\":\"wordpress.org\\\/plugins\",\"slug\":\"alphabridge-mcp\"},\"options\":{\"activate\":true}}]}"}},"all_blocks":[],"tagged_versions":["4.2.0","4.2.2","4.2.3","4.3.0","4.3.1","4.3.10","4.3.11","4.3.2","4.3.3","4.3.4","4.3.5","4.3.6","4.3.7","4.3.8","4.3.9","4.4.0","4.5.0","4.5.1","4.5.2","4.5.3","4.6.0","4.6.1","4.6.2","4.6.3","4.6.4"],"block_files":[],"assets_screenshots":{"screenshot-1.jpg":{"filename":"screenshot-1.jpg","revision":3726074,"resolution":"1","location":"assets","locale":"","width":2560,"height":2478},"screenshot-2.jpg":{"filename":"screenshot-2.jpg","revision":3726074,"resolution":"2","location":"assets","locale":"","width":2560,"height":2856},"screenshot-3.jpg":{"filename":"screenshot-3.jpg","revision":3726074,"resolution":"3","location":"assets","locale":"","width":2560,"height":1518},"screenshot-4.jpg":{"filename":"screenshot-4.jpg","revision":3726074,"resolution":"4","location":"assets","locale":"","width":2560,"height":3120},"screenshot-5.jpg":{"filename":"screenshot-5.jpg","revision":3741886,"resolution":"5","location":"assets","locale":"","width":2560,"height":1926},"screenshot-6.jpg":{"filename":"screenshot-6.jpg","revision":3741886,"resolution":"6","location":"assets","locale":"","width":2560,"height":1922}},"screenshots":{"1":"At the top, the main switch for write access, off until you turn it on. Below it, pick your assistant \u2014 Claude, ChatGPT, Cursor or another client \u2014 and follow its steps: for Claude a direct link into its connector directory, this site's address to copy, the video and the guide. A token is created only where one is needed.","2":"The moment you create a connection, the plugin shows what you need once \u2014 the Bearer token and a copy-paste config for Cursor \/ Claude Code, and the connector URL if connector-URL authentication is switched on \u2014 with a reminder to save it, because the token is shown in full only once.","3":"Optional advanced settings for a connection: a label, the WordPress user it acts as, full, content-only or read-only access, and an optional expiry in days.","4":"Switch all tools, a group or a single tool; open a group to see its tool groups and what each tool does, whether it reads or writes, or search for one. These switches sit under \u00abFine-tuning\u00bb, below the main switch for write access at the top of the page.","5":"Claude: both ways in side by side \u2014 through the hub (one connection, up to 10 sites) or directly with a custom connector \u2014 and under them the setting Claude needs: whether apps may sign in with their Connect button.","6":"ChatGPT: its three steps, and under them how ChatGPT signs in, with the status line for ChatGPT and Codex \u2014 direct, with the time of the last check and \u00abCheck again\u00bb \u2014 or, where the check found a firewall that blocks the direct sign-in, the two steps that lead to the goal: add the connector in the app again, or connect through the free AlphaBridge hub."}},"plugin_section":[],"plugin_tags":[2353,216196,229563,242115,260626],"plugin_category":[59],"plugin_contributors":[273898],"plugin_business_model":[],"class_list":["post-337059","plugin","type-plugin","status-publish","hentry","plugin_tags-ai","plugin_tags-chatgpt","plugin_tags-claude","plugin_tags-mcp","plugin_tags-mcp-server","plugin_category-utilities-and-tools","plugin_contributors-cultureclub","plugin_committers-cultureclub"],"banners":{"banner":"https:\/\/ps.w.org\/alphabridge-mcp\/assets\/banner-772x250.png?rev=3629098","banner_2x":"https:\/\/ps.w.org\/alphabridge-mcp\/assets\/banner-1544x500.png?rev=3629098","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/alphabridge-mcp\/assets\/icon.svg?rev=3731483","icon":"https:\/\/ps.w.org\/alphabridge-mcp\/assets\/icon.svg?rev=3731483","icon_2x":false,"generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/alphabridge-mcp\/assets\/screenshot-1.jpg?rev=3726074","caption":"At the top, the main switch for write access, off until you turn it on. Below it, pick your assistant \u2014 Claude, ChatGPT, Cursor or another client \u2014 and follow its steps: for Claude a direct link into its connector directory, this site's address to copy, the video and the guide. A token is created only where one is needed."},{"src":"https:\/\/ps.w.org\/alphabridge-mcp\/assets\/screenshot-2.jpg?rev=3726074","caption":"The moment you create a connection, the plugin shows what you need once \u2014 the Bearer token and a copy-paste config for Cursor \/ Claude Code, and the connector URL if connector-URL authentication is switched on \u2014 with a reminder to save it, because the token is shown in full only once."},{"src":"https:\/\/ps.w.org\/alphabridge-mcp\/assets\/screenshot-3.jpg?rev=3726074","caption":"Optional advanced settings for a connection: a label, the WordPress user it acts as, full, content-only or read-only access, and an optional expiry in days."},{"src":"https:\/\/ps.w.org\/alphabridge-mcp\/assets\/screenshot-4.jpg?rev=3726074","caption":"Switch all tools, a group or a single tool; open a group to see its tool groups and what each tool does, whether it reads or writes, or search for one. These switches sit under \u00abFine-tuning\u00bb, below the main switch for write access at the top of the page."},{"src":"https:\/\/ps.w.org\/alphabridge-mcp\/assets\/screenshot-5.jpg?rev=3741886","caption":"Claude: both ways in side by side \u2014 through the hub (one connection, up to 10 sites) or directly with a custom connector \u2014 and under them the setting Claude needs: whether apps may sign in with their Connect button."},{"src":"https:\/\/ps.w.org\/alphabridge-mcp\/assets\/screenshot-6.jpg?rev=3741886","caption":"ChatGPT: its three steps, and under them how ChatGPT signs in, with the status line for ChatGPT and Codex \u2014 direct, with the time of the last check and \u00abCheck again\u00bb \u2014 or, where the check found a firewall that blocks the direct sign-in, the two steps that lead to the goal: add the connector in the app again, or connect through the free AlphaBridge hub."}],"raw_content":"<!--section=description-->\n<p><strong>Claude and ChatGPT for WordPress. One switch. Full power. Free.<\/strong><\/p>\n\n<p>Tell your AI assistant what you need, in plain words, and it happens on your WordPress site:<\/p>\n\n<ul>\n<li>\"Write a post from these notes and schedule it for Friday.\"<\/li>\n<li>\"Approve the new comments and answer the question about opening hours.\"<\/li>\n<li>\"Which of my sites have updates waiting?\"<\/li>\n<\/ul>\n\n<p>AlphaBridge MCP turns your site into an MCP server, the open standard AI assistants use to work with other software. Connect Claude or ChatGPT in about two minutes. You need no account with us, no API key and no extra server.<\/p>\n\n<p>Watch the whole setup in one minute: <a href=\"https:\/\/www.youtube.com\/watch?v=DlMJ9tfrqJg\">Connect Claude to WordPress in five steps<\/a><\/p>\n\n<p>https:\/\/www.youtube.com\/watch?v=DlMJ9tfrqJg<\/p>\n\n<h4>What the free plugin does<\/h4>\n\n<ul>\n<li><strong>Write and publish.<\/strong> Turn notes into posts and pages, add images, set categories and tags, schedule the date.<\/li>\n<li><strong>Look after your site.<\/strong> Answer and moderate comments, see pending updates and the health of your site.<\/li>\n<li><strong>Read what matters.<\/strong> It reads widgets, site settings, SEO fields and pages built with blocks or a common page builder. Ask what needs work.<\/li>\n<li><strong>Up to 10 sites in one chat.<\/strong> The free AlphaBridge Connect hub brings them into the same conversation.<\/li>\n<li><strong>Nothing extra to host.<\/strong> AlphaBridge runs inside WordPress, in plain PHP, on ordinary hosting.<\/li>\n<\/ul>\n\n<p>40 tools. No license key, no registration, no quotas. The free plugin is complete, not a trial.<\/p>\n\n<h4>Safe by default<\/h4>\n\n<ul>\n<li><strong>Read-only until you switch it on.<\/strong> Out of the box the AI can only read. One switch, \"Write access for AI assistants\", lets it create, change and delete. One click turns it off again.<\/li>\n<li><strong>Your WordPress rights apply.<\/strong> Every connection acts as a real WordPress user. What that user may not do, the AI cannot do.<\/li>\n<li><strong>Rules per connection.<\/strong> Give each app full access, content only or read only, with an optional expiry. Switching write access on turns every tool on. Each connection keeps its access level. Single tools or whole groups can be switched off.<\/li>\n<li><strong>A clear log.<\/strong> The settings page lists the latest 200 tool calls with time and status. A limit of 120 requests a minute stops runaway request bursts.<\/li>\n<li><strong>Answers that help.<\/strong> When AlphaBridge refuses a request, it says why and what to do next.<\/li>\n<\/ul>\n\n<h4>Connect in two minutes<\/h4>\n\n<ul>\n<li><strong>Claude:<\/strong> pick \"AlphaBridge MCP for WordPress\" in Claude's connector directory and approve on your site. No token to copy.<\/li>\n<li><strong>ChatGPT<\/strong> on Plus, Pro, Business, Enterprise and Edu: add your site as an MCP app and approve on your site.<\/li>\n<li><strong>Cursor, Claude Code and other MCP clients:<\/strong> create a connection in the plugin and paste one ready-made config.<\/li>\n<\/ul>\n\n<h4>More with Pro<\/h4>\n\n<p>AlphaBridge MCP Pro is a separate add-on. Everything in the free plugin plus the Pro tools, 135 tools on your site:<\/p>\n\n<ul>\n<li><strong>Page builders.<\/strong> Change texts, links and images on pages of Elementor and many other page builders, with a preview first.<\/li>\n<li><strong>Code with a safety net.<\/strong> Edit theme and plugin files and PHP snippets. After each change to active PHP code, Pro tests the site and puts the old version back if it stops loading.<\/li>\n<li><strong>Undo.<\/strong> One sentence brings an edited page or file back. Its undo points expire after 7 days by default, adjustable from 1 to 30 days.<\/li>\n<li><strong>Shop, SEO, menus and users.<\/strong> Prices, stock and order status in WooCommerce. SEO titles and descriptions in Yoast or Rank Math. Menus and users by chat.<\/li>\n<li><strong>Your other plugins.<\/strong> Run the abilities your other plugins offer the AI.<\/li>\n<\/ul>\n\n<p>The Agency plan adds Site Deploy: the AI publishes files, themes and whole builds over SFTP onto the server the site runs on. Agency covers up to 10 sites.<\/p>\n\n<p>Pro can be tried free for 7 days, no card needed. The free plugin stays complete without it. Editions, guides and a comparison with other WordPress MCP plugins: <a href=\"https:\/\/alphabridge-mcp.com\">alphabridge-mcp.com<\/a><\/p>\n\n<p>Claude, ChatGPT and the other names mentioned belong to their respective owners. Naming them does not mean they partner with, sponsor or endorse AlphaBridge.<\/p>\n\n<h3>External services<\/h3>\n\n<p>AlphaBridge MCP sends no telemetry and calls no outside service on its own. Three things reach beyond your site, each only when you start them:<\/p>\n\n<ul>\n<li><strong>AlphaBridge Connect, optional.<\/strong> If you connect through the hub at connect.alphabridge-mcp.com, it calls your site to set up the connection and to pass on the tool calls you make. It keeps your site's access key encrypted and passes content through without storing it. <a href=\"https:\/\/connect.alphabridge-mcp.com\/legal\/terms\">Terms<\/a> and <a href=\"https:\/\/connect.alphabridge-mcp.com\/legal\/privacy\">privacy notice<\/a>.<\/li>\n<li><strong>The app you connect.<\/strong> Some apps, such as ChatGPT, identify themselves with a small public file. While you approve such an app on your site, your site fetches that file from the app's address. The request carries no content, cookies or tokens from your site. You can switch this off under ChatGPT \u2192 \"Switch the direct sign-in off\" on the plugin's settings page.<\/li>\n<li><strong>A file you name.<\/strong> The tool wp_upload_media_from_url downloads the file at the URL you give it.<\/li>\n<\/ul>\n\n<!--section=installation-->\n<ol>\n<li>In WordPress, go to Plugins \u2192 Add New Plugin, search for \"AlphaBridge MCP\", install and activate it.<\/li>\n<li>Claude: open Connectors, find \"AlphaBridge MCP for WordPress\" in the directory and connect. Enter your site's address and approve on your own site's login-protected consent screen. There is no endpoint or token to copy. To connect without the hub, add your endpoint as a custom connector instead.<\/li>\n<li>ChatGPT: open Plugins, choose Add, then Create MCP app. Paste your site's endpoint from Settings \u2192 AlphaBridge MCP as the server URL, choose OAuth and approve on your site.<\/li>\n<li>Cursor, Claude Code and other clients: under Settings \u2192 AlphaBridge MCP, create a connection and copy its ready-made config.<\/li>\n<li>Assistants only read until you allow more. To let them create, change and delete, and read user profile fields, switch on \"Write access for AI assistants\" at the top of Settings \u2192 AlphaBridge MCP. Changes then take effect immediately and not everything can be undone. You switch it on at your own risk, so keep a current backup. Switching it on asks you to agree to the Terms of Use.<\/li>\n<\/ol>\n\n<!--section=faq-->\n<dl>\n<dt id=\"is%20it%20really%20free%3F\"><h3>Is it really free?<\/h3><\/dt>\n<dd><p>Yes. All its tools work without payment, registration or license key, and the plugin does not expire. There are no usage quotas, only a limit of 120 requests a minute that protects your server. You need no API key or AI credits either: AlphaBridge has no AI of its own, and you use Claude or ChatGPT as you do today.<\/p><\/dd>\n<dt id=\"is%20it%20secure%3F\"><h3>Is it secure?<\/h3><\/dt>\n<dd><p>Yes, and it starts read-only. Until an administrator switches on write access, every tool that creates, changes or deletes is refused, and so is the reader of user profile fields. Each connection acts as a real WordPress user: what that user may not do, the AI cannot do. It cannot read arbitrary site options, only a fixed list of common settings and the settings of the site's widgets. The latest 200 calls are logged.<\/p><\/dd>\n<dt id=\"what%20if%20the%20ai%20gets%20something%20wrong%3F\"><h3>What if the AI gets something wrong?<\/h3><\/dt>\n<dd><p>Deleted posts and pages go to the trash by default, and WordPress keeps the revisions of edited posts as usual. Write access switches off again with one click. Keep a current backup all the same. Pro adds undo by chat: one sentence brings back an edited page, a page-builder element, a theme or plugin file or a PHP snippet.<\/p><\/dd>\n<dt id=\"which%20page%20builders%20does%20it%20read%3F\"><h3>Which page builders does it read?<\/h3><\/dt>\n<dd><p>It reads a page as an outline: its elements in page order, with their visible texts, links and images. Elements it cannot read safely, such as code or forms, are listed as locked, without their content.<\/p>\n\n<ul>\n<li>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).<\/li>\n<li>Read according to the vendors' documentation: WPBakery Page Builder, Divi 4, Avada, Flatsome and Enfold.<\/li>\n<li>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.<\/li>\n<\/ul>\n\n<p>Where a builder shows its own data and the WordPress content is only a copy, as with Elementor, Beaver Builder, SiteOrigin Page Builder and Enfold, the free plugin leaves that copy alone while the builder is active, because a change there would not show, and says how to change the page instead. With Pro, the AI changes texts, links and images right in the builder, with a preview first.<\/p><\/dd>\n<dt id=\"does%20it%20work%20on%20shared%20hosting%3F\"><h3>Does it work on shared hosting?<\/h3><\/dt>\n<dd><p>Yes. It runs inside WordPress, in plain PHP, over the WordPress REST API. There is nothing else to install on the server. It needs PHP 8.0 or newer, and HTTPS is recommended.<\/p><\/dd>\n<dt id=\"sign-in%20ends%20with%20%E2%80%9Cnot%20acceptable%E2%80%9D%20or%20mentions%20mod_security\"><h3>Sign-in ends with \u201cNot Acceptable\u201d or mentions Mod_Security<\/h3><\/dt>\n<dd><p>Some hosts run a firewall that refuses any request with a web address in the app's ID, and some apps (ChatGPT, Codex) identify themselves with exactly such an address. The site checks this itself and, where the firewall blocks it, lets ChatGPT and Codex register with the site instead. Then:<\/p>\n\n<ol>\n<li>In the app, remove the connector for this site and add it again. The sign-in now goes through.<\/li>\n<li>If it still fails, add the connector once more, this time with this address instead of your site's: https:\/\/connect.alphabridge-mcp.com\/mcp. When you click Authenticate, the free AlphaBridge hub asks for your site's address. Enter it and approve on your site as usual.<\/li>\n<\/ol>\n\n<p>If the site did not notice the firewall (some let requests from the site's own server pass), switch the direct sign-in off by hand: Settings \u2192 AlphaBridge MCP \u2192 ChatGPT \u2192 \"Switch the direct sign-in off\", then add the connector again.<\/p><\/dd>\n<dt id=\"a%20proxy%20has%20trouble%20with%20the%20newer%20mcp%20revision\"><h3>A proxy has trouble with the newer MCP revision<\/h3><\/dt>\n<dd><p>The site answers apps in MCP revision 2026-07-28 and keeps the older revisions for apps that ask for them. If a proxy in front of the site cannot handle the newer one, a developer switches it off with <code>add_filter( 'ab_mcp_modern_protocol', '__return_false' );<\/code> in a small plugin, or by setting <code>modern_protocol<\/code> to false in the option <code>ab_mcp_options<\/code>; the site then answers in the older revisions only.<\/p><\/dd>\n<dt id=\"does%20the%20plugin%20send%20data%20anywhere%3F\"><h3>Does the plugin send data anywhere?<\/h3><\/dt>\n<dd><p>No. It sends no telemetry and contacts no outside service on its own. The three cases you start yourself are listed under External services, at the end of the description.<\/p><\/dd>\n<dt id=\"do%20i%20need%20pro%3F\"><h3>Do I need Pro?<\/h3><\/dt>\n<dd><p>Not to get started. The free plugin covers content, media and comments, on as many sites as you like. Take Pro for page-builder texts, code and your shop, with undo for pages and files. Agency is for client sites: all tools and Site Deploy on up to 10 sites. Pro can be tried free for 7 days, no card needed: <a href=\"https:\/\/alphabridge-mcp.com\/#pricing\">alphabridge-mcp.com<\/a><\/p><\/dd>\n<dt id=\"is%20there%20an%20affiliate%20programme%3F\"><h3>Is there an affiliate programme?<\/h3><\/dt>\n<dd><p>Yes. It pays 60% of every Pro and Agency sale you refer, renewals included, monthly in US dollars via PayPal. It is open worldwide to anyone over 18 who does not live in a country under a US embargo, customer or not: apply on https:\/\/alphabridge-mcp.com\/affiliates, where you also find the terms, banners and ready-made texts. The commission comes from sales of the separately sold Pro and Agency editions. This free plugin itself earns none, and it works fully without joining.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>4.6.4<\/h4>\n\n<ul>\n<li><strong>Everything about connecting sits in one place: the connect card.<\/strong> The settings moved up from a card of their own at the foot of the page into the panel of the app they concern \u2014 the sign-in for apps under Claude and under ChatGPT (there with the status line for ChatGPT and Codex, \u00abCheck again\u00bb and the link to switch the direct sign-in off), the connector address with the token under Cursor and \u00abOther\u00bb, next to the token form. Each has its own Save.<\/li>\n<li><strong>Claude: both ways in, side by side, nothing folded away.<\/strong> \u00abThrough the hub\u00bb (one connection, up to 10 sites) with its three steps, and \u00abDirectly\u00bb (this site only) with two: add a custom connector in Claude with this site's address, then sign in here and approve.<\/li>\n<\/ul>\n\n<h4>4.6.3<\/h4>\n\n<ul>\n<li><strong>Sign-in works behind firewalls that block app IDs in address form.<\/strong> Some hosts (Bluehost with Mod_Security) answer \u00ab406 Not Acceptable\u00bb as soon as an app's ID is a web address, which is how ChatGPT and Codex identify themselves. The site now checks this itself with one request to its own sign-in page and, where the firewall blocks it, stops offering that way, so apps register with the site instead; the ChatGPT panel and the setting say so. The check runs when the settings page opens (again after six hours), on every save of the settings and on \u00abCheck again\u00bb. Reported in the support forum on 12 October 2026, thank you.<\/li>\n<li><strong>The settings for how apps connect sit on one card: two settings and a status line for ChatGPT and Codex.<\/strong> \u00abSign-in for apps\u00bb and \u00abConnector address with token\u00bb replace the three folded \u00abadvanced\u00bb sections, each with one sentence on what it is for; the status line says whether ChatGPT and Codex sign in directly or register with the site, with \u00abCheck again\u00bb and a link to switch the direct sign-in off. The switch for the MCP revision 2026-07-28 leaves the page: the setting keeps its value, and the <code>ab_mcp_modern_protocol<\/code> filter stays (see FAQ).<\/li>\n<li>FAQ: \u00abSign-in ends with \u201cNot Acceptable\u201d or mentions Mod_Security\u00bb.<\/li>\n<\/ul>\n\n<h4>4.6.2<\/h4>\n\n<ul>\n<li><strong>Tools that can publish now say so to AI clients.<\/strong> Eight tools can make content public on your site: creating and updating posts, replying to and approving comments, uploading media from a file or a web address, changing the texts of media, and renaming categories and tags. All eight now report <code>openWorldHint: true<\/code> and <code>destructiveHint: true<\/code>, because what is published cannot be taken back once it is out: a published post pings other sites and may go to newsletter subscribers, a reply reaches the commenter at once, and an uploaded file can be downloaded by anyone. An AI client can then ask you before it runs them. Reading, drafts, new categories and tags, and deleting stay inside the site as before.<\/li>\n<li>This follows OpenAI's review rules for tool hints. No setting changed.<\/li>\n<\/ul>\n\n<h4>4.6.1<\/h4>\n\n<ul>\n<li><strong>ChatGPT connects directly again while \u00abAccept apps with a metadata document\u00bb is on.<\/strong> ChatGPT identifies itself with a metadata document that prefers the token method private_key_jwt and also lists \u00abnone\u00bb among the methods it supports. The plugin refused any document whose preferred method was not \u00abnone\u00bb, so ChatGPT could not connect to the site directly. It now takes \u00abnone\u00bb from that list and treats the app as a public client, with PKCE as before. A document that asks for a shared client secret, or that offers no \u00abnone\u00bb at all, is still refused, and so is a list that does not contain the document's own preferred method. Reported in the support forum on 3 October 2026, thank you. No setting changed.<\/li>\n<\/ul>\n\n<h4>4.6.0<\/h4>\n\n<ul>\n<li><strong>Switching on write access asks for two boxes, the second for the Terms of Use.<\/strong> The notice says, as before, that changes take effect immediately, that not everything can be undone and that write access is switched on at the site owner's own risk, and now also that statutory rights and the liability rules of the Terms of Use remain unaffected. With the first box the administrator agrees to how write access works; with the second, to the <a href=\"https:\/\/alphabridge-mcp.com\/terms\">Terms of Use<\/a> of CultureClub Kulturagentur UG (haftungsbeschr\u00e4nkt), version of 7 October 2026, which the dialog links. Neither box is ticked in advance. Without a paid licence both are required; with a valid licence of Pro or Agency the second is optional, because the terms already apply from the purchase. Switching on by code is no agreement to the terms. The button reads \u00abAgree and switch on write access\u00bb.<\/li>\n<li>No box confirms a fact any more (\u00abUnderstood\u00bb, \u00abI have a current backup\u00bb): both say what the administrator agrees to.<\/li>\n<li>The notice and the boxes come in English and German only, as the Terms of Use, and from the plugin itself: a language pack does not change them. Other languages read English. The link goes to the German version of the terms on a German site.<\/li>\n<li>The record of a switch-on also holds the wording of the second box, the address it linked, whether and to which version of the terms the administrator agreed, and the edition. It stays on the site; nothing is sent anywhere. The notice is version 3; a record of version 1 or 2 stays valid.<\/li>\n<li>Where write access was switched on before this version, it stays on. The settings page says once that the agreement to the terms is asked for the next time write access is switched on; \u00abDismiss\u00bb hides it for this version of the terms.<\/li>\n<\/ul>\n\n<h4>4.5.3<\/h4>\n\n<ul>\n<li><strong>All visible texts of the plugin come in German on a German site<\/strong> (de_DE, de_DE_formal, de_AT, de_CH, de_CH_informal): the settings page with its cards, notices, tables, buttons, tooltips and the texts of its script; the consent screen with its access levels and its error pages; the description in the plugin list; the log, whose status and time now follow the language; and the refusals and error messages of the tools that an assistant passes on. The plugin brings these files itself; a language pack from translate.wordpress.org still takes precedence for every text it has.<\/li>\n<li>Stays English on purpose: what is written for the assistant \u2014 the descriptions of the tools and their parameters (shown behind the \u00abi\u00bb in the fine-tuning), the server instructions and the notes on single elements in the outline that <code>wp_get_builder_layout<\/code> hands over \u2014 and the protocol's own errors (JSON-RPC, and the error codes the OAuth standard sends to an app). The names and descriptions of abilities come from the plugins that offer them.<\/li>\n<li>The reasons why an app's metadata document is refused, the note of <code>wp_seo_detect<\/code> about AIOSEO and the status and time in the log are translatable now. The plugin header names <code>\/languages<\/code> as its Domain Path, so the plugin list shows the description in German also while the plugin is inactive.<\/li>\n<li><strong>A command for Claude Code.<\/strong> After a connection is created, the settings page shows a ready-made <code>claude mcp add --transport http \u2026<\/code> command with the endpoint and the token, as the guide on alphabridge-mcp.com does. The config with <code>mcp-remote<\/code> is now labelled for Cursor only: in Claude Code, <code>${AUTH}<\/code> in that config stayed empty and <code>\/mcp<\/code> reported it missing.<\/li>\n<li>The note under the fine-tuning names the rate limit without \u00ab(fixed)\u00bb.<\/li>\n<li>The readme says what the audit log keeps: the latest 200 tool calls.<\/li>\n<\/ul>\n\n<h4>4.5.2<\/h4>\n\n<ul>\n<li><strong>The request for a review is a short strip at the foot of the coloured header<\/strong> of Settings \u2192 AlphaBridge MCP instead of a WordPress notice. As before it appears only there, once the site has used the plugin for at least 14 days and made at least 50 successful tool calls, names exactly these figures and asks everyone the same way. \u00abWrite a review\u00bb now counts as an answer: the strip does not come back afterwards, as after \u00abDon't show again\u00bb. Its texts, and \u00ab(opens in a new tab)\u00bb for screen readers, come in German with the plugin, and so do the texts of the header around it that were still English on German sites (\u00abConnect your AI assistant\u00bb, the question below it and the hints on the assistant buttons).<\/li>\n<li><strong>A \u00abSettings\u00bb link in the plugin list.<\/strong> The plugin's row under Plugins now starts with \u00abSettings\u00bb, which opens Settings \u2192 AlphaBridge MCP, as WordPress plugins usually do. It shows only to users who may open that page, and it comes in German with the plugin (de_DE, de_DE_formal, de_AT, de_CH, de_CH_informal).<\/li>\n<\/ul>\n\n<h4>4.5.1<\/h4>\n\n<ul>\n<li><strong>The answer to a tool of AlphaBridge MCP Pro, and the paragraph about Pro in the server instructions, state facts only.<\/strong> A call of a tool that belongs to the separate AlphaBridge MCP Pro or its Agency plan is answered with the edition it belongs to and the page that describes the editions and their tools (https:\/\/alphabridge-mcp.com\/docs). The steps to install Pro, the request to the assistant to point the person to Pro and the link to the prices are gone: ChatGPT's app directory allows saying that a feature is missing, not promoting an upgrade. The server instructions of a site without Pro list what is not on the site and name the same page. No tool, permission or setting changed.<\/li>\n<li><strong>The description says which reading tool waits for write access.<\/strong> It said that with write access off assistants could not read code, files, the database, logs or credentials; this plugin has no tool for any of these. Its only reading tool that waits for write access reads user profile fields (<code>wp_get_user_meta<\/code>). The description, the installation steps and the FAQ now say so. The description also says that each connection keeps its access level (Full, Content or Read only) when write access is on.<\/li>\n<li>The directory page is shorter: a shorter name and short description, the description in short paragraphs, the AlphaBridge Connect hub under its own heading (up to 10 sites in one chat, free, in every edition) and AlphaBridge MCP Pro as a list. \u00abfast, stable\u00bb and \u00abfaster and more stable\u00bb are gone from the plugin's description and the readme; nothing measured backs them. The captions of screenshots 1 and 5 match the current settings page.<\/li>\n<li>The new sentence of the answer to a Pro tool comes in German with the plugin (de_DE, de_DE_formal, de_AT, de_CH, de_CH_informal); the two sentences with the steps to install Pro are gone.<\/li>\n<li><strong>A token in the query string or in the request body is never accepted, also with the connector URL switched on.<\/strong> With the connector URL on, <code>\/mcp?token=\u2026<\/code> and a <code>token<\/code> field in the body were taken as the token too; only the path <code>\/mcp\/&lt;token&gt;<\/code> was meant. Now only the path counts, as the FAQ says. Header authentication is unchanged.<\/li>\n<li>The server instructions of a site without Pro name changing the texts, links and images of page-builder elements as not on this site, instead of the texts of page-builder pages: reading them with <code>wp_get_builder_layout<\/code> works on every site. The list of what AlphaBridge MCP Pro adds says that its test requests run after PHP code is saved and catch the fatal errors they hit, not every error.<\/li>\n<\/ul>\n\n<h4>4.5.0<\/h4>\n\n<ul>\n<li><strong>The main switch \u00abWrite access for AI assistants\u00bb replaces the box with the modes Read and Full.<\/strong> It sits where the box was, the first thing on Settings \u2192 AlphaBridge MCP, and holds for every connection \u2014 Claude, ChatGPT, Cursor and all others. Off (as every site starts) assistants only read; on, they read and write with full power. The page calls the states \u00abwrite access off (read only)\u00bb and \u00abwrite access on (full power)\u00bb; the internal names (<code>read<\/code>, <code>full<\/code>), the option and the PHP interface stay as they were. Switching on opens a small window at the switch with the notice and a box to tick (without JavaScript the same fields stand in the page); switching off takes one click. The notice is new (version 2): changes take effect immediately, they can create, change and also delete, not everything can be undone, at your own risk, a current backup. A confirmation of the notice of 4.4.0 stays valid; nobody has to confirm again.<\/li>\n<li><strong>Switching on write access switches everything on.<\/strong> Every tool is on afterwards, also one that was switched off before or kept off from a version before 4.4.0. Single tools can be switched off under Fine-tuning; that holds until write access is switched on the next time. Only a switch from off to on does this: a second click from an old tab while write access is on changes nothing. An update alone resets nothing.<\/li>\n<li><strong>The fine-tuning, compact and open.<\/strong> Four main groups, seven at most with the Pro add-on (Content; Site &amp; users; Plugins, themes &amp; code; Database &amp; operations; Shop; Undo; Abilities of other plugins), each with its switch, its tool groups and how many of its tools are on; every tool group opens its tools. Every tool shows a short name in your language next to its name in code, and its description for the assistant behind an \u00abi\u00bb; the search finds a tool by either and by the names of its groups. The only badges left are \u00abReads\u00bb and \u00abWrites\u00bb, each with a symbol; readers that wait for write access say \u00abonly with write access\u00bb. One button saves everything.<\/li>\n<li><strong>Refusals of the switch, the access level, the role and the fine-tuning lead to the place where they are changed.<\/strong> When write access is off, the connection's access level does not include a tool, the account lacks the capability, or a tool is switched off under Fine-tuning, the answer says why in one sentence, what the person can do, gives a direct link (to the switch, the fine-tuning, the connections or the users) and asks the assistant to pass it on kindly and try again afterwards. The same holds where a tool itself refuses because the account's role does not allow it \u2014 this post, this user's meta, publishing: the answer adds that an administrator can change the account's role under Users, with the link.<\/li>\n<li><strong>Tools of AlphaBridge MCP Pro are named as such.<\/strong> A call of a tool that belongs to the separate AlphaBridge MCP Pro or its Agency plan is answered with what it is and where it comes from instead of \u00abUnknown tool\u00bb, and the server instructions of a site without Pro say in a short paragraph what Pro adds. Nothing in this plugin is locked or limited by it.<\/li>\n<li><strong>New connections start with the full access level.<\/strong> The consent screen preselects \u00abFull\u00bb, and says that the switch for write access on the site decides whether assistants may write; an approval without a choice gets the full level too. Connections made before keep their level.<\/li>\n<li>The texts of the switch and the fine-tuning, the short names of the tools and the refusals for the account's role come in German with the plugin (de_DE, de_DE_formal, de_AT, de_CH, de_CH_informal); dates on the settings page follow the language.<\/li>\n<li>For add-ons: the action <code>ab_mcp_reset_switches<\/code> (write access switched on), the filters <code>ab_mcp_unavailable_tool_message<\/code> and <code>ab_mcp_tool_label<\/code> (a tool's short name), the action <code>ab_mcp_fine_save<\/code> (one save for the fine-tuning), the helpers <code>AB_MCP_Admin::fine_row_html()<\/code>, <code>fine_sub_html()<\/code>, <code>count_badges()<\/code> and <code>addon_text()<\/code>, and the class <code>AB_MCP_Guidance<\/code> with <code>role_refusal()<\/code>.<\/li>\n<\/ul>\n\n<h4>4.4.0<\/h4>\n\n<ul>\n<li><strong>Page builders: <code>wp_get_builder_layout<\/code> recognises the builder a page was made with and reads the page as an outline.<\/strong> For an account that may edit the post, it lists the page's elements in page order, each with its id, type and parent, and with its visible text, heading, HTML, link and image fields. Code, forms, global parts and elements it does not know are listed as locked, with the reason and without their content; the raw builder data, styling, attributes and scripts are never handed out. The answer also names the builder, whether it is active, what the site shows (<code>storage<\/code>), where copies of the page are kept, a hash of the layout to compare before and after a change, and the tools that change the page with a visible effect (<code>write_via<\/code>). Read, as of 1 October 2026: WordPress blocks, Elementor (classic and atomic elements), 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, Flatsome and Enfold \u2014 the last five from the vendors' documentation and code, not yet checked on a live installation, which the answer says. Further builders, among them Bricks, Breakdance, Oxygen and Divi 5, are recognised but not read; the dated list is in the FAQ. An Elementor element that Elementor has not registered is listed as locked with the way: the plugin that provides it; for a container while Elementor's Container feature is off, the switch under Elementor \u203a Settings \u203a Features; for an atomic element while Elementor's Atomic Editor is off, the switch under Elementor \u203a Settings \u203a Atomic Editor. A guided prompt, <code>edit_builder_page<\/code>, takes an assistant through recognising, reading, previewing, applying and checking a change.<\/li>\n<li><strong><code>wp_get_post<\/code> says which page builder a post was made with.<\/strong> The new field <code>built_with<\/code> names the builder, whether it is active, its version, what the site shows and the tools that change the page with a visible effect, with a note where post_content is not simply the page.<\/li>\n<li><strong><code>wp_list_posts<\/code> filters by page builder.<\/strong> <code>built_with<\/code> takes a builder id as <code>wp_get_post<\/code> names it, <code>any<\/code> for every known builder or <code>none<\/code> for posts without one. The totals count only matching posts, and each listed post names the builder found on it.<\/li>\n<li><strong><code>wp_update_post<\/code> refuses a change to the content only where the builder shows its own data.<\/strong> Where an active builder renders a page from its own data \u2014 Elementor, Beaver Builder, SiteOrigin Page Builder or Enfold, and only on a page that has such data \u2014 post_content is a copy the site does not show, so a change to it would not appear. Such a call is refused before anything is written, and the answer says how to change the page instead; title, status, excerpt and the other fields still change when the call leaves the content out. Where the builder is inactive, restores its own copy on its next save, or may or may not show its own data, the change is saved and the answer says what to expect.<\/li>\n<li><strong><code>wp_duplicate_post<\/code> copies a page with its custom fields and page builder data.<\/strong> A copy used to carry only title, content, excerpt, parent, order and terms, so a builder page came out as a text page. For an account that may edit the original, the copy now also gets the custom fields, the page template, the featured image and WordPress' list of removed hooked blocks. Page builder data \u2014 Elementor, Beaver Builder, SiteOrigin, Themify, Zion, Live Composer, Brizy, Visual Composer, SeedProd and Pagelayer \u2014 holds markup, so it is copied only for an account with the unfiltered_html capability, and each builder's keys together or not at all. Elementor elements get new ids where the layout can be read; otherwise it is copied unchanged, and the answer says so. Other builders' data is copied byte for byte, and the answer says so. Builder caches, credential-shaped keys, the original's editing state and other plugins' protected keys are not copied; the answer lists what stayed behind and why.<\/li>\n<li><strong>Hardening: page builder data in the <code>meta<\/code> argument needs the unfiltered_html capability.<\/strong> <code>wp_create_post<\/code> and <code>wp_update_post<\/code> wrote keys without \"_\" in which a page builder keeps markup or code \u2014 <code>panels_data<\/code>, <code>dslc_code<\/code>, <code>pagelayer-data<\/code>, <code>brizy<\/code>, <code>mfn-page-items<\/code>, <code>tve_updated_post<\/code> and others \u2014 for any account that may edit posts. For an account without unfiltered_html such a call is now refused before anything is written; the answer names who has the capability, the builder's own editor, the tools that change the page's texts, and the call without the key for the other fields. Other keys behave as before. Site owners can change the list with the <code>ab_mcp_builder_markup_meta_keys<\/code> filter.<\/li>\n<li><strong>MCP 2026-07-28 alongside the older revisions.<\/strong> The endpoint also speaks the stateless revision 2026-07-28: a request that names it in <code>_meta<\/code> is answered in it, with <code>server\/discover<\/code>, result types, cache hints and the checks of the <code>MCP-Protocol-Version<\/code>, <code>Mcp-Method<\/code> and <code>Mcp-Name<\/code> headers, and without a session. <code>initialize<\/code> and the requests of the revisions 2024-11-05, 2025-03-26 and 2025-06-18 are answered as before, apart from one new field in the site's self-description (<code>protocol_versions<\/code>). The newer revision can be switched off under Settings \u2192 AlphaBridge MCP \u2192 Your connections \u2192 \u00abMCP protocol 2026-07-28 (advanced)\u00bb, or with the <code>ab_mcp_modern_protocol<\/code> filter; the site then answers in the older revisions only.<\/li>\n<li><strong>Apps can identify themselves with a client metadata document (CIMD).<\/strong> Besides registering with the site (RFC 7591, unchanged), an app may give the HTTPS address of its client metadata document as its client id, the registration MCP 2026-07-28 prefers. The site fetches that document only once a logged-in user who may approve connections opens the consent screen: from public addresses only, without redirects, at most 5 KB within 5 seconds, kept for at most a day. The consent screen names the host it came from. It can be switched off under Settings \u2192 AlphaBridge MCP \u2192 Your connections \u2192 \u00abConnect from Claude (OAuth, advanced)\u00bb \u2192 \u00abAccept apps with a metadata document\u00bb, or with the <code>ab_mcp_oauth_cimd<\/code> filter, and it is off while WordPress blocks outgoing requests. Details under External services.<\/li>\n<li><strong>Read out of the box: the modes Read and Full.<\/strong> AlphaBridge MCP now starts in Read, on new sites and on every site after this update: assistants can read content, media, terms, comments, settings and the structure of the site; every tool that creates, changes or deletes is refused, <code>wp_undo<\/code> included, and so is every tool marked Mighty that reads code, files, the database, logs or credentials, with an answer saying why and that an administrator can switch to Full at the top of Settings \u2192 AlphaBridge MCP. That switch is the first thing on the page. Switching to Full takes a ticked box under a notice that it can be destructive and is at the site owner's own risk; the account, the time, the version and the wording of the notice and the plugin version are recorded in the plugin's settings and in its log, the last 20 switches also in a history that clearing the log leaves alone, and the page shows since when and by whom \u2014 or that code set Full and nobody confirmed it there. In Full every tool is on, the powerful ones marked Mighty included, unless an administrator switches it off under \u00abFine-tuning (for advanced users)\u00bb. Back to Read takes one click. The server instructions and the consent screen say when a site is in Read; the tools it refuses stay listed there, as writing tools did under the former read-only mode, and are refused when called. After the update, administrators see a notice that explains the change until one of them dismisses it or switches the mode. The global read-only switch is gone, Read replaces it; switches saved before no longer hold writing Mighty tools off, while a Mighty tool that only reads and was switched off stays off in Full until an administrator switches it on under Fine-tuning. The texts of the modes come in German with the plugin (de_DE, de_DE_formal, de_AT, de_CH, de_CH_informal); a language pack from translate.wordpress.org takes precedence. The access levels per connection (Read only, Content, Full) are unchanged.<\/li>\n<li><strong>The access levels on the consent screen are described.<\/strong> When an app connects, the consent screen offers Read only, Content and Full as a choice, each with one sentence on what the connection may then do and what not. Content stays preselected.<\/li>\n<li><strong>Refusals from AlphaBridge's own checks name the way.<\/strong> Where AlphaBridge itself refuses a call or reports a failure, the answer now says, beyond what did not work and why, what does: the tool that finds an id, the right it takes and who has it, the switch under Settings \u2192 AlphaBridge MCP \u2192 Fine-tuning, a wider access level when connecting, the values a parameter accepts, the filter a site owner can use \u2014 and, where WordPress gives no reason, how to check the result. Errors WordPress itself reports are passed on as WordPress words them. The rate limit names its figure. No limit, permission or behaviour changed.<\/li>\n<li><strong>The texts about the Pro add-on's undo give its current window:<\/strong> undo points expire after 7 days by default, adjustable from 1 to 30 days, in the description and in the box about AlphaBridge MCP Pro on the settings page.<\/li>\n<li>For add-ons: the builder interface is versioned by the constant <code>AB_MCP_BUILDER_API<\/code> (1), with the filters <code>ab_mcp_builder_adapters<\/code>, <code>ab_mcp_builder_signatures<\/code>, <code>ab_mcp_builder_block_profiles<\/code>, <code>ab_mcp_builder_write_via<\/code> and <code>ab_mcp_builder_content_update_guard<\/code>. <code>AB_MCP_Site_Mode<\/code> says which mode a site is in (<code>get()<\/code>, <code>is_full()<\/code>, <code>allows()<\/code>), and the action <code>ab_mcp_site_mode_changed<\/code> fires when an administrator switches. A connection with Content access may run an add-on's <code>wp_update_builder_element<\/code>.<\/li>\n<\/ul>\n\n<h4>4.3.11<\/h4>\n\n<ul>\n<li><strong>An invitation to the affiliate programme, on the settings page.<\/strong> One line in the side column, below the box about AlphaBridge MCP Pro: the commission \u2014 60% of every Pro and Agency sale you refer, renewals included \u2014 and a link to the programme's page on alphabridge-mcp.com, which has the full terms and says how to apply. The link opens in a new tab and carries no tracking. The commission comes from sales of the separately sold Pro and Agency editions; this free plugin itself earns none. Where the Pro add-on shows your own affiliate figures, it takes the line's place. No tool or setting changed.<\/li>\n<li>For add-ons: the filter <code>ab_mcp_affiliate_invite<\/code> decides whether the line shows.<\/li>\n<\/ul>\n\n<h4>4.3.10<\/h4>\n\n<ul>\n<li><strong>A new settings page: pick your assistant first, then follow its steps.<\/strong> The page opens with the plugin's logo, this site's state (connections, tools switched on, read-only mode) and a choice of assistant \u2014 Claude, ChatGPT, Cursor or another client. Each gets its own steps with direct links: for Claude into its connector directory, with this site's address ready to copy, the setup video and the step-by-step guide; for ChatGPT to its plugins page, with this site's endpoint. Creating a token is offered where one is needed \u2014 for Cursor and other clients \u2014 and no longer next to the ways that never use one. The page remembers the assistant you picked in your browser.<\/li>\n<li><strong>Capabilities with switches.<\/strong> One switch turns all tools on or off, one read-only mode, and every group has a switch of its own. Open a group to see each tool with what it does \u2014 the first sentence, the whole description behind the \u00abi\u00bb \u2014 and switch it on its own. A search finds a tool by name or description. A group that is partly on shows it; the bar at the bottom tells you when switches have changed and are not saved yet. What the form saves is unchanged.<\/li>\n<li>The connections now follow the capabilities, above the log. \u00ab1 tool\u00bb instead of \u00ab1 tools\u00bb.<\/li>\n<li>For add-ons: the side column has a place for their boxes (<code>ab_mcp_admin_side_boxes<\/code>), between the box about AlphaBridge MCP Pro and the guides.<\/li>\n<\/ul>\n\n<h4>4.3.9<\/h4>\n\n<ul>\n<li><strong>The box about AlphaBridge MCP Pro on the settings page says what Pro adds, how to try it and what it costs.<\/strong> It now stands at the top of the side column: what the separately sold plugin adds on this site, a button that starts the 7-day trial without a card, and the monthly and the yearly price. Each link opens the Freemius checkout, which sells AlphaBridge MCP Pro, for exactly what it names \u2014 trial, monthly or yearly \u2014 and carries no tracking. On a site where AlphaBridge MCP Pro runs with a valid Pro or Agency licence the box no longer shows; it offered what the site already had. Its look comes from a small stylesheet that ships with the plugin and loads only on this settings page; nothing is loaded from outside. No tool or setting changed: this free plugin remains complete and fully functional on its own.<\/li>\n<\/ul>\n\n<h4>4.3.8<\/h4>\n\n<ul>\n<li><strong><code>wp_update_post<\/code> saves a page whose page template is gone like any other.<\/strong> WordPress saves a post's page template along on every save; where that template no longer exists \u2014 after a theme switch, say \u2014 the tool reported \u00abInvalid page template\u00bb although the change was already saved, and the hooks after the save did not run: a scheduled post got no schedule, caches were not cleared. Now WordPress falls back to the default template, as the classic editor does, and finishes the save; the page already looked that way.<\/li>\n<\/ul>\n\n<h4>4.3.7<\/h4>\n\n<ul>\n<li><strong>In <code>wp_update_post<\/code>, a file that would take its visibility from its parent needs the right to publish \u2014 also through \u00abdraft\u00bb or another parent.<\/strong> WordPress stores a file with any status but \u00abprivate\u00bb, \u00abtrash\u00bb or \u00abauto-draft\u00bb as \u00abinherit\u00bb, and a file with \u00abinherit\u00bb is as visible as its parent: public without one, and public the moment the parent is published. <code>wp_update_post<\/code> asked for the right to publish only when the status asked for would publish, so an account without that right could make a private file public by asking for \u00abdraft\u00bb or \u00abpending\u00bb, or make a file that a draft kept hidden public by giving it another parent. Now a save that makes a file \u00abinherit\u00bb, or leaves a file \u00abinherit\u00bb or in the trash (from where it comes back as \u00abinherit\u00bb) under another parent, needs the right to publish \u2014 whatever the parent's status is now, since a draft that is published later shows the file too. The parent that counts is the one WordPress stores: none where a loop would run through the file, which any save can cause, a title alone included. A save that leaves status and parent as they are needs no such right. This is stricter than it would have to be in some cases, on purpose: an account without the  \u2026<\/li>\n<\/ul>","raw_excerpt":"Free MCP server for WordPress. Claude and ChatGPT write posts, add images and answer comments on your site. You decide when they may write.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/ml.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/337059","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ml.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/ml.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/ml.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=337059"}],"author":[{"embeddable":true,"href":"https:\/\/ml.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/cultureclub"}],"wp:attachment":[{"href":"https:\/\/ml.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=337059"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/ml.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=337059"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/ml.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=337059"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/ml.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=337059"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/ml.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=337059"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/ml.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=337059"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}