Title: MountDev AI MCP Connector for WordPress Author: Cascadia Web Services Published: 31.03.2026 Last modified: 01.10.2026 --- Поиск плагинов ![](https://ps.w.org/mountdev-ai-mcp-connector/assets/banner-772x250.png?rev=3717384) ![](https://ps.w.org/mountdev-ai-mcp-connector/assets/icon-256x256.png?rev=3717384) # MountDev AI MCP Connector for WordPress Автор: [Cascadia Web Services](https://profiles.wordpress.org/cascadiawebservices/) [Скачать](https://downloads.wordpress.org/plugin/mountdev-ai-mcp-connector.2.2.0.zip) * [Детали](https://ru.wordpress.org/plugins/mountdev-ai-mcp-connector/#description) * [Отзывы](https://ru.wordpress.org/plugins/mountdev-ai-mcp-connector/#reviews) * [Установка](https://ru.wordpress.org/plugins/mountdev-ai-mcp-connector/#installation) * [Разработка](https://ru.wordpress.org/plugins/mountdev-ai-mcp-connector/#developers) [Поддержка](https://wordpress.org/support/plugin/mountdev-ai-mcp-connector/) ## Описание Connect ChatGPT, Claude or another AI assistant to your WordPress site, then ask it to do the work you would otherwise do by hand. 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. Ask it to draft and publish a post, tidy your menus, fix a typo on every page, 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. You decide what it may touch. Access is granted with a profile, which is a named set of tools: read only, content editing, site administration, 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. #### What you can ask for * **Precise edits** — change one sentence, or one word across the whole site, with every change previewed, checked and reversible * **Content** — draft, edit, publish and schedule posts and pages, manage categories, tags and menus * **Media** — upload images, set alt text, tidy the library * **Housekeeping** — comments, users, plugins, themes and site settings * **Your other plugins** — anything they offer as WordPress Abilities #### Works with any plugin that registers WordPress Abilities WordPress 6.9 added Abilities: a standard way for a plugin to describe what it can do, what it needs and who may use it. Any plugin that registers abilities gets tools in this connector, with nothing extra to install or configure. When the plugin updates its abilities, your assistant sees the change. Every ability starts switched off, in every profile. You turn on the ones you want, profile by profile, and each is clearly labeled when it can change or delete things. The ability itself checks who may use it before anything runs. Abilities need WordPress 6.9 or later. On older versions the connector’s own tools work as before. #### Works with the assistants people actually use * **ChatGPT** — paste the address, sign in, done * **Claude** — paste the address, sign in, done (Claude.ai, Claude Desktop and Claude Code) * **Cursor, Windsurf and other editors** — connect with a WordPress Application Password * Any client that speaks the Model Context Protocol #### Built for people who are responsible for a site * Nothing is sent to us or to any third party. The assistant talks to your site and nowhere else. * Client secrets are encrypted before they are stored. * Access tokens expire after an hour; authorization codes after ten minutes. * Only administrators can issue credentials. * Every action respects the signed-in user’s WordPress capabilities, checked against the specific post, product or comment being touched. ### Security * **OAuth 2.0 with PKCE** — authorization requires a logged-in WordPress user and an explicit approval step * **AES-256-CBC encryption** — client secrets encrypted at rest * **Token expiry** — access tokens last an hour, refresh tokens 30 days, authorization codes ten minutes * **Per-object capability checks** — a tool checks rights over the specific object, not just a broad capability * **Administrator-only credentials** — only administrators can issue or view OAuth credentials * **No privilege escalation** — the assistant can never exceed the permissions of the account it signed in as ### External Services This plugin talks to your site and nothing else. No data is sent to Cascadia Web Services or to any third party. 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: * `https://yoursite.com/wp-json/mountdev-ai-mcp-connector/v1/messages` * `https://yoursite.com/wp-json/mountdev-ai-mcp-connector/v1/oauth/*` It 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. The settings page has links to cascadiawebservices.com. Nothing is loaded from that site, and nothing is sent to it unless you click a link. ### License This plugin is licensed under the GPL v3 or later. See https://www.gnu.org/licenses/gpl-3.0.en.html for details. Icons on the settings page are from Lucide (https://lucide.dev), licensed under the ISC license. See licenses/lucide.txt. ## Скриншоты [⌊Access: choose what your assistant may do, from six ready-made profiles or your own.⌉⌊Access: choose what your assistant may do, from six ready-made profiles or your own.⌉[ Access: choose what your assistant may do, from six ready-made profiles or your own. [⌊Activating a profile asks you to confirm, then shows progress until the change is saved.⌉⌊Activating a profile asks you to confirm, then shows progress until the change is saved.⌉[ Activating a profile asks you to confirm, then shows progress until the change is saved. [⌊Quick Start: connect ChatGPT, Claude or another assistant.⌉⌊Quick Start: connect ChatGPT, Claude or another assistant.⌉[ Quick Start: connect ChatGPT, Claude or another assistant. [⌊Client Setup: build a ready-to-use configuration for desktop and editor apps.⌉⌊ Client Setup: build a ready-to-use configuration for desktop and editor apps.⌉[ Client Setup: build a ready-to-use configuration for desktop and editor apps. [⌊OAuth: credentials and setup steps for ChatGPT and Claude.⌉⌊OAuth: credentials and setup steps for ChatGPT and Claude.⌉[ OAuth: credentials and setup steps for ChatGPT and Claude. [⌊Endpoints: your MCP address, with a connection test.⌉⌊Endpoints: your MCP address, with a connection test.⌉[ Endpoints: your MCP address, with a connection test. [⌊FAQ: answers to common questions, on the settings page itself.⌉⌊FAQ: answers to common questions, on the settings page itself.⌉[ FAQ: answers to common questions, on the settings page itself. ## Установка 1. Install and activate the plugin. 2. Go to **Settings — MCP Connector**. 3. Copy the address shown on the page. 4. In ChatGPT or Claude, add it as a custom connector and sign in when asked. 5. Choose a profile, so the assistant knows what it may do. #### ChatGPT and Claude 1. Copy the address from **Settings — MCP Connector**. 2. In ChatGPT or Claude, open Settings, then Connectors, and add a custom connector with that address. Leave any Client ID and Secret fields empty. 3. 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. 4. Open the **Access** tab and choose what the assistant may do. If you prefer to issue credentials yourself, the **OAuth** tab still generates a Client ID and Secret, and connectors set up that way keep working. #### Cursor, Windsurf and other editors 1. Create an Application Password under **Users — Profile**. 2. Use the **Client Setup** tab to generate the configuration file for your editor. ## Часто задаваемые вопросы ### Do I need to be technical to use this? No. Copy one address from the plugin into your assistant, sign in, and pick what it may do. ### Can it change things I did not ask it to? It 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. ### Is my content sent to anyone? No. Your assistant talks to your site directly. Nothing goes to us or to any third party. ### Which plugins does it work with? Any plugin that registers WordPress Abilities. Its abilities appear under Access, grouped by the plugin’s own categories, and stay off until you switch them on. The connector’s own WordPress tools work on a plain WordPress site with nothing else installed. ### Why can’t my assistant see a plugin’s abilities? Every ability starts off in every profile, Full Access included. Switch it on under Access, then restart your assistant. Abilities need WordPress 6.9 or later. ### Who checks what an ability may do? WordPress checks the request against what the ability accepts, then asks the ability whether the signed-in user may use it. Checking which records that user may touch is up to the plugin that registered the ability. ### Do I need an API key or a client ID? No. 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. ### ChatGPT or Claude cannot connect, but Test Connection works. Why? A firewall, CDN or security rule on your host may be turning AI clients away before they reach WordPress. Run Test Connection: its outside check requests your site the way AI assistants do and names what is blocking them. Ask your host to allow these addresses for all visitors: /.well-known/oauth-authorization-server, /.well- known/oauth-protected-resource, /wp-json/mountdev-ai-mcp-connector/ and /mcp-token. ### What is MCP? The 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. ### What happens if I deactivate the plugin? The connection stops working. Nothing on your site is changed or removed. ### Can several people connect? Yes. Each person signs in as themselves, and what they can do follows their own WordPress role. ## Отзывы Нет отзывов об этом плагине. ## Участники и разработчики «MountDev AI MCP Connector for WordPress» — проект с открытым исходным кодом. В развитие плагина внесли свой вклад следующие участники: Участники * [ Cascadia Web Services ](https://profiles.wordpress.org/cascadiawebservices/) [Перевести «MountDev AI MCP Connector for WordPress» на ваш язык.](https://translate.wordpress.org/projects/wp-plugins/mountdev-ai-mcp-connector) ### Заинтересованы в разработке? [Посмотрите код](https://plugins.trac.wordpress.org/browser/mountdev-ai-mcp-connector/), проверьте [SVN репозиторий](https://plugins.svn.wordpress.org/mountdev-ai-mcp-connector/), или подпишитесь на [журнал разработки](https://plugins.trac.wordpress.org/log/mountdev-ai-mcp-connector/) по [RSS](https://plugins.trac.wordpress.org/log/mountdev-ai-mcp-connector/?limit=100&mode=stop_on_copy&format=rss). ## Журнал изменений #### 2.2.0 * Added: Test Connection now also checks your site from outside, the way ChatGPT and Claude reach it, through your CDN, firewall and host. It requests the connection addresses as a browser and as each AI client, checks what comes back, and says plainly what is wrong and who answered: the CDN, the server or a security plugin. Copy report gives a plain-text version to send to your host * Added: Test Connection names any switched-on abilities that never reach the assistant, such as those from a plugin that registers them only on admin pages * Fixed: One ability with a schema that AI clients reject no longer breaks the whole tool list. Ability schemas are made valid JSON Schema before they are sent, so Refresh tools works in Claude and other clients * Changed: Each ability’s title names the plugin it comes from, for example «FluentCRM: Get Contact», so assistants that list tools by title show where each one comes from. The settings page keeps the plain label * Changed: The Changes tab matches the new settings design. Each change reads as a short sentence, the full before and after text sits behind Show details, and times show as «2 hours ago» with the full date on hover * Note: Changes made before 2.2.0 show their short summary under Show details. Undo works as before #### 2.1.0 * Changed: A new settings page, with the same layout as the other MountDev plugins * Changed: Activating a profile asks you to confirm in plain words, then keeps the window open with a progress indicator until the change is saved * Changed: Notices from other plugins no longer appear on this plugin’s settings page * Added: New screenshots and directory artwork #### 2.0.0 * Removed: The built-in tools for WooCommerce, Rank Math, Yoast SEO, Elementor, Jetpack and Contact Form 7, and their ready-made profiles. Each was code this plugin had to keep in step with another plugin’s updates. Several of those plugins now describe their own actions through WordPress Abilities, which is the better source * Added: WordPress Abilities. Any plugin that registers abilities (WordPress 6.9 or later) gets tools in the connector, grouped by the plugin’s own categories, with no code written for it here * Added: Every ability starts switched off, in every profile including Full Access. Built-in profiles have an Abilities button to switch them on; custom profiles do it under Edit. Choices are kept by ability name, so a plugin that is deactivated and reactivated finds them as it left them * Added: Tools that can change your site are labeled Write, and those that may delete or overwrite are labeled Destructive, in the profile editor and the list of enabled tools * Added: Abilities run through WordPress itself, which checks the input and the ability’s own permission check before anything runs. The assistant sees each ability’s title, input and output schemas and its read only, destructive and idempotent hints * Added: Precise edits works with more page builders: SiteOrigin Page Builder, Zion Builder and Live Composer, the new widgets in Elementor 4, and the text settings of Spectra, Essential Blocks, Otter, Kubio and Greenshift blocks * Fixed: Precise edits on a Beaver Builder page failed, and put the page back, when the page held a backslash anywhere * Changed: Full Access now means every one of the connector’s own tools. Abilities are switched on one by one * Changed: An unknown tool, and a tool given bad input, now return the MCP «Invalid params» error (-32602) instead of an internal error * Upgrade: Saved profiles forget the removed tools and keep everything else. A custom profile left with none stays, shown as empty, until you edit or delete it. A site whose active profile was one of the removed ones goes back to WordPress Read Only. OAuth connections, application passwords and the Changes history are untouched #### 1.8.0 * Added: duplicate_post copies a post, page or other public post type as a new draft. The copy keeps the content, the layout as your builder stored it, the featured image, the page template and the terms, and is titled «(copy)» unless you give it a title. It is always a draft, and it is refused unless you may edit what you are copying * Fixed: Three links in the «Who builds this» box on the settings page (WordPress care, Hosting and Automation) led to pages that no longer exist. They now open the current pages * Fixed: bridge/README.md is included in the plugin again. 1.7.1 left it out by mistake * Changed: The short description is now within WordPress.org’s 150 character limit, so the directory no longer cuts it off #### 1.7.1 * Added: How long changes are kept is now a setting, 30 days by default, from 7 days to a year. The change list and the backups are cleared on the same schedule, so neither grows without limit; previously the list itself was never cleared * Added: Recent changes, on its own Changes tab, 20 to a page. Every change made with precise edits is listed with the page, what changed, when and by whom, and can be undone from there, without the assistant that made it * Added: Undoing a change on a page that has been edited since now asks first, because it would also remove those later edits. Assistants are told the same and must confirm * Fixed: The settings tabs now fill their space when selected, and only the tab you are on is highlighted. Since 1.6.8, WordPress’s own tab styling sat on top of the plugin’s, leaving a gap beside each tab and keeping Quick Start highlighted * Changed: Patch tools are now called Precise edits in the settings, with a plainer description of what they do * Changed: The Access tab is simpler. It leads with what the assistant may do, the list of allowed tools opens on request, in three columns with each tool’s description on hover, instead of scrolling in a small box, the banners suggesting other plugins are gone, and Precise edits sits at the end with the other permissions. Recent changes has its own Changes tab #### 1.7.0 * Added: Patch tools. Your assistant can change part of a page, such as one sentence, or one spelling across many pages, without resending the whole page. Every change is a preview first; a real change must say which version of the page it expects and how many times each piece of text should be found, and nothing happens if either is wrong * Added: Every patch is backed up for 30 days, read back from the database after saving, checked, and undone automatically if the check fails. content_rollback puts any page back exactly as it was * Added: Patches change only visible text. Links, image addresses, classes, styles, code and SVG are never matched, and «realise» never matches inside «realised» * Added: Works with the block editor and block builders such as Greenshift, Kadence and Spectra, where text is changed in both the page and the block’s own settings so the editor still recognises it; and with Elementor, Divi, WPBakery and Beaver Builder * Added: cache_purge clears cached copies of changed pages through WordPress and any of the common caching plugins that is installed * Added: Each change is previewed as the sentence before and after, so a change that is valid but wrong, such as a doubled full stop, is visible before anything is written * Added: The patch tools are included in the built-in editing profiles, not only Full Access * Changed: Deleting the plugin also removes the patch tools’ backups, write log, settings and scheduled cleanup * Note: Patch tools are off until an administrator turns them on, under Access. They need an account allowed to save unfiltered HTML #### 1.6.9 * 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 * Note: Your posts, products, media and anything an assistant created are your site’s own content and are never touched #### 1.6.8 * 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 * 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 * 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 * Changed: The settings screen uses WordPress’s own layout and styling * Changed: Promotional banners and the advertising sidebar removed * Changed: The page opens on Quick Start instead of the FAQ, and the Profiles tab is now called Access * Fixed: The tool count said 389; there are 388 (81 WordPress core, not 82) * Changed: Readme rewritten in plain language * Note: Existing connections keep working and do not need setting up again #### 1.6.7 * 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` header’s `resource_metadata` 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` (and `/.well-known/oauth-protected- resource`), and `authorization_servers` leads clients to the existing metadata * Fixed: 401 responses for an expired or invalid access token now carry the `WWW- Authenticate` challenge too * Fixed: The token endpoint now accepts client credentials sent with HTTP Basic authentication (`client_secret_basic`), which the metadata already advertised * Security: A `client_secret` sent with a PKCE token or refresh request is now verified. Previously a wrong secret was ignored when PKCE succeeded * 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 #### 1.6.6 * 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`, `edit_posts`, `delete_posts`) 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) * Security: `get_post`, `get_post_meta` and `get_post_revisions` now run WordPress’s` read_post` capability for the requested object; under the default read-only profile a Subscriber could previously retrieve Administrator-owned private pages and drafts by ID * Security: `list_posts`, `get_posts`, `get_pages`, `search_posts` and `search` reduce the caller-supplied `status` to the statuses that user may actually see, and scope the query to their own authorship where they may only see their own; previously `status=draft` returned everyone’s drafts * Security: `create_post` and `create_page` authorize the requested status, post type and author; publishing (and scheduling, and private status) now requires` publish_posts`, so a Contributor can no longer publish, and internal post types are rejected * Security: `update_post`, `update_page`, `delete_post` and `delete_page` require` edit_post` / `delete_post` 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 * Security: `update_post_meta` and `delete_post_meta` use core’s `edit_post_meta`/` delete_post_meta` capabilities and reject protected keys; `get_post_meta` hides protected keys from users who cannot edit the post * Security: Media tools authorize the attachment itself, comment tools authorize the specific comment, and `assign_terms` requires edit rights on the post plus` assign_terms` on the taxonomy * Security: `create_comment` requires being able to read the post and finding comments open on it, and no longer bypasses moderation; comments from users without `moderate_comments` are queued rather than published immediately * Note: No configuration change is required and no profile is modified. Administrator and Editor behaviour is unchanged #### 1.6.5 * Added: The MCP Router settings tab is now visible, exposing the first-party MountDev MCP Router configuration UI * Changed: The MountDev MCP Router callback hosts are now allowed OAuth redirect hosts so the router can complete the authorization flow #### 1.6.4 * Security: Fixed a critical OAuth authorization bypass (CVE-2026-15015); `/oauth/ authorize` auto-selected the site’s first administrator and issued an access token to any unauthenticated caller presenting a valid `client_id`. 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 * 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; every connected client must authorize again * Security: `redirect_uri` 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 * Security: PKCE is now mandatory and S256-only; `plain` is rejected at request time, in `verify_pkce()`, and no longer advertised in any metadata document * Security: Authorization codes are bound to the `client_id` and `redirect_uri` they were issued for and are invalidated on any failed redemption; the refresh grant now validates client identity * 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 * Fixed: The authorization endpoint is now served outside the REST API. Cookie authentication does not work for REST requests without an `X-WP-Nonce`, which a browser navigation from an OAuth client never carries; this made the login check always fail and is why the fix written for 1.6.1 was reverted * Fixed: Hosts and plugins that force every login to their own page can no longer strand the authorization flow #### 1.6.3 * Security: Removed OAuth Dynamic Client Registration (`/mcp-register`, `/register`,`/ oauth/register`); clients can no longer self-provision a `client_id`; connect using admin-issued OAuth credentials from the plugin’s admin panel instead #### 1.6.2 * 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 * Fixed: Navigation menus could previously only be listed and created, not renamed, deleted, populated with items, or assigned to a theme location * Changed: Tool count increased from 382 to 389 total tools (75 to 82 WordPress core) #### 1.6.1 * 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` allowlist validation, PKCE S256 enforcement at request time, a Claude.ai redirect URI allowlist entry, and login-redirect hijack protection #### 1.6.0 * Added: 35 Jetpack tools for module control, stats & analytics, related posts, sharing, subscriptions, SEO, publicize connections, and protect settings (requires Jetpack plugin) * Added: 5 new Jetpack profiles — Read Only, Analyst, Site Manager, Content Manager, and Full Access * Added: MCP Server URL now shown in the OAuth credentials generated modal for quick copying * Changed: Plugin renamed to «MountDev AI MCP Connector for WordPress» * Changed: Tool count increased from 347 to 382 total tools * Fixed: OAuth token exchange failure for Claude Desktop and claude.ai * Fixed: OAuth `/authorize` and `/token` fallback handling on sites that block `. well-known` requests #### 1.5.2 * Fixed: Button size adjusted to fit profile cards correctly * Fixed: Icon color not visible in create profile button * Fixed: Removed icons from profile action buttons to resolve alignment issue * Added: Settings link on the plugin page for quicker access * Changed: Marked tested up to WordPress 7.0 #### 1.5.1 * 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) * Added: 2 new predefined profiles for Elementor Pro (elementor_pro_designer, elementor_pro_full_access) * Improved: Profile manager category filter for easier navigation in admin UI * Improved: OAuth Claude Desktop setup instructions updated with clearer guidance * Changed: Tool count increased from 312 to 347 total tools #### 1.5.0 * 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) * Added: 3 new predefined profiles (elementor_read_only, elementor_designer, elementor_full_access) * Added: Elementor plugin banner and tool grouping in admin UI * Changed: Tool count increased from 276 to 312 total tools #### 1.4.0 * Added: 20 Contact Form 7 tools for complete form management (list, get, create, update, delete, duplicate, mail templates, messages, additional settings, plugin settings, integrations) * Added: 3 new predefined profiles (cf7_read_only, cf7_form_manager, cf7_full_access) * Added: Contact Form 7 plugin banner and profile category in admin UI * Changed: Tool count increased from 256 to 276 total tools #### 1.3.2 * Fixed: RankMath per-post robots meta (noindex, nofollow, noarchive, noimageindex, nosnippet) now readable and writable via rankmath_get/update_post_meta * Fixed: RankMath schema tools rewritten to use modern rank_math_schema_* meta format (was using deprecated rank_math_rich_snippet keys) * 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+ #### 1.3.1 * 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) * Fixed: Yoast SEO Premium tools were unreachable due to an early return in get_tools() * Fixed: RankMath create_redirect now correctly uses the sources column; url_to/ destination values were swapped * Changed: Tool count increased from 245 to 256 total tools #### 1.3.0 * Added: 78 Rank Math SEO tools for comprehensive SEO management * Added: 18 core read tools (post meta, social meta, canonical, content analysis, keyword analysis, schema, sitemap settings) * Added: 16 core write tools (update post meta, social meta, schema, canonical, FAQ/HowTo schema blocks, global/sitemap settings) * Added: 6 redirect and 404 monitor tools (list/create/bulk-delete/export redirects, 404 logs, 404 summary) * Added: 6 analytics tools (site analytics, Search Console data, winning/losing posts, Content AI score) * Added: 32 Rank Math Pro tools (Schema Templates, Link Genius, Keyword Tracking, Multi-Location, News/Video Sitemaps, Image SEO, Email Reports) * Added: 3 new predefined profiles (rankmath_read_only, rankmath_content_optimizer, rankmath_full_access) * Added: Pro badge detection in Profile Manager for profiles requiring Rank Math Pro * Fixed: Page parent parameter now correctly sets post hierarchy when creating/ updating pages * Fixed: Reading Settings options (homepage display, feed settings) added to site tools whitelist * Fixed: Claude Desktop OAuth setup instructions added to client setup page * Changed: Tool count increased from 167 to 245 total tools #### 1.2.0 * Added: 18 Yoast SEO tools for comprehensive SEO management * Added: 3 new predefined profiles (yoast_read_only, yoast_content_optimizer, yoast_full_access) * Added: Yoast SEO Premium support with redirect management and multiple keywords * Added: Content analysis, readability scoring, and keyword optimization tools * Added: Schema markup management (page types and article types) * Added: Social meta management (Open Graph and Twitter Card) * Changed: Tool count increased from 149 to 167 total tools #### 1.1.1 * Changed: Updated readme description for better clarity * Fixed: WooCommerce default profiles now properly hidden when WooCommerce plugin is deactivated * Fixed: Removed WooCommerce badge from FAQ section when WooCommerce is not active #### 1.1.0 * Added: 74 WooCommerce tools across 3 new tool classes * Added: 4 new predefined profiles (woo_read_only, woo_store_manager, woo_full_access, complete_site) * Added: WooCommerce Brands extension support with 5 brand management tools * Added: Global product attributes management with 8 attribute tools * Added: Enhanced Profile Manager UI with WooCommerce branding and search/filter * Added: Advanced product features (Global Unique ID, sold individually, shipping dimensions, linked products) * Added: Comprehensive coupon management with usage restrictions and limits * Changed: Profile Manager UI now separates WordPress and WooCommerce tools * Changed: Tool categories expanded from 10 to 28 categories * Changed: Tool count increased from 75 to 149 total tools * Technical: Conditional WooCommerce tool registration (only when WooCommerce is active) * Technical: 3 new tool classes (Woo_Product_Tools, Woo_Order_Tools, Woo_Store_Tools) #### 1.0.0 * Initial release * MCP Server Implementation with JSON-RPC 2.0 endpoint * OAuth 2.0 support for ChatGPT * WordPress Application Passwords for Claude Desktop, Cursor, Windsurf * 75 WordPress core tools across 10 categories * Profile-based access control with 3 predefined profiles ## Мета * Версия **2.2.0** * Обновление: **4 дня назад** * Активных установок: **200+** * Версия WordPress ** 5.8 или выше ** * Совместим вплоть до: **7.1.2** * Версия PHP ** 7.4 или выше ** * Язык * [English (US)](https://wordpress.org/plugins/mountdev-ai-mcp-connector/) * Метки: * [AI](https://ru.wordpress.org/plugins/tags/ai/)[AI agent](https://ru.wordpress.org/plugins/tags/ai-agent/) [ChatGPT](https://ru.wordpress.org/plugins/tags/chatgpt/)[Claude](https://ru.wordpress.org/plugins/tags/claude/) [mcp](https://ru.wordpress.org/plugins/tags/mcp/) * [Дополнительно](https://ru.wordpress.org/plugins/mountdev-ai-mcp-connector/advanced/) ## Оценки Пока что нет ни одного отзыва. [Ваш отзыв](https://wordpress.org/support/plugin/mountdev-ai-mcp-connector/reviews/#new-post) [Посмотреть всеотзывы](https://wordpress.org/support/plugin/mountdev-ai-mcp-connector/reviews/) ## Участники * [ Cascadia Web Services ](https://profiles.wordpress.org/cascadiawebservices/) ## Поддержка Есть что сказать? Нужна помощь? [Перейти в форум поддержки](https://wordpress.org/support/plugin/mountdev-ai-mcp-connector/)