Connect ChatGPT, Claude or another AI assistant to your WordPress site, then ask it to do the work you would otherwise do by hand.<\/p>\n\n
Connecting takes one address and a sign-in. There are no API keys to create, no client IDs to copy and nothing to paste into a configuration file. Claude and ChatGPT identify themselves automatically, using the published client metadata the Model Context Protocol defines for exactly this, and you approve the connection on your own site.<\/p>\n\n
Ask it to draft and publish a post, update product prices in WooCommerce, rewrite the SEO titles on a slow page, tidy your menus, or clear out spam comments. It works on your site directly, so there is no copying and pasting between a chat window and your admin screens.<\/p>\n\n
You decide what it may touch. Access is granted with a profile, which is a named set of tools: read only, content editing, SEO, store management, or one you build yourself. Everything the assistant does still runs through WordPress's own permissions, so it can never do more than the account it signed in as.<\/p>\n\n
81 WordPress core, 78 Rank Math SEO, 74 WooCommerce, 71 Elementor (36 free and 35 Pro), 35 Jetpack, 29 Yoast SEO and 20 Contact Form 7. Tools for a plugin appear only when that plugin is active, so the list stays as short as your site is.<\/p>\n\n
Written for the specific plugin, not guessed at. Rank Math's focus keywords, Elementor's page structure and WooCommerce's variations each store data their own way, and each tool is built for how that plugin actually works.<\/p>\n\n
This plugin talks to your site and nothing else. No data is sent to Cascadia Web Services or to any third party.<\/p>\n\n
For editors that cannot connect to a remote MCP server themselves, the plugin includes an optional Node.js bridge script that runs on your own computer. It passes requests between the editor and your site's REST API at:<\/p>\n\n
https:\/\/yoursite.com\/wp-json\/mountdev-ai-mcp-connector\/v1\/messages<\/code><\/li>\nhttps:\/\/yoursite.com\/wp-json\/mountdev-ai-mcp-connector\/v1\/oauth\/*<\/code><\/li>\n<\/ul>\n\nIt sends your WordPress username and Application Password to authenticate, along with whatever the assistant is asking for. Everything stays between your computer and your own server.<\/p>\n\n
License<\/h3>\n\n
This plugin is licensed under the GPL v3 or later.<\/p>\n\n
See https:\/\/www.gnu.org\/licenses\/gpl-3.0.en.html for details.<\/p>\n\n\n
\n- Install and activate the plugin.<\/li>\n
- Go to Settings - MCP Connector<\/strong>.<\/li>\n
- Copy the address shown on the page.<\/li>\n
- In ChatGPT or Claude, add it as a custom connector and sign in when asked.<\/li>\n
- Choose a profile, so the assistant knows what it may do.<\/li>\n<\/ol>\n\n
ChatGPT and Claude<\/h4>\n\n\n- Copy the address from Settings - MCP Connector<\/strong>.<\/li>\n
- In ChatGPT or Claude, open Settings, then Connectors, and add a custom connector with that address. Leave any Client ID and Secret fields empty.<\/li>\n
- Sign in to WordPress when the window opens, and approve the request. The approval screen names the app asking and the domain that published it.<\/li>\n
- Open the Access<\/strong> tab and choose what the assistant may do.<\/li>\n<\/ol>\n\n
If you prefer to issue credentials yourself, the OAuth<\/strong> tab still generates a Client ID and Secret, and connectors set up that way keep working.<\/p>\n\nCursor, Windsurf and other editors<\/h4>\n\n\n- Create an Application Password under Users - Profile<\/strong>.<\/li>\n
- Use the Client Setup<\/strong> tab to generate the configuration file for your editor.<\/li>\n<\/ol>\n\n\n
\nDo I need to be technical to use this?<\/h3><\/dt>\nNo. Copy one address from the plugin into your assistant, sign in, and pick what it may do.<\/p><\/dd>\n
Can it change things I did not ask it to?<\/h3><\/dt>\nIt can only use the tools in the profile you chose, and only within the permissions of the WordPress account that signed in. A read-only profile cannot publish, edit or delete anything.<\/p><\/dd>\n
Is my content sent to anyone?<\/h3><\/dt>\nNo. Your assistant talks to your site directly. Nothing goes to us or to any third party.<\/p><\/dd>\n
Do I need WooCommerce, Rank Math or Elementor?<\/h3><\/dt>\nNo. Tools for a plugin appear only if that plugin is active. The plugin works on a plain WordPress site.<\/p><\/dd>\n
Do I need an API key or a client ID?<\/h3><\/dt>\nNo. Claude and ChatGPT identify themselves with a metadata document they publish, so you paste the address and sign in. Issuing your own credentials is still supported for clients that need it.<\/p><\/dd>\n
What is MCP?<\/h3><\/dt>\nThe Model Context Protocol is an open standard for connecting AI assistants to outside tools and data. This plugin makes your WordPress site one of those tools.<\/p><\/dd>\n
What happens if I deactivate the plugin?<\/h3><\/dt>\nThe connection stops working. Nothing on your site is changed or removed.<\/p><\/dd>\n
Can several people connect?<\/h3><\/dt>\nYes. Each person signs in as themselves, and what they can do follows their own WordPress role.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.6.9<\/h4>\n\n\n- Changed: Deleting the plugin now removes everything it stored: profiles, settings, OAuth credentials, tokens and the key they were encrypted with. Until now these were left behind, so a site that had removed the plugin still held credentials that could authorize an assistant against it. Deactivating changes nothing; only deleting does this, and reconnecting after a delete means setting the connection up again<\/li>\n
- Note: Your posts, products, media and anything an assistant created are your site's own content and are never touched<\/li>\n<\/ul>\n\n
1.6.8<\/h4>\n\n\n- Fixed: A GET request to the MCP endpoint returned the authorization server metadata with HTTP 200 instead of the 401 challenge. Clients following the MCP authorization spec, ChatGPT among them, probe the endpoint first and expect that challenge to find the protected resource metadata. Reaching the authorization metadata this way left ChatGPT reporting that PKCE support was not advertised, even though it was. Reported on parsiagent.ir against 1.6.7<\/li>\n
- Added: Claude and ChatGPT can now connect with your site address alone. They identify themselves with a published metadata document (CIMD, per MCP SEP-991), so there are no credentials to generate first. Connections using generated credentials are unaffected<\/li>\n
- Added: The approval screen names the app asking for access, says which domain published it, and says so plainly when the app is running on your own computer<\/li>\n
- Changed: The settings screen uses WordPress's own layout and styling<\/li>\n
- Changed: Promotional banners and the advertising sidebar removed<\/li>\n
- Changed: The page opens on Quick Start instead of the FAQ, and the Profiles tab is now called Access<\/li>\n
- Fixed: The tool count said 389; there are 388 (81 WordPress core, not 82)<\/li>\n
- Changed: Readme rewritten in plain language<\/li>\n
- Note: Existing connections keep working and do not need setting up again<\/li>\n<\/ul>\n\n
1.6.7<\/h4>\n\n\n- Fixed: ChatGPT connectors failed with \"OAuth authorization server metadata must advertise PKCE support with code_challenge_methods_supported containing S256\". The plugin did not implement RFC 9728 Protected Resource Metadata, and the 401
WWW-Authenticate<\/code> header's resource_metadata<\/code> pointed at the authorization server metadata instead. It is now served at \/.well-known\/oauth-protected-resource\/wp-json\/mountdev-ai-mcp-connector\/v1\/messages<\/code> (and \/.well-known\/oauth-protected-resource<\/code>), and authorization_servers<\/code> leads clients to the existing metadata<\/li>\n- Fixed: 401 responses for an expired or invalid access token now carry the
WWW-Authenticate<\/code> challenge too<\/li>\n- Fixed: The token endpoint now accepts client credentials sent with HTTP Basic authentication (
client_secret_basic<\/code>), which the metadata already advertised<\/li>\n- Security: A
client_secret<\/code> sent with a PKCE token or refresh request is now verified. Previously a wrong secret was ignored when PKCE succeeded<\/li>\n- Note: If a client is configured with a Client Secret, it must be the current one shown in the OAuth settings. Clients that send no secret are unaffected<\/li>\n<\/ul>\n\n
1.6.6<\/h4>\n\n\n- Security: Fixed an authenticated broken access control vulnerability affecting every tool that takes an object ID. Only the single broad capability on each tool definition (
read<\/code>, edit_posts<\/code>, delete_posts<\/code>) was checked, never the caller's rights over the specific object, so a low-privileged authenticated user could act on content belonging to anyone. Reported by Ananda Dhakal (Patchstack)<\/li>\n- Security:
get_post<\/code>, get_post_meta<\/code> and get_post_revisions<\/code> now run WordPress's read_post<\/code> capability for the requested object \u2014 under the default read-only profile a Subscriber could previously retrieve Administrator-owned private pages and drafts by ID<\/li>\n- Security:
list_posts<\/code>, get_posts<\/code>, get_pages<\/code>, search_posts<\/code> and search<\/code> reduce the caller-supplied status<\/code> to the statuses that user may actually see, and scope the query to their own authorship where they may only see their own \u2014 previously status=draft<\/code> returned everyone's drafts<\/li>\n- Security:
create_post<\/code> and create_page<\/code> authorize the requested status, post type and author \u2014 publishing (and scheduling, and private status) now requires publish_posts<\/code>, so a Contributor can no longer publish, and internal post types are rejected<\/li>\n- Security:
update_post<\/code>, update_page<\/code>, delete_post<\/code> and delete_page<\/code> require edit_post<\/code> \/ delete_post<\/code> for the target object, plus a separate check on the requested transition, so another user's content can no longer be rewritten, unpublished or permanently deleted<\/li>\n- Security:
update_post_meta<\/code> and delete_post_meta<\/code> use core's edit_post_meta<\/code> \/ delete_post_meta<\/code> capabilities and reject protected keys; get_post_meta<\/code> hides protected keys from users who cannot edit the post<\/li>\n- Security: Media tools authorize the attachment itself, comment tools authorize the specific comment, and
assign_terms<\/code> requires edit rights on the post plus assign_terms<\/code> on the taxonomy<\/li>\n- Security:
create_comment<\/code> requires being able to read the post and finding comments open on it, and no longer bypasses moderation \u2014 comments from users without moderate_comments<\/code> are queued rather than published immediately<\/li>\n- Note: No configuration change is required and no profile is modified. Administrator and Editor behaviour is unchanged<\/li>\n<\/ul>\n\n
1.6.5<\/h4>\n\n\n- Added: The MCP Router settings tab is now visible, exposing the first-party MountDev MCP Router configuration UI<\/li>\n
- Changed: The MountDev MCP Router callback hosts are now allowed OAuth redirect hosts so the router can complete the authorization flow<\/li>\n<\/ul>\n\n
1.6.4<\/h4>\n\n\n- Security: Fixed a critical OAuth authorization bypass (CVE-2026-15015) \u2014
\/oauth\/authorize<\/code> auto-selected the site's first administrator and issued an access token to any unauthenticated caller presenting a valid client_id<\/code>. It now requires a logged-in WordPress user and explicit Approve\/Deny consent, and binds the token to the user who approved rather than an arbitrary admin. This affected all releases up to and including 1.6.3; see the retraction under 1.6.1 below<\/li>\n- Security: All existing OAuth authorization codes, access tokens and refresh tokens are revoked on upgrade, because any of them may have been obtained through the bypass \u2014 every connected client must authorize again<\/li>\n
- Security:
redirect_uri<\/code> is now validated against an allowlist before a code is issued and again at token exchange, matching on parsed host rather than string prefix; loopback callbacks are allowed per RFC 8252<\/li>\n- Security: PKCE is now mandatory and S256-only;
plain<\/code> is rejected at request time, in verify_pkce()<\/code>, and no longer advertised in any metadata document<\/li>\n- Security: Authorization codes are bound to the
client_id<\/code> and redirect_uri<\/code> they were issued for and are invalidated on any failed redemption; the refresh grant now validates client identity<\/li>\n- Security: Clients that self-registered via Dynamic Client Registration before 1.6.3 were still accepted at runtime; they are no longer honoured and the records are deleted<\/li>\n
- Fixed: The authorization endpoint is now served outside the REST API. Cookie authentication does not work for REST requests without an
X-WP-Nonce<\/code>, which a browser navigation from an OAuth client never carries \u2014 this made the login check always fail and is why the fix written for 1.6.1 was reverted<\/li>\n- Fixed: Hosts and plugins that force every login to their own page can no longer strand the authorization flow<\/li>\n<\/ul>\n\n
1.6.3<\/h4>\n\n\n- Security: Removed OAuth Dynamic Client Registration (
\/mcp-register<\/code>, \/register<\/code>, \/oauth\/register<\/code>) \u2014 clients can no longer self-provision a client_id<\/code>; connect using admin-issued OAuth credentials from the plugin's admin panel instead<\/li>\n<\/ul>\n\n1.6.2<\/h4>\n\n\n- Added: 7 new WordPress Core menu tools - update_nav_menu, delete_nav_menu, add_menu_item, update_menu_item, delete_menu_item, get_menu_locations, set_menu_location<\/li>\n
- Fixed: Navigation menus could previously only be listed and created, not renamed, deleted, populated with items, or assigned to a theme location<\/li>\n
- Changed: Tool count increased from 382 to 389 total tools (75 to 82 WordPress core)<\/li>\n<\/ul>\n\n
1.6.1<\/h4>\n\n\n- RETRACTION: The security entries originally published for this release were incorrect. The commit implementing them broke the OAuth flow for Claude and ChatGPT and was reverted before 1.6.1 shipped, but the changelog was not corrected at the time. CVE-2026-15015 remained exploitable in 1.6.1, 1.6.2 and 1.6.3, and is fixed in 1.6.4. Dynamic Client Registration removal was part of the same reverted commit and did not ship until 1.6.3. The withdrawn entries were: an OAuth authorization bypass fix requiring login and consent,
redirect_uri<\/code> allowlist validation, PKCE S256 enforcement at request time, a Claude.ai redirect URI allowlist entry, and login-redirect hijack protection<\/li>\n<\/ul>\n\n1.6.0<\/h4>\n\n\n- Added: 35 Jetpack tools for module control, stats & analytics, related posts, sharing, subscriptions, SEO, publicize connections, and protect settings (requires Jetpack plugin)<\/li>\n
- Added: 5 new Jetpack profiles - Read Only, Analyst, Site Manager, Content Manager, and Full Access<\/li>\n
- Added: MCP Server URL now shown in the OAuth credentials generated modal for quick copying<\/li>\n
- Changed: Plugin renamed to \"MountDev AI MCP Connector for WordPress\"<\/li>\n
- Changed: Tool count increased from 347 to 382 total tools<\/li>\n
- Fixed: OAuth token exchange failure for Claude Desktop and claude.ai<\/li>\n
- Fixed: OAuth
\/authorize<\/code> and \/token<\/code> fallback handling on sites that block .well-known<\/code> requests<\/li>\n<\/ul>\n\n1.5.2<\/h4>\n\n\n- Fixed: Button size adjusted to fit profile cards correctly<\/li>\n
- Fixed: Icon color not visible in create profile button<\/li>\n
- Fixed: Removed icons from profile action buttons to resolve alignment issue<\/li>\n
- Added: Settings link on the plugin page for quicker access<\/li>\n
- Changed: Marked tested up to WordPress 7.0<\/li>\n<\/ul>\n\n
1.5.1<\/h4>\n\n\n- Added: 35 Elementor Pro tools for form submissions, theme builder templates, popups, global widgets, dynamic tags, loop templates, notes, custom fonts\/icons, WooCommerce settings, element permissions, and role manager (requires Elementor Pro)<\/li>\n
- Added: 2 new predefined profiles for Elementor Pro (elementor_pro_designer, elementor_pro_full_access)<\/li>\n
- Improved: Profile manager category filter for easier navigation in admin UI<\/li>\n
- Improved: OAuth Claude Desktop setup instructions updated with clearer guidance<\/li>\n
- Changed: Tool count increased from 312 to 347 total tools<\/li>\n<\/ul>\n\n
1.5.0<\/h4>\n\n\n- Added: 36 Elementor FREE tools for complete page builder management (list\/get\/create\/delete pages, read\/write elements tree, global colors, global fonts, site settings, template library, plugin settings, experiments, CSS regeneration)<\/li>\n
- Added: 3 new predefined profiles (elementor_read_only, elementor_designer, elementor_full_access)<\/li>\n
- Added: Elementor plugin banner and tool grouping in admin UI<\/li>\n
- Changed: Tool count increased from 276 to 312 total tools<\/li>\n<\/ul>\n\n
1.4.0<\/h4>\n\n\n- Added: 20 Contact Form 7 tools for complete form management (list, get, create, update, delete, duplicate, mail templates, messages, additional settings, plugin settings, integrations)<\/li>\n
- Added: 3 new predefined profiles (cf7_read_only, cf7_form_manager, cf7_full_access)<\/li>\n
- Added: Contact Form 7 plugin banner and profile category in admin UI<\/li>\n
- Changed: Tool count increased from 256 to 276 total tools<\/li>\n<\/ul>\n\n
1.3.2<\/h4>\n\n\n- Fixed: RankMath per-post robots meta (noindex, nofollow, noarchive, noimageindex, nosnippet) now readable and writable via rankmath_get\/update_post_meta<\/li>\n
- Fixed: RankMath schema tools rewritten to use modern rank_math_schema_* meta format (was using deprecated rank_math_rich_snippet keys)<\/li>\n
- Fixed: rankmath_update_schema, rankmath_get_post_schema, rankmath_add_faq_schema, rankmath_add_howto_schema now work correctly with Rank Math 1.0.42+<\/li>\n<\/ul>\n\n
1.3.1<\/h4>\n\n\n- Added: 11 new Yoast SEO tools (robot directives, breadcrumb title, term SEO metadata, global settings, keyword usage, post type settings, update redirect, inclusive language score)<\/li>\n
- Fixed: Yoast SEO Premium tools were unreachable due to an early return in get_tools()<\/li>\n
- Fixed: RankMath create_redirect now correctly uses the sources column; url_to\/destination values were swapped<\/li>\n
- Changed: Tool count increased from 245 to 256 total tools<\/li>\n<\/ul>\n\n
1.3.0<\/h4>\n\n\n- Added: 78 Rank Math SEO tools for comprehensive SEO management<\/li>\n
- Added: 18 core read tools (post meta, social meta, canonical, content analysis, keyword analysis, schema, sitemap settings)<\/li>\n
- Added: 16 core write tools (update post meta, social meta, schema, canonical, FAQ\/HowTo schema blocks, global\/sitemap settings)<\/li>\n
- Added: 6 redirect and 404 monitor tools (list\/create\/bulk-delete\/export redirects, 404 logs, 404 summary)<\/li>\n
- Added: 6 analytics tools (site analytics, Search Console data, winning\/losing posts, Content AI score)<\/li>\n
- Added: 32 Rank Math Pro tools (Schema Templates, Link Genius, Keyword Tracking, Multi-Location, News\/Video Sitemaps, Image SEO, Email Reports)<\/li>\n
- Added: 3 new predefined profiles (rankmath_read_only, rankmath_content_optimizer, rankmath_full_access)<\/li>\n
- Added: Pro badge detection in Profile Manager for profiles requiring Rank Math Pro<\/li>\n
- Fixed: Page parent parameter now correctly sets post hierarchy when creating\/updating pages<\/li>\n
- Fixed: Reading Settings options (homepage display, feed settings) added to site tools whitelist<\/li>\n
- Fixed: Claude Desktop OAuth setup instructions added to client setup page<\/li>\n
- Changed: Tool count increased from 167 to 245 total tools<\/li>\n<\/ul>\n\n
1.2.0<\/h4>\n\n\n- Added: 18 Yoast SEO tools for comprehensive SEO management<\/li>\n
- Added: 3 new predefined profiles (yoast_read_only, yoast_content_optimizer, yoast_full_access)<\/li>\n
- Added: Yoast SEO Premium support with redirect management and multiple keywords<\/li>\n
- Added: Content analysis, readability scoring, and keyword optimization tools<\/li>\n
- Added: Schema markup management (page types and article types)<\/li>\n
- Added: Social meta management (Open Graph and Twitter Card)<\/li>\n
- Changed: Tool count increased from 149 to 167 total tools<\/li>\n<\/ul>\n\n
1.1.1<\/h4>\n\n\n- Changed: Updated readme description for better clarity<\/li>\n
- Fixed: WooCommerce default profiles now properly hidden when WooCommerce plugin is deactivated<\/li>\n
- Fixed: Removed WooCommerce badge from FAQ section when WooCommerce is not active<\/li>\n<\/ul>\n\n
1.1.0<\/h4>\n\n\n- Added: 74 WooCommerce tools across 3 new tool classes<\/li>\n
- Added: 4 new predefined profiles (woo_read_only, woo_store_manager, woo_full_access, complete_site)<\/li>\n
- Added: WooCommerce Brands extension support with 5 brand management tools<\/li>\n
- Added: Global product attributes management with 8 attribute tools<\/li>\n
- Added: Enhanced Profile Manager UI with WooCommerce branding and search\/filter<\/li>\n
- Added: Advanced product features (Global Unique ID, sold individually, shipping dimensions, linked products)<\/li>\n
- Added: Comprehensive coupon management with usage restrictions and limits<\/li>\n
- Changed: Profile Manager UI now separates WordPress and WooCommerce tools<\/li>\n
- Changed: Tool categories expanded from 10 to 28 categories<\/li>\n
- Changed: Tool count increased from 75 to 149 total tools<\/li>\n
- Technical: Conditional WooCommerce tool registration (only when WooCommerce is active)<\/li>\n
- Technical: 3 new tool classes (Woo_Product_Tools, Woo_Order_Tools, Woo_Store_Tools)<\/li>\n<\/ul>\n\n
1.0.0<\/h4>\n\n\n- Initial release<\/li>\n
- MCP Server Implementation with JSON-RPC 2.0 endpoint<\/li>\n
- OAuth 2.0 support for ChatGPT<\/li>\n
- WordPress Application Passwords for Claude Desktop, Cursor, Windsurf<\/li>\n
- 75 WordPress core tools across 10 categories<\/li>\n
- Profile-based access control with 3 predefined profiles<\/li>\n<\/ul>","raw_excerpt":"Connect ChatGPT or Claude to WordPress with one address, no API keys. Your assistant can write posts, update products and fix SEO, within limits you s …","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/tw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/285474","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/tw.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/tw.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=285474"}],"author":[{"embeddable":true,"href":"https:\/\/tw.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/cascadiawebservices"}],"wp:attachment":[{"href":"https:\/\/tw.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=285474"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/tw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=285474"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/tw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=285474"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/tw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=285474"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/tw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=285474"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/tw.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=285474"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}