Title: AlphaBridge MCP – Connect Claude and ChatGPT to WordPress: MCP server with permissions per connection and audit log Author: cultureclub Published: جولای 30, 2026 Last modified: سپتامبر 30, 2026 --- Search plugins ![](https://ps.w.org/alphabridge-mcp/assets/banner-772x250.png?rev=3629098) ![](https://ps.w.org/alphabridge-mcp/assets/icon-256x256.png?rev=3629098) # AlphaBridge MCP – Connect Claude and ChatGPT to WordPress: MCP server with permissions per connection and audit log By [cultureclub](https://profiles.wordpress.org/cultureclub/) [Download](https://downloads.wordpress.org/plugin/alphabridge-mcp.4.3.9.zip) [Live Preview](https://azb.wordpress.org/plugins/alphabridge-mcp/?preview=1) * [Details](https://azb.wordpress.org/plugins/alphabridge-mcp/#description) * [Reviews](https://azb.wordpress.org/plugins/alphabridge-mcp/#reviews) * [Installation](https://azb.wordpress.org/plugins/alphabridge-mcp/#installation) * [Development](https://azb.wordpress.org/plugins/alphabridge-mcp/#developers) [Support](https://wordpress.org/support/plugin/alphabridge-mcp/) ## Description **Connect Claude and ChatGPT to WordPress — with the rights you choose.** AlphaBridge MCP turns your WordPress site into a native **MCP server** (Model Context Protocol). An AI assistant such as Claude — on Claude.ai, in Claude Desktop, Claude Code or Cursor — connects over one authenticated HTTPS endpoint and manages content, media, taxonomies, comments, widgets and site settings through structured tools that check WordPress permissions on every single call. ChatGPT connects the same way, as an MCP app on the Plus, Pro, Business, Enterprise and Edu plans. Tell Claude what you want done — “draft a post from these notes, add last week’s photos, file it under the right categories and schedule it for Friday” — and it happens on your site, not through screen-clicking or raw admin access. **You stay in control** Handing an AI the keys to your site should feel safe — so control comes first: * Every connection acts as a real WordPress user, and every tool checks the matching WordPress capability. What that user may not do, the AI cannot do. * Scoped connections: hand out a read-only or content-only key with an optional expiry instead of full access. Rotate a connection’s secret in one click. * Tool groups you can switch off entirely — disabled tools vanish from the MCP surface. Plus a global read-only mode. * An audit log records every tool call, and a fixed rate limit stops abusive request bursts. **Connected in two minutes** In Claude, connect «AlphaBridge MCP for WordPress» from the connector directory, enter your site’s address and approve on your own site’s login-protected consent screen — no address or token to copy (standard OAuth 2.1 with PKCE; the login is your WordPress login, no account with us). That entry runs through the AlphaBridge Connect hub described below; to connect directly, paste your endpoint URL into Claude as a custom connector instead. For clients without a Connect button, create a token manually and paste one ready-made config. ChatGPT connects the same way: add the endpoint as an MCP app (Plugins Add Create MCP app, authentication OAuth) and approve on your site — checked on 26 September 2026 with ChatGPT Pro, directly and through the hub. The whole way in one minute — install, connect from Claude’s directory, approve on your site, give Claude a first task: In German: [Claude mit WordPress verbinden](https://www.youtube.com/watch?v=M262gCOc7gM) **AlphaBridge Connect — the optional hub** The entry «AlphaBridge MCP for WordPress» in Claude’s connector directory is the hosted hub at connect.alphabridge-mcp.com: you enter your site’s address instead of copying the endpoint, and you approve the site on its own login screen. The site keeps its own rights and its own audit log. Through the hub, up to 10 sites work from one chat, in every edition including this free plugin: add a site from the chat and keep working in the same conversation. The hub is optional and free, and this plugin never contacts it on its own — the hub connects to your site for authorization, connection setup and management, and to forward the tool calls you make through it. It stores the site’s access key encrypted and passes content through without storing it; the details are in its privacy notice (https://connect.alphabridge-mcp. com/legal/privacy) and its data processing agreement (https://connect.alphabridge- mcp.com/legal/dpa). **Nothing extra to host** Unlike bridge-based solutions, AlphaBridge speaks MCP directly in PHP inside WordPress. With a direct connection there is no Node middleware, no external service and nothing else to run or pay for — it works on ordinary WordPress hosting, which makes it faster and more stable. The hub above is the one optional exception, and you choose whether to use it. **Free means free** Everything in this plugin is fully functional: no license keys, no registration, no plan-based, cumulative or time-based usage limits, no locked features. **What’s inside** * Native MCP endpoint (JSON-RPC 2.0 over HTTP POST; protocol versions 2024-11-05, 2025-03-26, 2025-06-18) — no external server required. * 39 structured tools across content, media, taxonomies, comments, widgets, site settings, site info, SEO reads and search. * Bearer-token authentication mapped to a real WordPress user, with per-tool capability checks. * Unlimited connections — create one deliberately limited key per client. **How it compares** A dated comparison with other WordPress MCP plugins, every cell checked against the vendors’ own pages: https://alphabridge-mcp.com/compare.html Need more? A separate commercial add-on, AlphaBridge MCP Pro, adds tool groups for the database, users, plugin and theme files, WooCommerce and migration, plus an undo for changes made through it (undo points expire after 24 hours). The Agency plan adds Site Deploy: files, themes and whole builds published onto your own hosting over SFTP; ZIP deploys can run atomically, with rollback when the swap fails. Both are entirely optional — this free plugin is complete on its own and stays fully functional without them. Details are on the plugin website. AlphaBridge is our own product brand for this project. MCP (Model Context Protocol) is an open protocol standard; this plugin is an independent implementation and is not affiliated with or endorsed by the protocol’s authors or by any other vendor. ### External services This plugin makes no automatic outbound requests and sends no telemetry. One tool can contact an external address, and only on your explicit instruction: when you call `wp_upload_media_from_url` with a URL, the plugin downloads that file from the address you provide (and up to a few safely re-validated redirects; SSRF-guarded, type- and size-checked). The plugin itself initiates no other outbound requests. ## Screenshots [⌊Set up the Claude connector in two steps: copy the endpoint URL, then connect from Claude — or create a token manually for Cursor, Claude Code and scripts. Existing connections are listed and managed in the same place.⌉⌊Set up the Claude connector in two steps: copy the endpoint URL, then connect from Claude — or create a token manually for Cursor, Claude Code and scripts. Existing connections are listed and managed in the same place.⌉[ Set up the Claude connector in two steps: copy the endpoint URL, then connect from Claude — or create a token manually for Cursor, Claude Code and scripts. Existing connections are listed and managed in the same place. [⌊The moment you create a connection, the plugin shows what you need once — the Bearer token and a copy-paste config for Cursor / Claude Code, and the connector URL if connector-URL authentication is switched on — with a reminder to save it, because the token is shown in full only once.⌉⌊The moment you create a connection, the plugin shows what you need once — the Bearer token and a copy-paste config for Cursor / Claude Code, and the connector URL if connector-URL authentication is switched on — with a reminder to save it, because the token is shown in full only once.⌉[ The moment you create a connection, the plugin shows what you need once — the Bearer token and a copy-paste config for Cursor / Claude Code, and the connector URL if connector-URL authentication is switched on — with a reminder to save it, because the token is shown in full only once. [⌊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.⌉⌊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.⌉[ 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. [⌊Enable or disable tools by functional group. Powerful ("mighty") tools are off by default, and one switch turns on a global read-only mode.⌉⌊Enable or disable tools by functional group. Powerful ("mighty") tools are off by default, and one switch turns on a global read-only mode.⌉[ Enable or disable tools by functional group. Powerful (“mighty”) tools are off by default, and one switch turns on a global read-only mode. [⌊Connect from Claude is on by default: Claude discovers the site, you approve on a login-protected consent screen, and the approved connection appears in the list, revocable any time. Switching it off removes the OAuth endpoints.⌉⌊Connect from Claude is on by default: Claude discovers the site, you approve on a login-protected consent screen, and the approved connection appears in the list, revocable any time. Switching it off removes the OAuth endpoints.⌉[ Connect from Claude is on by default: Claude discovers the site, you approve on a login-protected consent screen, and the approved connection appears in the list, revocable any time. Switching it off removes the OAuth endpoints. [⌊Connector-URL authentication is off by default, because a token in a URL leaks more easily than one in a header; the setting explains the trade-off before you switch it on.⌉⌊Connector-URL authentication is off by default, because a token in a URL leaks more easily than one in a header; the setting explains the trade-off before you switch it on.⌉[ Connector-URL authentication is off by default, because a token in a URL leaks more easily than one in a header; the setting explains the trade-off before you switch it on. ## Installation 1. Upload the `alphabridge-mcp` folder to `/wp-content/plugins/` (or install the ZIP via Plugins Add New Upload). 2. Activate the plugin. 3. In 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. Done. To connect directly, without the AlphaBridge Connect hub in between, add a custom connector with the endpoint `https://your-site.tld/wp- json/alphabridge/v1/mcp` instead. In ChatGPT: Plugins Add Create MCP app with the endpoint and OAuth. 4. For clients without a Connect button (Cursor, Claude Code, scripts): open **Settings AlphaBridge MCP**, create a connection manually and copy its token. ## FAQ ### Is it secure? Every request needs a token bound to a WordPress user; each tool enforces the matching WordPress capability, including object-level checks for the specific post, attachment or taxonomy (non-public taxonomies additionally require that taxonomy’s own capability). Powerful tools are off by default and only run once the admin enables their group. All calls are logged. Arbitrary option or transient values cannot be read through this plugin at all — only a fixed list of common site settings is exposed. Post, term and user meta is layered-protected: protected (“_”-prefixed) keys, keys flagged by is_protected_meta(), and two kinds of credential-shaped key are refused: keys whose whole name is a credential word, singular or plural (token, secret, password, passphrase, passcode, pwd, otp, credential), and keys containing one of a fixed list of compound credential patterns (api_key, access_token, client_secret, license_key, oauth, _token, _secret, _password, passwd, …). Case and surrounding whitespace are ignored. The list is matched literally, which makes this guard deliberately conservative rather than exhaustive: token_count, password_hint, credential_type, api_version, counters such as maxTokens and camelCase spellings such as accessToken all pass it, and the layers around it do the real work — and every generic post, term and user meta read or write additionally passes WordPress’s own per-key meta capability( edit_post_meta / edit_term_meta / edit_user_meta), which honours auth_callback rules that other plugins register via register_meta() (the media and SEO tools read only their own fixed keys). A key you may not edit is not exposed over MCP either. Tokens are accepted via the Authorization or X-Api-Key header — header authentication is the default. An admin can optionally enable a connector URL that carries the token in its path (served with Referrer-Policy: no-referrer and Cache-Control: no-store); this is off by default, because a token in a URL leaks more easily. Query-string tokens are never accepted. If you turn the connector URL on, treat it like a password: it contains the token — rotate the connection if the URL is shared, logged or pasted anywhere. ### Does it work on shared hosting? Yes. It is pure PHP and uses the WordPress REST API. PHP 8.0+ and HTTPS are recommended. ### Is the free plugin limited? No. Every feature in this plugin works without payment, registration or license keys, and there are no plan-based, cumulative or time-based usage limits. A uniform security throttle (120 requests/minute, identical for every user) protects your server from abusive request bursts. ### Does the plugin send data anywhere? No. It contacts no external service on its own. The only outbound request happens when you explicitly ask a tool to fetch a file from a URL you provide (see External services). ## Reviews There are no reviews for this plugin. ## Contributors & Developers “AlphaBridge MCP – Connect Claude and ChatGPT to WordPress: MCP server with permissions per connection and audit log” is open source software. The following people have contributed to this plugin. Contributors * [ cultureclub ](https://profiles.wordpress.org/cultureclub/) [Translate “AlphaBridge MCP – Connect Claude and ChatGPT to WordPress: MCP server with permissions per connection and audit log” into your language.](https://translate.wordpress.org/projects/wp-plugins/alphabridge-mcp) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/alphabridge-mcp/), check out the [SVN repository](https://plugins.svn.wordpress.org/alphabridge-mcp/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/alphabridge-mcp/) by [RSS](https://plugins.trac.wordpress.org/log/alphabridge-mcp/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 4.3.9 * **The box about AlphaBridge MCP Pro on the settings page says what Pro adds, how to try it and what it costs.** 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— trial, monthly or yearly — 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. #### 4.3.8 * **`wp_update_post` saves a page whose page template is gone like any other.** WordPress saves a post’s page template along on every save; where that template no longer exists — after a theme switch, say — the tool reported «Invalid page template» 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. #### 4.3.7 * **In `wp_update_post`, a file that would take its visibility from its parent needs the right to publish — also through «draft» or another parent.** WordPress stores a file with any status but «private», «trash» or «auto-draft» as «inherit», and a file with «inherit» is as visible as its parent: public without one, and public the moment the parent is published. `wp_update_post` 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 «draft» or «pending», or make a file that a draft kept hidden public by giving it another parent. Now a save that makes a file «inherit», or leaves a file «inherit» or in the trash( from where it comes back as «inherit») under another parent, needs the right to publish — 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 right to publish can no longer move a file from one published post to another. «Visible» means the attachment page, the file’s entry in the REST API and its title, caption and description: WordPress never protects the uploaded file itself, whose address stays reachable. * **`wp_create_post` and `wp_duplicate_post` make no files.** A file created or copied there had no file behind it: an attachment page with whatever text was given, stored as «inherit» — public without a parent — and a copy of a private file showed its title, caption and description. Files are added with `wp_upload_media` or `wp_upload_media_from_url`. A copy WordPress could not save is now reported as an error; it came back as a copy with the id 0. * **A parent must be a post id.** `wp_update_post` took a parent given as null or a list as none — a file came off its post, a page moved to the top level — and `wp_create_post` took a list as post 1. Both are refused now. A file goes under another post only where the account may edit that post, as with the upload tools, and never under a revision or another file. * **A post in the trash that `wp_update_post` gives a status comes out the way WordPress takes one out:** its comments get their states back, the notes the trash keeps are removed, and the hooks other plugins listen to run; a plugin may also keep it in the trash. It is still one save, with the status, date and fields asked for. * **`wp_update_media` reports a save that failed** instead of «updated», and follows the rule of `wp_update_post` for files. * **`wp_delete_post` puts every kind of post into the trash unless `force` is set.** It promised the trash, but WordPress moves only posts and pages there: a product, an event or a post of any other type was deleted for good, and a file together with the file on the server. Without `force` any post now goes to the trash. A file is deleted with `wp_delete_media` or with `force`, since the media library has no trash unless a site turns it on. A post already in the trash, or on a site without a trash, needs `force` to be deleted for good. #### 4.3.6 * In the connections list, the time a connection was last used and an expiry still ahead are shown as the site’s date and time in digits, to the minute, for example« 2026-09-27 12:52» — the form of the log below, which adds the seconds. They were phrases such as «2 weeks ago» and «in 3 days»: WordPress translates the time span, the words around it come from this plugin, and a site whose language this plugin has no translation for yet mixed the two — a German site read «2 Wochen ago». «never», «expired» and the dash for a connection not used yet stay as they were. Found while recording a setup video on 27 September 2026. * The steps for Claude start with the simplest way: «AlphaBridge MCP for WordPress» in Claude’s connector directory, where you enter your site’s address instead of copying the endpoint; it connects through the AlphaBridge Connect hub. The settings screen shows that way first, with this site’s address, while connecting from Claude (OAuth) is switched on — the hub signs in through it. The direct way, a custom connector with the endpoint, follows as the way without the hub. * The steps for Claude no longer spell out its menus. Claude has rearranged them— Connectors now sit under «Customize», and a custom connector is added through an «Add» menu — so the settings screen, the notice after saving the tool selection and the installation steps, which pointed to «Settings Connectors», no longer matched what Claude shows. The settings screen and the installation steps now say to open Connectors in Claude and add a custom connector there. The notice after saving says where in Claude to make a change visible: in Connectors, refresh the connector’s tool list — new in the notice — or disconnect and connect again. * `wp_list_posts` keeps a steady order when several posts share the same date to the second, as posts created by an import or a script often do. Such posts came back in whatever order the database chose, which could change from one call to the next, so paging through a list could show one of them twice and leave another out. Posts that tie on the field being sorted by — date, title, modified or menu order — are now also sorted by their id, in the same direction, so a tie no longer shifts posts between pages. Sorting by id is unchanged. Found while recording a setup video on 27 September 2026, on a demo site where several posts carry the same date. * `wp_update_post` takes a date, in the forms `wp_create_post` takes: site time, or RFC 3339 with an offset. Neither tool publishes a post, or takes one off the site, unless the call asks for it. WordPress decides between «publish» and «future» by the date: a post saved as «future» whose date is not at least a minute ahead is published at once. Until now «future» without a date did exactly that to a draft, which takes the time of the save. Such a save is now refused before anything is written, with the date it would have had and what to pass instead — a later date to schedule, status «publish» to publish, status «future» to schedule a published post. An edit to a scheduled post whose date has passed is refused the same way rather than publishing it. Both tools schedule a post only for a date at least five minutes ahead: WordPress publishes a scheduled post at once whenever it is saved less than a minute before its date, and a schedule closer than that margin could be lost to a save still running, or to another plugin saving the same post again. When `wp_update_post` publishes a draft that has no date of its own, or `wp_create_post` publishes a post without a date, the plugin dates it at the save, the local and the UTC time taken from one reading of the clock; WordPress would derive the UTC time from the local one, which is an hour off in the hour the clocks go back. A date that would schedule a published post needs the right to publish, as asking for «future» does. In `wp_update_post` a status passed as null is refused too; WordPress would have stored it as «draft». Found on 28 September 2026 while checking what the setup video had turned up. * `wp_list_media` keeps a steady order in the same way. Files uploaded in the same second — a batch, an import — came back in whatever order the database chose, so paging through the media library could show one of them twice and leave another out. Without a search they are now also sorted by their id, newest first. A search keeps WordPress’ own order by relevance, which WordPress applies only when no order is named. #### 4.3.5 * A request for a review on WordPress.org, on the plugin’s own settings page only. It appears once a site has been using the plugin for at least 14 days and has made at least 50 successful tool calls, links to the review form (whatever your verdict), and stays on that page until «Don’t ask again» ends it for good — also across updates, and no tool call that is still counting can undo it. The counter stops once 50 successful calls are stored, so counting is a small, bounded cost rather than a write per call; nothing is sent anywhere. * Times on the settings screen follow the site’s timezone. «Last used» in the connections list measured against the site’s local clock instead of real time and was off by the site’s UTC offset: on a site in Central European summer time, a connection used a minute ago read «2 hours ago». The log showed the UTC clock without saying so. Both now read like every other time in WordPress. * A connection made by approving an app on this site is labelled with the app’s name and «OAuth», for example «ChatGPT · OAuth», instead of «… · Claude Connect», which put Claude’s name on every app that connects this way. A connection through AlphaBridge Connect keeps that name alone. Existing connections keep the label they were given. * The connections list marks an older connection when the same app has connected again for the same user. ChatGPT’s «reconnect», for one, leaves the earlier connection working. Nothing is removed automatically, because a second connection of the same app can be wanted; compare «Last used» and delete the one no longer in use. Only connections made from this version on can be matched. * Post, media, revision and comment dates in the tools’ answers are in the site’s time with the UTC offset written out, for example «2026-06-16T09:00:00+02:00». They used to be the UTC time without saying so: a post published at 09:00 in Zurich read as 07:00. A draft whose date is not fixed yet shows its local date instead of «0000-00-00 00:00:00»; no date at all is null. A date whose offset has seconds, like Zurich before 1894, or that would leave the years 1 to 9999 in site time, is given in UTC («…Z»). wp_create_post takes this form as well as site time as before. A date it cannot use is refused with the reason: no such day, a time the clocks skip, a year out of range, or a time where they go back that WordPress would read, and schedule, as the other of the two. * Uninstalling the plugin now also removes the list of apps that registered with the site to connect through OAuth — their names, return addresses and when they registered and last connected; that list stayed in the database until now. On a network, uninstalling now cleans every site: it stopped after the first 100, and the sites beyond kept their connections and settings. #### 4.3.4 * The capabilities screen says what to do after saving: a client that is already connected may cache the tool list it loaded, and this endpoint offers no server- initiated stream, so it cannot push `notifications/tools/list_changed`; if a change is not visible in such a client, refresh its tool list or reconnect it. The message after saving and a note under the Save button say so. Found by the acceptance test of 25 September 2026, where a newly enabled tool stayed invisible to a connected client until it reconnected. * Widget ids are trimmed and matched to the end of the string. An id such as `text- 2` followed by a newline was split into its base and number (the pattern ended in `$`, which also matches before a trailing newline) but never found in the sidebar map, so a delete removed the settings row and left the sidebar entry behind. Found while re-reading the widget tools after the September 2026 security review. * `wp_upload_media_from_url` now says what it does. The site itself downloads the file from a public http(s) URL through WordPress’ safe-URL check (private and internal hosts refused unless WordPress itself allows them, such as the site’s own host; checked on every redirect), with at most 3 redirects, 20 seconds per request and 20 MB by default; the URL or the content type must say JPEG, PNG, GIF, WebP or PDF, and WordPress then checks the file as for any upload. Behaviour unchanged; the description is what Claude reads before choosing a tool, and the automatic check in Anthropic’s connector portal asked for a description that names the source. #### 4.3.3 * **Security: a connection for another user can only be created by someone who may edit that user.** The token form accepted any user id: an administrator could issue a full-access connection in the name of any account — on a multisite network also in the name of a network administrator, whose rights a site administrator does not have — and rotating an existing entry had the same gap. Creating and rotating now require WordPress’ own `edit_user` right for the account the connection acts as; on multisite a network administrator’s connection can only be issued by a network administrator. Existing entries are left as they are: if connections for other users exist, look through the list. Found by an external code review in September 2026. * **Security: password-protected posts no longer hand out their text to every token whose user may edit posts at all.** `wp_get_post` and `wp_duplicate_post` checked` read_post`, which for a published post means “may read the site” and does not look at the post password; a revision of such a post carries the text but never the password, so it had the same gap. Both tools now require the right to edit the post when a password is set, and a revision — its text as well as its excerpt in any listing — is available only to someone who may edit its parent, the rule the WordPress REST API applies in its edit context. `wp_list_revisions` follows the same rule, `wp_list_posts` lists revisions only for one post at a time and only for someone who may edit it, and `wp_search` does not search revisions at all — a bare count of matches would already tell of the text. Same review. * **Hardening: the pending-consent record of a Claude connection is signed.** The record that carries user, scope and PKCE challenge from the consent page to the token endpoint lives in WordPress’ transient store, which every plugin and any generic “set transient” tool can write to. It now carries a signature over its fields and its storage key, made with the site’s auth salt; the token endpoint refuses a record without a valid signature, one older than a code’s two minutes, or one naming an unknown scope. Consent records written before the update are refused too; they live for two minutes, so at most a connection started during the update has to be started again. Same review. #### 4.3.2 * **Change: the rate limit on client registration is thirty per sender and hour instead of ten, and the hour now starts over on its own.** The public registration endpoint (RFC 7591) counts requests per sender address. Until now every request that passed the limit gave the counter a fresh hour, so the count only started over after an hour without such a request: ten registrations, each less than an hour after the one before, reached the limit even when spread over an afternoon, and further registrations from that address were refused until an hour after the tenth. The count now starts over one hour after the first request it counted. A registration grants no access by itself, and `MAX_CLIENTS` with eviction keeps the client store from filling up. #### 4.3.1 * **Fix: four tools told MCP clients they only add data, while they overwrite it.**` wp_update_post`, `wp_update_media`, `wp_update_term` and `wp_moderate_comment` reported `destructiveHint: false`, which the Model Context Protocol defines as“ performs only additive updates”. Clients use that hint to decide whether to ask you before a call, so an overwrite could run without a prompt. All four now report` destructiveHint: true`. The hint no longer comes from the “off by default” flag, which answers a different question: anything that writes counts as destructive unless it only ever adds (create, upload, duplicate, reply). #### 4.3.0 * **Breaking (Pro): the WooCommerce tools are renamed.** `wc_list_orders` becomes` wp_wc_list_orders`, and so on for all nine. Same reason as below, and the same one-time move of any per-tool on/off override you had set. * **Breaking: the two SEO tools are renamed.** `seo_detect` becomes `wp_seo_detect` and `seo_get` becomes `wp_seo_get`. Every other tool already carried the `wp_` prefix; these two did not. The prefix is what keeps a WordPress tool from colliding with a same-named tool from another CMS when a client reaches several sites at once — without it, two different tools merge into one and one of the two sites gets a description that does not fit it. If you have saved instructions or automations that call the tools by name, change those two names. Nothing else about what they do has changed. If you had switched one of them off in the settings, it stays off — the stored override moves to the new name during the update. * New: a revocation endpoint (RFC 7009) at `/wp-json/alphabridge/v1/oauth/revoke`. A client that holds a connection token can now hand it back and end the connection itself, instead of the connection lingering until somebody deletes it in the settings. The endpoint is announced in the discovery document, so clients find it without being told the path. It answers the same way whether or not the token existed, which is what the standard requires: the answer must not reveal whether a token is valid. * New: the `initialize` response now carries a short self-description under `_meta`— which CMS answered, its version, the plugin version, the licensed edition and the scope of the token that was used. A hub or client that speaks to several sites can tell them apart without guessing from version strings. Nothing about your content is included. * Change: a connection created through AlphaBridge Connect is now labelled with that name alone in the connections list, instead of “AlphaBridge Connect · Claude Connect”. #### 4.2.3 * Fix: a backslash in a title, name, description, comment or custom field was silently dropped when writing. WordPress expects the data it is given to be escaped and removes one level of escaping itself, so passing it through unchanged turned “ C:\Docs” into “C:Docs” — with no error anywhere. Every write path now escapes what it hands over: posts and pages, media titles and alt text, terms, post meta and comments. Values without a backslash are unaffected, and nothing already stored changes. #### 4.2.2 * Hardening: the meta-key credential guard now refuses keys whose whole name is a bare credential word — token, secret, password, passphrase, passcode, pwd, otp, credential, and their plurals. Previously only compound patterns such as api_token or client_secret were caught, so a key named exactly “token” could be read or written by a user who already held the key’s own edit capability. The compound list itself is unchanged apart from license_key, so everything 4.2.0 refused stays refused and no ordinary key changes behaviour. If one of your fields is named exactly like one of those words, its value stays untouched in the database but is no longer readable or writable over MCP. * Docs: the security answer in the FAQ now describes the rule exactly — which names are refused as a whole, that the compound list is matched literally, and where the guard deliberately stops — instead of implying that any key containing “token” or “secret” is refused. #### 4.2.0 * New: Connect from Claude. The site now speaks the OAuth flow MCP clients expect: add the endpoint URL in Claude (web, desktop or mobile) and click Connect — Claude discovers the site, you approve on a login-protected consent screen (choosing full, content-only or read-only access), and the approved connection appears in the connections list like any other, revocable at any time. Technically: RFC 9728/8414 discovery metadata under /.well-known/, dynamic client registration( RFC 7591), authorization-code grant with PKCE (S256 required) and resource indication( RFC 8707); 401 responses point clients at the metadata via WWW-Authenticate. Issued tokens are ordinary hashed connection tokens — nothing new is stored in readable form. No account with us, no external service: the login is your own WordPress login. Can be switched off under “Connect from Claude (OAuth, advanced)”; manual tokens keep working unchanged. #### 4.1.6 * The connector URL is now only offered once connector-URL authentication is actually enabled — if it is off, a one-click “Enable and show the connector URL” button( with the same security note as the setting itself) appears in its place. A copied connector URL therefore always authenticates; previously the URL was shown with only a small note and would be rejected until the setting was switched on. The Bearer token and the Cursor / Claude Code config are unaffected and always work. #### 4.1.5 * When you create a connection, the settings screen now shows everything ready for copy-paste: the full connector URL with the token embedded (for Claude.ai), the Bearer token, and a ready-made config snippet for Cursor / Claude Code — plus a clear reminder to save it, because the token is shown in full only once. #### 4.1.4 * Simpler, clearer connector setup: the settings screen now shows one “Claude.ai Connector” box with a two-step flow — copy the endpoint, then click one “Create connection” button (label, access scope, user and expiry moved into optional advanced settings). The token appears right below the button, and existing connections are listed in the same box. Removes the previous duplicate create buttons. #### 4.1.3 * Uninstall no longer removes this plugin’s data while the separately distributed AlphaBridge MCP Pro plugin is still installed — Pro shares this core data (connections, tool state, settings, log), so removing the free plugin alone keeps Pro fully configured. Uninstalling last (or alone) cleans up as before. #### 4.1.2 * Added an informational box about the separately distributed AlphaBridge MCP Pro plugin to the plugin’s own settings page. Nothing in this free plugin changed— it remains complete and fully functional on its own. #### 4.1.1 * Hardened connection handling: the token is shown once at creation and only its hash is stored; scope values are validated fail-closed; header authentication is the default and connector-URL authentication is an explicit opt-in. * User-meta reads limited to a fixed list of standard profile fields. * Improved capability checks and packaging consistency. #### 4.1.0 * Added connection scopes, an optional expiry and one-click rotation. * Improved transport and object-level security. #### 4.0.0 * Rebuilt the directory package as a fully standalone free plugin. * Connections are unlimited and every bundled tool is available without restriction. * Removed the raw option/transient readers; site settings are available through wp_get_site_settings. * Update status is read from WordPress’s cache and performs no remote request. * Broadened object-level and per-key capability checks across posts, meta, terms, taxonomies, media and search. * Simplified the settings screen and the distribution package. #### 3.0.0 * MCP tool annotations (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) for every tool. * MCP protocol negotiation: the server echoes the client’s requested protocol version when supported (2024-11-05, 2025-03-26, 2025-06-18). * New global read-only mode: one switch blocks every writing tool; read, list and search tools keep working. * Better error messages: argument validation reports all missing or invalid fields at once. #### 2.0.0 * Restructured for the WordPress.org directory: this plugin contains the core free toolset. * Settings-screen JavaScript is enqueued from assets/admin.js (2.0.2). #### 1.x * Initial development line: MCP endpoint, token auth, tool groups, security hardening( SSRF guards, path traversal guards, capability checks, rate limiting, audit log), 26 bundled translations. ## Meta * Version **4.3.9** * Last updated **1 ساعات ago** * Active installations **10+** * WordPress version ** 6.5 or higher ** * Tested up to **7.1.2** * PHP version ** 8.0 or higher ** * Language * [English (US)](https://wordpress.org/plugins/alphabridge-mcp/) * Tags * [AI](https://azb.wordpress.org/plugins/tags/ai/)[ChatGPT](https://azb.wordpress.org/plugins/tags/chatgpt/) [Claude](https://azb.wordpress.org/plugins/tags/claude/)[mcp](https://azb.wordpress.org/plugins/tags/mcp/) [mcp-server](https://azb.wordpress.org/plugins/tags/mcp-server/) * [Advanced View](https://azb.wordpress.org/plugins/alphabridge-mcp/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/alphabridge-mcp/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/alphabridge-mcp/reviews/) ## Contributors * [ cultureclub ](https://profiles.wordpress.org/cultureclub/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/alphabridge-mcp/)