=== MCP Server for WordPress – Connect Claude, ChatGPT & Gemini | AtlasMCP === Contributors: hasanazizul, atlasaidev Donate link: https://atlasaidev.com/ Tags: mcp, mcp-server, ai, claude, chatgpt Requires at least: 6.8 Tested up to: 7.1 Requires PHP: 7.4 Stable tag: 1.9.3 License: GPLv2 or later License URI: https://www.gnu.org/licenses/gpl-2.0.html Secure MCP server for WordPress. Connect Claude, ChatGPT & Gemini via OAuth 2.1. Unlimited AI abilities, WooCommerce tools, RBAC, editor AI. == Description == **AtlasMCP is the only WordPress MCP server with no limit on how many AI abilities your site can expose.** It turns your site into a Model Context Protocol (MCP) server so AI assistants and autonomous AI agents like **Claude**, **ChatGPT**, **Gemini**, **Cursor**, and **Claude Desktop** can read, write, and manage your posts, pages, media, users, settings, and WooCommerce store through natural language. Your tool list is not a fixed catalogue: on top of the built-in abilities, the free plugin picks up **every ability any plugin registers through the WordPress Abilities API** and turns **WooCommerce's own REST API** into read-only AI tools, with no cap in free or Pro. Generate excerpts, feature images, summaries, titles, and alt text without leaving the post — on a **secure MCP server** built around **OAuth 2.1 with PKCE**, **per-role access control**, and an **audit trail of every AI action**, so each connection only does what you allow and nothing happens on your site unseen. = How do I connect Claude, ChatGPT or Gemini to WordPress? = A **setup guide** walks a new site from install to "my AI app answered a question": what you want AI to do, a check of your site, which tools to offer, connecting your app and a first question. Any time later, open **AtlasMCP → Connections** and click **Connect an AI app**: Claude opens with your site already filled in, Cursor and VS Code add it in one click, and ChatGPT, Claude Code and Gemini CLI get short steps. You approve on your own site, choosing **Full access** or **Read only**, and the screen tells you the moment the app is connected. No tokens to copy. Scripts and automation tools can use an access token or an Application Password instead. = Does it work with my other plugins? = Yes. Most MCP plugins only expose what they wrote themselves; AtlasMCP turns the plugins you already run into AI tools: * **Abilities API — free, unlimited.** Any plugin that registers abilities through the WordPress Abilities API is picked up automatically. * **REST API to AI tools — WooCommerce free, every plugin in Pro.** AtlasMCP reads REST endpoint definitions and turns them into AI tools, grading each one on how well it describes itself. = WooCommerce AI agent = Turn Claude or ChatGPT into a WooCommerce AI agent. The free **AI Store Manager** module adds 24 store tools: search and edit products, categories, tags and brands, look up orders, and read sales reports. WooCommerce's own REST API adds read-only tools for products, orders and customers, so an AI can answer "which products are low on stock". **Pro adds the rest of the REST API** — fulfil orders, issue refunds, edit customers, coupons, shipping and more — and each role only gets the tools you grant it. = Is an MCP server on WordPress secure? = An MCP server gives an AI assistant real write access, so this one is built to be governed, not trusted blindly: * **OAuth 2.1 with PKCE and dynamic client registration** — your site is its own authorization server, with no client secrets or long-lived tokens to leak. JWT and Application Passwords work for headless and CI use. * **Every connection maps to a WordPress user** — an AI client can never exceed what the person behind it may do. * **Role-based access control** — choose which modules and abilities each role may use. Pro adds per-ability RBAC, tool/resource/prompt modes and OAuth scope rules. * **Audit trail** — with the official AI plugin's request logging on, every AI tool call is recorded: tool, user, duration and result. * **Read-only apps, a pause switch and one-click revoke** — the **Connections** screen lists every AI app, token and app password, who it acts as and when it was last used. * **Your keys, your server** — bring your own AI provider keys; nothing is proxied through us. = Works with the official WordPress AI plugin and the Classic Editor = AtlasMCP integrates with the official [AI plugin](https://wordpress.org/plugins/ai/) instead of running a parallel system: our AI experiments appear as feature cards on its **Settings → AI** screen, respect its toggles and inherit its editorial Guidelines, and you can hide its duplicate experiments. All experiments also work in the **Classic Editor**, which the official AI plugin does not support. = Why choose AtlasMCP? = * **MCP server + AI content in one plugin** — most WordPress MCP plugins do one or the other. * **Works on WordPress 6.8+** — bundles the Abilities API and MCP Adapter, so you need not wait for core. * **Multi-provider AI** — OpenAI, Google Gemini or Anthropic Claude through the WordPress AI Client; one provider key serves everything. * **Workflow builder** — combine abilities into reusable workflows. = Modules — individually toggleable = 1. **AI Content Steward (22 abilities)** — content analysis and generation, plus posts, categories and tags. 2. **Abilities from other plugins** — other plugins' REST endpoints as tools. 3. **Pages Manager (5)**, **Media Manager (7)**, **Users Manager (7)**, **Custom Post Types Manager (6)**. 4. **REST API Tools (3)** — discover and run any WordPress REST endpoint. 5. **Site Info & Diagnostics (4)** and **Settings Manager (3)**. 6. **AI Store Manager — WooCommerce (24)** — requires WooCommerce. 7. **Error Debugger (4)** — PHP error monitoring with AI fix commands. 8. **External Abilities** — every ability other plugins register through the Abilities API. = AI Content Generator: Write Blog Posts, Pages and Product Descriptions = Six panels run on your AI provider in both the Block Editor and the Classic Editor: * **Content Generation** — an AI blog post generator and article writer: pick a title, edit the outline, then generate and preview the full post. Works for pages, custom post types and WooCommerce product descriptions. * **Excerpts**, **Title Suggestions** and **Summaries** — one click, with tone and style presets. * **Feature Image Generation** — images generated from your post content. * **Alt Text Generation** — vision-based: the AI sees the actual image, not just the filename. **Pro extends every experiment** with a prompt templates library, batch variants, generation history, model tuning, "Explain This Generation" and keyboard shortcuts, and lets Content Generation link to posts and products that really exist. = Shopping assistant: customers shop with their own AI (Pro) = A "Shop with AI" button lets shoppers connect Claude, ChatGPT or another AI app in a few taps. Their assistant searches your catalogue, builds the cart and places the order, as a guest or with their account. It can never edit your store, and card payment always finishes on your own checkout page. = Site check, Versions and Error Debugger = * **Connection health check** — checks HTTPS, permalinks, the login header, security plugins, page caches and whether the internet can reach your site, says what to fix, and can add the missing login-header line to .htaccess for you (after a backup). * **Versions** — go back to an earlier release in one click; each version is checked against your site first, and your settings and connected apps are kept. * **Error Debugger** — PHP errors from plugins and themes, grouped by file, with email alerts and a copy-paste **Fix Command** for any AI assistant. Pro adds an MCP Fix Command with automatic backups, Slack/Discord webhooks and a Backups Manager. = See every AI tool on your site, and fix the weak ones = The **Abilities** screen lists every tool your site can expose — ours, other plugins', and those derived from REST endpoints — and **grades each one on how well it describes itself**, with a tool budget so AI apps stay accurate. The **Usage** screen shows what was actually called. Pro adds an editor for any ability's name and description, saved as an overlay so plugin updates never overwrite it. = Built on the WordPress AI building blocks = Every ability is registered through the standard **WordPress Abilities API** and exposed over MCP via the official MCP Adapter, both bundled so everything works on WordPress 6.8+ today. Add your provider key once under **Settings → Connectors** with the official [AI Provider for OpenAI](https://wordpress.org/plugins/ai-provider-for-openai/), [Google](https://wordpress.org/plugins/ai-provider-for-google/) or [Anthropic](https://wordpress.org/plugins/ai-provider-for-anthropic/) plugins, and AtlasMCP reuses it. = Role-based MCP access and OAuth = Your site is its own OAuth 2.1 server: an AI app finds it through `.well-known` metadata, registers itself and completes a PKCE sign-in after you approve. The connection acts as your WordPress user, so your role and **Access Control** decide what it can do. Pick a role, check the abilities and workflows it may use, and save; changes apply to every connection at once. New tools go to Administrator automatically, and by default only users who can edit posts may approve a connection (`awfah_oauth_authorize_min_capability` filter). = AtlasMCP Pro = [AtlasMCP Pro](https://wpatlasmcp.com/pricing/) adds the **Shopping assistant**, **unlimited workflows** (free allows 3), **per-ability RBAC** with per-role OAuth policy, **T/R/P access modes**, **ability editing**, **REST tools for every plugin, including writes**, **advanced AI experiments**, **workflow prompt builders**, **Error Debugger Pro** and **priority support**. 7-day free trial, no credit card required. == External services == AtlasMCP connects to the outside services below only for the features named. Nothing else leaves your site, and the MCP server itself does not send your content anywhere: the AI apps you connect call your site, not the other way round. = AtlasMCP connection check (AtlasAiDev) = When you press **Run check** on the **Connections** screen, the last step asks an AtlasAiDev server at `voice.atlasvoice.cloud` to call your site from the internet, the way Claude and ChatGPT do. It sends your site address and your MCP server address, nothing else. The server then reads only your site's public sign-in addresses; it never signs in or changes anything, and it keeps no record beyond a short technical log. It runs only when you press the button, and it is skipped for local sites. [Terms](https://atlasvoice.cloud/terms), [Privacy policy](https://atlasvoice.cloud/privacy). Developers can point it elsewhere or switch it off with the `awfah_reachability_endpoint` filter. = WordPress.org = The **Versions** screen asks the WordPress.org plugin directory (`api.wordpress.org`) for this plugin's released versions when you open it, and downloads a version from `downloads.wordpress.org` only when you press Roll back. The **Our Plugins** page reads the public ratings of our plugins from `api.wordpress.org`. Only the plugin names are sent. [Privacy policy](https://wordpress.org/about/privacy/). = GitHub (raw.githubusercontent.com) = The **Our Plugins** page and the dashboard's occasional offers read two public JSON files we publish on GitHub, cached for 12 hours. The request is a plain download; no information about your site is sent. [Terms](https://docs.github.com/en/site-policy/github-terms/github-terms-of-service), [Privacy policy](https://docs.github.com/en/site-policy/privacy-policies/github-general-privacy-statement). = Usage tracking (AtlasAiDev, opt-in) = Only if an administrator clicks **Allow** on the opt-in notice or ticks **Share anonymous usage data** in the setup guide, the plugin sends `track.atlasaidev.com` the site name, language and address, the administrator's name and email, the number of plugins, which AtlasMCP modules are on, and feature-usage counts. Never post content, credentials or tokens. You can opt out at any time. [Terms](https://atlasaidev.com/terms-and-conditions/), [Privacy policy](https://atlasaidev.com/privacy-policy/). = Your AI provider (OpenAI, Google or Anthropic) = The AI experiments (content, excerpts, titles, summaries, featured images, alt text) send the text or image you are working on to the AI provider you set up under **Settings → Connectors**, through WordPress's AI Client, only when you press a generate button. Generated images are then downloaded from the provider into your Media Library. The provider's own terms apply: OpenAI ([Terms](https://openai.com/policies/terms-of-use/), [Privacy](https://openai.com/policies/privacy-policy/)), Google ([Terms](https://ai.google.dev/gemini-api/terms), [Privacy](https://policies.google.com/privacy)), Anthropic ([Terms](https://www.anthropic.com/legal/commercial-terms), [Privacy](https://www.anthropic.com/legal/privacy)). == Frequently Asked Questions == = What is an MCP server for WordPress? = An MCP server for WordPress exposes your site to AI assistants through the Model Context Protocol (MCP) — an open standard for connecting AI agents to tools. AtlasMCP adds this server to WordPress so clients like Claude, ChatGPT, Gemini, and Cursor can securely read and manage your posts, pages, media, users, settings, and WooCommerce store via natural language. = How is AtlasMCP different from other WordPress MCP plugins? = Most WordPress MCP plugins give you a server only, with a fixed list of tools. AtlasMCP pairs an unlimited MCP server (OAuth 2.1, role-based access control, workflows, and third-party plugin support) with AI content generation inside the post editor — excerpts, titles, summaries, feature images, and alt text — in both the Block Editor and the Classic Editor, and it integrates with the official WordPress AI plugin instead of competing with it. = How do I generate a blog post with AI in WordPress? = Open a new post, click AtlasMCP Write in the editor, and enter your topic. The AI content generator suggests titles, drafts an outline you can edit, then writes the full article. You preview the draft and insert it yourself — nothing is written to your post or published until you choose to. = Can it write WooCommerce product descriptions? = Yes. On a product screen the AI product description generator is selected automatically and writes for shoppers — what the item is, what it is made of, who it suits, and how to care for it. It will not invent measurements, materials or claims you did not give it. = Does the AI writer work with the Classic Editor? = Yes. AtlasMCP Write sits beside the Add Media button on the classic content editor, with the same topic, outline and preview steps as the block editor. = How do I connect Claude to WordPress? = Open **AtlasMCP → Connections**, click **Connect an AI app** and pick Claude: it opens with your site already filled in. Click Add, then approve on your site. No tokens to copy. See **Connect your AI client** above for other apps. = How do I connect ChatGPT to WordPress? = Add the same MCP server URL as a connector in ChatGPT (OpenAI's connector settings), authorize via the OAuth consent screen, and ChatGPT can manage your WordPress site through the abilities you allow. JWT and Application Password authentication are available as alternatives. = Does it work with Cursor, Windsurf, or Claude Code? = Yes — any MCP-compatible client works: Cursor, Windsurf, Claude Code, Claude Desktop, Gemini CLI, and more. Point the client at your MCP endpoint and authenticate with OAuth 2.1, JWT, or an Application Password. = Troubleshooting: my AI client cannot connect (Cloudflare, SiteGround, caching) = Most connection failures are caused by the host or a firewall interfering with the MCP endpoint, not by the plugin: * **Cloudflare** — the "Block AI Bots" setting and Bot Fight Mode block requests from Claude, ChatGPT, and other AI clients. Add a WAF skip/exception rule that allowlists the `/wp-json/awfah_mcp/` path (or turn off Block AI Bots), then reconnect. * **SiteGround and similar hosts** — built-in anti-bot filters can answer MCP requests with an HTML challenge page. Ask support to exclude `/wp-json/awfah_mcp/` from bot protection. * **LiteSpeed / server caching** — REST responses must never be cached. Exclude `/wp-json/` (or at least `/wp-json/awfah_mcp/`) from LiteSpeed Cache, Varnish, or any full-page/server cache; a cached OAuth or JSON-RPC response breaks the handshake. = Does OAuth work if WordPress is installed in a subdirectory? = Yes, since 1.9.0. Sign-in works when WordPress lives in a subfolder (`https://example.com/blog`) as well as at the domain root. It needs HTTPS for web apps like Claude and ChatGPT. If an app still cannot connect, run the health check on the **Connections** screen. = Does it work with the Classic Editor? = Yes. All six AI experiments — full content generation, excerpt, titles, summary, featured image, and image alt text (via the media modal) — work in the Classic Editor as well as the Block Editor. The official WordPress AI plugin's experiments are Block Editor only. = Does it work with the official WordPress AI plugin? = Yes — by design. Our experiments show up as feature cards on its **Settings → AI** screen, respect its toggles, and inject its editorial Guidelines into every prompt. You can also hide its duplicate experiments (per experiment or globally) so editors see a single AI button. = Does it work with WooCommerce? = Yes. The **AI Store Manager** module adds 24 WooCommerce abilities — search and manage products, orders, categories, tags, brands, and sales reports — through the same MCP server. The module only registers its abilities when WooCommerce is active. = What AI providers are supported? = Any provider the **WordPress AI Client** supports, including OpenAI (GPT models), Google Gemini, and Anthropic Claude. Configure providers under **Settings → Connectors**. = How many AI abilities do I get? = There is no fixed number, and no limit. The plugin ships built-in abilities across 11 modules — Content Steward, Posts, Pages, Media, Users, Custom Post Types, REST API Tools, Site Info, Settings, WooCommerce Store Manager and Error Debugger — and then adds every ability any other plugin on your site registers through the WordPress Abilities API. Install more AI-aware plugins and your tool list grows on its own, in the free version. = Will hundreds of AI tools slow my site down? = No. Nothing in this plugin runs on your front end, so visitor page loads are unaffected. On a store with 396 WooCommerce endpoints connected, registering them takes under a millisecond and adds roughly 4 MB to peak memory, and only on the two admin screens that list abilities. The practical limit is not your server — it is that AI models start picking the wrong tool past roughly a hundred, which is why the plugin shows the count and warns you. = Does it work with my other plugins? = Yes, in two ways. Any plugin that registers abilities through the WordPress Abilities API is picked up automatically and free. For plugins that have not adopted the API yet, AtlasMCP can read their REST API and turn those endpoints into AI tools — free for WooCommerce, and for every plugin on your site with Pro. = Can an AI change my WooCommerce store? = Only as far as you allow. The free **AI Store Manager** module can edit products, categories, tags and brands; the tools made from WooCommerce's REST API are read-only in free. Pro adds the REST endpoints that write, such as refunds and order changes. You can switch any single tool off for a role in Access control. In both versions, an endpoint whose permission check cannot be verified is never turned into a tool, and nothing is available to a role until you grant it. = Does it work with WordPress versions before 6.9? = Yes. AtlasMCP bundles the WordPress Abilities API and MCP Adapter as vendor dependencies, so it works on WordPress 6.8 and above, even on versions where these APIs are not yet included in core. = Is AtlasMCP free? = Yes. The free plugin includes the full MCP server, unlimited abilities, third-party plugin support through the Abilities API, 24 WooCommerce store tools plus read-only tools from WooCommerce's REST API, one-click OAuth 2.1, role-based access control, all six AI experiments in both editors, three workflows, and the Error Debugger. Pro adds reach on top — the free plugin never stops working. = Can I control what the AI is allowed to do? = Yes, on several levels: toggle whole modules on or off, choose exactly which abilities are exposed over MCP, and assign per-role access so each connected AI client can only use what its WordPress user role allows. On the **Connections** screen you can make any app read-only, remove it, or pause all AI access at once. = Can the AI break my site? = The AI can only do what you allow. Every ability runs standard WordPress permission checks as the authenticated user, access is scoped by role and by your module/ability selection, OAuth is off by default, and you can make an app read-only, pause all AI access, or remove any connection with one click. The AI never gets more power than the WordPress user it connects as. = Is there a Pro version? = Yes! [AtlasMCP Pro](https://wpatlasmcp.com/pricing/) unlocks unlimited workflows, T/R/P access modes, advanced AI experiments (templates, batch variants, explain, history, shortcuts), workflow prompt builders, REST API tools from every plugin, per-ability RBAC, Error Debugger Pro, and priority support. It includes a **7-day free trial — no credit card required** — start it from the **Overview → Pricing** tab. The free plugin stays fully functional whether or not you try Pro. = Can I disable modules I do not need? = Yes. Each module has an independent toggle in the AtlasMCP dashboard. Disabled modules do not register their abilities or expose them via MCP. = Why do I see "AI analysis failed"? = This usually means no AI provider is configured. Go to **Settings → Connectors** and verify at least one provider is set up. Enable `WP_DEBUG_LOG` and check `debug.log` for lines beginning with `[AtlasMCP]`. = How does the Error Debugger work? = Enable the **Error Debugger** module from the dashboard. PHP errors in plugins and themes are tracked automatically and shown in the **Error Log** tab, and optional email alerts include a pre-filled **Fix Command** you can paste into any AI assistant for step-by-step fix instructions. With Pro, the command becomes an MCP tool call: paste it into Claude Desktop or Cursor and the AI reads the file, creates a backup, and applies the fix. A rate limiter prevents duplicate emails for the same error. = How do I get support? = Click the **"Contact Support"** button in the AtlasMCP dashboard, or visit: https://wpatlasmcp.com/contact/ --- = Can my customers shop with ChatGPT or Claude? = Yes, with AtlasMCP Pro and WooCommerce. The Shopping assistant adds a "Shop with AI" button to your store. Shoppers connect their own AI app, and it searches products, fills the cart and places the order through WooCommerce. It can never change your store, and card payments finish on your own checkout page. = Where do the older versions on the Versions screen come from? = From WordPress.org, the same place updates come from. The screen asks the WordPress.org plugin directory for the list of released versions only when you open it, and downloads a version only when you press Roll back. Nothing about your site is sent apart from the plugin's name. With AtlasMCP Pro installed, Pro's older versions come from Freemius using the licence already on the site. = Where do I report security bugs found in this plugin? = Please report security bugs found in the source code of the MCP Server for WordPress – Connect Claude, ChatGPT & Gemini | AtlasMCP plugin through the [Patchstack Vulnerability Disclosure Program](https://patchstack.com/database/vdp/d16b3c06-2fdf-45bf-9972-19ff3a180000). The Patchstack team will assist you with verification, CVE assignment, and notify the developers of this plugin. == Screenshots == 1. AtlasMCP dashboard with module toggles and provider status. 2. Workflow builder - drag abilities to create workflows. 3. Post editor meta box with ability selection and prompt preview. 4. Claude Desktop connected to WordPress via MCP. 5. AI Experiments - Excerpt generation in the block editor. 6. AI Experiments - Image generation in the block editor. --- == Changelog == = 1.9.3 (16 Oct 2026) = * Improved: Tools made from another plugin's REST API now use the description and name that plugin wrote for each endpoint, so your AI app understands what each tool does. * Fixed: A tool with only the generic "calls this endpoint" text could still get grade A. It now gets at most grade B, and the Abilities screen says why. If you only allow grade A tools from WooCommerce, check that setting after updating. * Improved: Every AtlasMCP REST API endpoint now explains what it does and what each value means, for developers and AI tools that read the API. * Improved: The Shopping assistant's visitor endpoints are no longer listed as a source of tools on the REST sources screen. * Fixed: An AI app that registers with a malformed redirect address is now refused with a clear message, and leaving out an optional field no longer writes a warning to the debug log. * Improved: The FAQ explains how to report a security issue privately. = 1.9.2 (9 Oct 2026) = * Improved: A shorter, clearer plugin description on WordPress.org, so the whole page shows again. * Improved: The privacy notes now mention the usage-data checkbox in the setup guide. = 1.9.1 (8 Oct 2026) = * New: Setup guide. A new site is walked from start to "my AI app answered a question": what you want AI to do, a check of your site, which tools to offer, connecting your AI app and a first question. Each step saves as you go, and you can leave and come back. * New: The site check can fix the most common sign-in problem for you: when your server drops the login header AI apps use, one click adds the missing line to .htaccess, after making a backup. * New: Sites that already use AtlasMCP get an optional setup check on Home instead. It shows your current settings and changes nothing unless you save a step. * Improved: The connection health check on the Connections screen and in the setup guide now share the same checks and fixes. = 1.9.0 (30 Sep 2026) = * New: Connections screen, first under MCP server. See every AI app, access token and app password that can use your site, who it acts as and when it was last used, and remove any of them. * New: Connect an AI app from the dashboard. Pick Claude, ChatGPT, Cursor, VS Code or Claude Code and follow the steps for that app; the screen tells you when it has connected and suggests a first question to ask. * New: Read-only connections. When you approve an AI app you can let it only look things up, never change anything, and switch it to full access later. * New: Pause all AI access with one switch, without disconnecting anything. Shoppers are not affected. * New: Connection health check. It finds what can stop AI apps reaching your site (HTTPS, permalinks, a server that removes the login header, a security plugin, a page cache) and says how to fix each one. * New: Create, name and revoke access tokens for scripts and automation tools on the Connections screen. * New: Versions screen. If an update breaks something, go back to an earlier release in one click, from the dashboard or the Roll back link on the Plugins page. Each version is checked against your site first, and your settings and connected AI apps are kept. * New: Shopping assistant (with AtlasMCP Pro and WooCommerce). A "Shop with AI" button lets customers shop your store with their own AI app, as a guest or with their account. * New: Redesigned Abilities screen. A tool budget shows how many tools your AI apps are offered, with a one-click trim, three clear tabs, and a side panel for each ability that shows what the AI reads and how often it was used. * New: Switch any single ability off for AI apps, one by one or in bulk, and see which abilities were used in the last 30 days. * New: Adding abilities from other plugins is previewed before it is saved, with Essentials, Read only and Everything starting points. * New: Sign-in for AI apps works when WordPress is installed in a subfolder. * New: After an update, a notice shows what is new and how to go back if something stopped working. * Changed: The old MCP Auth page now opens the Connections screen, so bookmarks keep working. * Improved: The Abilities screen opens at once on large sites. * Improved: Unused app registrations are cleaned up daily. * Fixed: Abilities from other plugins could go missing from the tool list on some sites. * Fixed: With LiteSpeed Cache or another page cache caching the REST API, the dashboard could show old settings. The plugin's screens are never served from a page cache now. * Fixed: Dashboard screens no longer say "saved" when the site refused the change. * Fixed: Error notification settings can be saved with the email field left blank. = 1.8.4 (27 Sep 2026) = * Fixed: tools you switch on and give to a role now always reach your AI app. On some sites, tools added after the plugin was first set up (a module switched on later, WooCommerce's REST API, Pro's tools) were quietly left out. Some sites will now see more tools in their AI app: these are tools you had already switched on. * New: Access control shows exactly which tools each role's AI app gets, with a count for every role and the full list one click away. If a ticked tool still doesn't reach the AI app, it tells you why. * New: tools you switch on go to Administrator automatically, and switching something off and on again gives them all back. Other roles only change when you change them. * New: after you switch something on, a short note beside the switch explains how the tools reach your AI app, and a reminder at the top tells you to reconnect Claude or ChatGPT. The reminder clears itself once your AI app has loaded the new list. * New: a warning with a one-click fix when tools are switched on but no role can use them. * Improved: messages after you save stay on screen until you close them. * Fixed: Access control could show more tools granted than exist, for example "173 of 54". = 1.8.3 (24 Sep 2026) = * New name: AtlasAI Connector is now AtlasMCP, with a new home at wpatlasmcp.com. Only the name and website change. Your settings, AI connections and MCP address stay exactly the same. * The dashboard, editor buttons, emails and links now use the new name. Pro, documentation and support links open wpatlasmcp.com. = 1.8.2 (23 Sep 2026) = * Security: fixed an issue where a harmful link, opened by a logged-in administrator, could change the site through its REST API. Thanks to Raphael P. Cigana, reported through WPScan. * Security: only administrators can now create, change or delete workflows, the shared AI prompts and prompt templates. Other roles can still use the workflows they are given. * Security: running a workflow now needs permission to edit that post, and only runs the abilities the user's role allows. * Security: an AI connection approved through OAuth now only works for the MCP connection itself, and its permissions can never be wider than what the app registered for. * Security: the connection approval page shows which website the approval goes to, and cannot be shown inside another site. * Security: AI connections and access tokens stop working when the user changes their password or is deleted. * Security: the AI generation history in the editor is cleaned before it is saved and shown. * Security: the debug log setting only accepts a log file, and the general REST tool can no longer reach the plugin's own settings. * Fix: the dashboard no longer shows "called incorrectly" notices for store abilities that are not loaded. = 1.8.1 (13 Sep 2026) = * Security: AI tools now follow WordPress permissions for each post, page and custom post type. Contributors and Authors can no longer read, change or delete other people's drafts and private posts, or publish when their role is not allowed to. * Security: the content tools (analysis, titles, excerpts, summaries, keywords, featured images and alt text) only work on posts and images the user is allowed to see. * Security: media file downloads now check that the user may view that file. * Security: showing plugin and theme code in the Error Debugger now needs permission to edit those files, and is switched off when file editing is disabled on the site. * Security: repeated wrong passwords when signing in for an access token are now limited. * What each role can use under Access Control is unchanged. * If you use AtlasAI Connector Pro, update it to 2.3.1 as well. You can update the two plugins in either order. = 1.8.0 (13 Sep 2026) = * New: an Activity log screen showing what your AI clients and editor tools actually did — which tool ran, which user and role it acted as, how long it took and whether it worked. * New: you can now choose to record the tool calls your AI clients make. This is off until you switch it on, under AtlasAI Connector → Activity log. * Fixed: tool calls stopped being recorded, and role limits stopped being applied to the tool list, after an update to the underlying MCP library. * Fixed: AI clients could not connect on sites that also run another plugin with its own MCP connection, such as Rank Math or Imagify. Both now work side by side, each with its own connection details, so your AI client reaches the right one. * Fixed: on multilingual sites the connection URL changed with the language of the page you copied it from. It is now the same address everywhere. * Fixed: the MCP settings screen now shows the exact address your AI client needs. * Improved: the Documentation screen is now a short guide to every screen, with links to step-by-step articles and screenshots. The Documentation button at the top opens it. * Security: removed an old, hidden access token setting that could let AI clients connect without a WordPress user. If your site still had one, you will see a notice explaining how to reconnect. * Fixed: another plugin that ships an older copy of the MCP connection library, such as Rank Math, could take over from ours and stop role limits and tool-call recording from working. AtlasAI Connector now uses its own private copy, so other plugins can no longer interfere with it. * Fixed: with Imagify installed, AI clients connecting to Imagify could be sent AtlasAI Connector's sign-in details instead of Imagify's. * Fixed: a long list of repeated warning messages in the admin area. * Fixed: every request from an AI client wrote thousands of error lines to the WordPress debug log on sites with WooCommerce connected. The log stays quiet now. * Your existing AI client connections keep working, and your server address has not changed. * If you use AtlasAI Connector Pro, update it to 2.3.0 as well to keep its workflow prompts. You can update the two plugins in either order. == Upgrade Notice == = 1.9.3 = Tools made from other plugins' REST APIs now use those plugins' own descriptions, and their grades are more accurate. Your settings and connected AI apps are not changed. Pro users should update AtlasMCP Pro to 2.4.2 too. = 1.9.2 = A shorter plugin description on WordPress.org. No changes to how the plugin works. = 1.9.1 = New setup guide that walks you from install to your AI app's first answer, with a site check that can fix the common login-header problem in one click. Existing settings stay as they are. Pro users should update AtlasMCP Pro to 2.4.1 too. = 1.9.0 = New Connections screen: connect AI apps in one click, make an app read-only or pause all AI access. New Versions screen to go back to an earlier version if anything goes wrong. Shopping assistant for WooCommerce with AtlasMCP Pro 2.4.0. Pro users should update AtlasMCP Pro to 2.4.0 too. = 1.8.4 = Tools you switch on now reliably reach your AI app, and Access control shows exactly what each role's AI app gets. After updating, reconnect your AI app once so it loads the full list. Pro users should also update to AtlasMCP Pro 2.3.4. = 1.8.3 = AtlasAI Connector is now called AtlasMCP. Only the name and website change; your settings and AI connections keep working as before. Pro users should also update to AtlasMCP Pro 2.3.3. = 1.8.2 = Security update, recommended for all sites: fixes an issue that could let a harmful link change the site when opened by an administrator, and tightens who can change workflows and prompts. Pro users should also update to Pro 2.3.2. = 1.8.1 = Security update, recommended for all sites: AI tools now follow WordPress permissions for each post, media file and plugin file, and repeated wrong passwords are limited. Pro users should also update to Pro 2.3.1. = 1.8.0 = Adds an Activity log showing what your AI clients did, and optional recording of their tool calls. Fixes conflicts with other plugins that have their own MCP connection, such as Rank Math and Imagify, and a wrong connection URL on multilingual sites. Existing connections are unaffected. Pro users should also update to Pro 2.3.0. = 1.7.2 = Draft a full post, page or product description from a topic, without leaving the editor. Long answers no longer time out, and editing prompts is far easier. = 1.7.1 = Adds a short guide on the Abilities screen for turning your other plugins into AI tools, plus a clearer plugin description. Safe to update. = 1.7.0 = Adds WooCommerce AI tools and makes abilities from other plugins free. Rebuilt Abilities and Access control screens; nothing is exposed to an AI until you grant it. Safe to update. = 1.6.7 = Compatibility update for WordPress 7.1 and the official AI plugin 1.3.0. AI actions can now be recorded in the AI plugin's request log, and usage is broken down by provider and model; safe to update. = 1.6.6 = Fixes a debug-log notice on WordPress 6.7+; safe to update. = 1.6.5 = Minor compatibility and polish update — improves MCP responses for strict AI clients; safe to update. = 1.6.4 = The five AI writing tools now integrate with the official WordPress AI plugin and work in the Classic Editor; alt text is generated from the actual image, and your editorial guidelines are applied to titles, images, and alt text.