=== 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: 2.0.0 License: GPLv2 or later License URI: https://www.gnu.org/licenses/gpl-2.0.html Let Claude, ChatGPT or Gemini do what you can do in wp-admin, in any plugin. Direct MCP server, no middleman, no call limits, every change undoable. == Description == **AtlasMCP turns your WordPress site into an MCP server, so the AI app you already use can do everything your WordPress role allows — in WordPress and in any plugin — straight from the chat.** Ask Claude, ChatGPT, Gemini, Cursor or Claude Code to write and fix posts, change a page built with Elementor, clear a cache, update your SEO plugin's settings, or refund a WooCommerce order, and it happens on your site with your permissions. * **Direct, no middleman.** The AI app talks straight to your site. There is no AtlasMCP account, no relay server, and your content never passes through us. * **We never count or limit tool calls.** Not in the free plugin, not in any Pro plan. * **Every change can be undone.** Each AI change is recorded with how it looked before; undo it from the Activity log in one click. * **Your role is the permission.** A connection acts as a WordPress user and can never do more than that user can do in wp-admin. = 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". 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 and choose what the app may do — **Full by role**, **Read only** or **Content only** — and the screen tells you the moment the app is connected. No tokens to copy. Scripts can use an access token or an Application Password instead. = Everything your role can do, in any plugin = There is no "enable tools first" step. What the connecting user may do in wp-admin, the AI app may do: * **Content:** posts, pages, any custom post type, categories, tags, custom fields; change one block of a post without rewriting the rest; list, compare and restore revisions; find and replace across content, after a preview; media from a web address or your computer, with alt text and captions; comments, replies and moderation. * **Site:** menus, widgets, block templates, global styles, site settings (with a protected list), users and roles (never the last administrator, never a role above the caller). * **Any plugin's settings:** read and change the saved settings of SEO, cache, multilingual, feed, invoice and ad plugins. Keys, passwords and core settings stay locked. * **SEO plugins:** SEO title, description, focus keyword, canonical and indexing of any post, in Yoast SEO, Rank Math, All in One SEO, SEOPress, The SEO Framework and Slim SEO. * **Advanced Custom Fields:** list field groups, read and change field values. * **Any plugin's content and API:** every ability other plugins register through the WordPress Abilities API, every plugin's REST API as tools (reads and writes), and every post type and taxonomy a plugin adds. * **Plugin actions:** safe one-step jobs your plugins offer — clear a cache, rebuild a sitemap, regenerate a feed, run a scheduled task. * **Plugins and themes:** install from WordPress.org, activate, update, deactivate and switch themes. A backup is made first, the site is checked after, and it is put back by itself if it stops answering. * **Database and files, read only:** table sizes, autoload, a cleanup report, read-only queries and theme or plugin files. = WooCommerce AI agent = Products, variations, stock, orders, order notes, refunds, coupons, customers and sales reports. Bulk jobs change hundreds of products in the background (titles, prices, a sale for a category) and can be undone as one job. Refunds always ask first. = Page builders, by element = The AI app reads an Elementor page as an outline of sections, containers and widgets with their ids, and changes one element at a time: a heading, a text, a button, an image, colours, page settings; or it adds, moves, duplicates and removes elements. Saves go through Elementor itself, a copy of the design is kept before every change, and undo rebuilds the page's CSS. Elementor V4 (atomic) elements are read only. Beaver Builder, Bricks and Divi 4 pages can be read and changed by element too, and block-based builders such as Kadence and GenerateBlocks work through the block tools. = Approve and upload inside the chat = In apps that show panels, such as Claude, AtlasMCP opens a panel right in the chat. Before something is removed or replaced you see what will change, with **Approve**, **Decline** and **Request changes** buttons. To add files, drag them from your computer into the upload panel. Other AI apps ask you in words instead. = Search, traffic and security data = Connect your own Google account and the AI app can read Search Console queries and Analytics reports; connect your own Semrush key and it can read domain and keyword figures. Your site talks to these services directly, and nothing is sent until you connect. A read-only security checklist looks at waiting updates, HTTPS, administrators, users with extra powers and unlisted plugin folders, and the AI app can read Wordfence and Solid Security findings. = Safety you can see = * **Undo journal:** every AI write is recorded with its before-state for 7 days; undo or redo it from **Activity log → Changes**. * **Checkpoints:** a backup of files or tables before risky changes, restored from **Versions → Checkpoints**. * **Ask before deleting:** the AI app shows you what will be removed and waits for your yes in the chat. * **Dry run:** any change can be previewed first, without changing anything. * **New content starts as a draft:** an optional switch, so nothing an AI app creates goes public on its own. * **Tool calls per minute:** an optional limit you set yourself, for a site or host that needs less traffic. It is off by default, and no plan changes it. * **Hard locks:** the last administrator, your own account, AtlasMCP itself, keys and core files can never be changed by an AI app. * **Pause, read-only and safe mode:** pause all AI access with one switch, make any app read only, or define `AWFAH_SAFE_MODE` to refuse every write. * **Connections screen:** every app, token and app password, who it acts as and when it was last used, with one-click disconnect and a health check. = Multisite = On a network, each site keeps its own MCP address, apps, limits and undo history, and a site administrator's AI app works on that site only. Network tools — list sites, create a site, network-activate a plugin, network settings — are for super admins only. Network Admin shows every site with a pause switch. = AI writing in the editor = Six panels in both the Block Editor and the Classic Editor: full content generation, excerpts, title suggestions, summaries, featured images and alt text, on your own AI provider (OpenAI, Google or Anthropic through the WordPress AI Client). AtlasMCP works with the official [AI plugin](https://wordpress.org/plugins/ai/) and the official [MCP Adapter](https://wordpress.org/plugins/mcp-adapter/) instead of competing with them. = Site health = A connection health check (HTTPS, permalinks, the login header, security plugins, page caches), one-click roll back to an earlier AtlasMCP version, and an Error Debugger with email alerts and a copy-paste fix command for any AI assistant. = AtlasMCP Pro = The free plugin never breaks a site and is complete on its own. [AtlasMCP Pro](https://wpatlasmcp.com/pricing/) adds power, development and governance: a development pack (theme and plugin code on a draft copy with syntax check, preview, publish with backup and automatic roll back; new child themes and plugins; SQL writes with a dry run; install from a ZIP), design a whole site from a brief, workflows ("when this happens, do that": triggers, conditions and any tool as an action, with AI steps, webhooks, templates and scheduled agent jobs), 1-year undo with a signed audit export, per-tool access and approval rules, the Shopping assistant, an AI error fixer and an agency sites list. Every Pro plan has the same features; plans differ only in the number of sites, and none counts tool calls. == 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. = Google Search Console and Google Analytics (only if you connect them) = If you paste a Google service account key under **Tools → Add from plugins → Data sources**, your site signs in at `oauth2.googleapis.com` and asks `www.googleapis.com` (Search Console) and `analyticsdata.googleapis.com` (Analytics) for the reports an AI app or you request. Your site talks to Google directly and sends only the report request. Nothing is sent before you connect. [Google Terms of Service](https://policies.google.com/terms) · [Privacy Policy](https://policies.google.com/privacy) = Semrush (only if you connect it) = If you enter a Semrush API key on the same screen, your site sends that key and the domain or keyword asked about to `api.semrush.com` and `www.semrush.com`, and each report uses your own Semrush API units. Nothing is sent before you connect. [Semrush Terms of Service](https://www.semrush.com/company/legal/terms-of-service/) · [Privacy Policy](https://www.semrush.com/company/legal/privacy-policy/) = 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`. When an AI app (or you) installs or updates a plugin or theme with the plugins and themes tools, the package is downloaded from `downloads.wordpress.org`, the same place WordPress's own updates come from. Only the plugin or theme 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? = Three things. It reaches **everything your role can do in wp-admin, in any plugin** — settings, content, REST APIs, plugin actions — instead of a fixed list of tools. It is **direct**: no AtlasMCP account or relay server, and we **never count or limit tool calls**. And **every change can be undone** from the Activity log, with backups before risky changes and approval in the chat before anything is deleted. It also brings AI writing panels to both the Block Editor and the Classic Editor. = 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. The same screen has the steps 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 the official MCP Adapter plugin? = Yes, install both. The MCP Adapter keeps its own server and AtlasMCP keeps its own, so an AI app can connect to either. AtlasMCP's tools are offered only through AtlasMCP's server, so pausing AI access, read-only connections and your role settings cover them however an AI app connects. Abilities that other plugins mark as public stay on the MCP Adapter's server as before. The Connections screen health check confirms both are working. = Does it work with WooCommerce? = Yes. While WooCommerce is active, the AI app can manage products, variations, stock, orders, notes, refunds, coupons, customers and sales reports through the same MCP server. Refunds always ask first, and bulk jobs can be undone as one job. = 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. AtlasMCP ships tools for WordPress itself, WooCommerce, Elementor, plugin settings and plugin actions, and adds every ability other plugins register through the WordPress Abilities API and every plugin's REST API. Install more plugins and the 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. Tools are only built when an AI app or an AtlasMCP screen asks for them. If an AI app picks the wrong tool on a very large site, switch off the groups you do not need in **Tools → Groups**. = Does it work with my other plugins? = Yes, in several ways, all free: abilities other plugins register through the WordPress Abilities API, every plugin's REST API as tools (reads and writes; a plugin you add starts read only), every plugin's saved settings (with a protected list), its post types, taxonomies and custom fields, and the safe one-step actions it offers, such as clearing a cache or rebuilding a sitemap. = Can an AI change my WooCommerce store? = Yes, as far as the connecting user may. Products, stock, orders, notes, coupons and customers can be changed; refunds always ask you first in the chat; bulk jobs run in the background and can be undone as one job. Choose **Read only** when you connect if the app should only look. = 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 is complete: the direct MCP server with one-click sign-in, everything your role can do in any plugin, WooCommerce, Elementor editing by element, installs from WordPress.org with backups, the undo journal and other safety features, multisite support, the six editor AI panels and the Error Debugger. There is no limit on tool calls. = Can I control what the AI is allowed to do? = Yes. The connecting user's WordPress role is the permission. On top, pick a preset when you approve an app (**Full by role**, **Read only** or **Content only**), switch off whole tool groups or single tools, limit what each role may use in **Access control**, keep **Ask before deleting** on, or pause all AI access with one switch. = Can the AI break my site? = AtlasMCP is built so it cannot leave your site broken. Every AI change is recorded and can be undone; plugin and theme changes make a backup first and are put back automatically if the site stops answering; deletes wait for your yes in the chat; the last administrator, AtlasMCP itself, keys and core files are locked. Writing code, SQL writes and installs from outside WordPress.org are not in the free plugin at all. = Is there a Pro version? = Yes. [AtlasMCP Pro](https://wpatlasmcp.com/pricing/) adds a development pack, design a site from a brief, workflows with AI steps and agent jobs, 1-year undo with a signed audit export, per-tool access and approval rules, the Shopping assistant, an AI error fixer, advanced editor AI and an agency sites list. Every Pro plan has the same features; plans differ only in sites, and none counts tool calls. The free plugin keeps working whether or not you use Pro. = Where are workflows? = Workflows ("when this happens, do that") are part of [AtlasMCP Pro](https://wpatlasmcp.com/pricing/). If you made workflows with an earlier version of this plugin, they stay on your site exactly as they were, with their run history, and they run again as soon as AtlasMCP Pro is active. Nothing is deleted. = Can I disable modules I do not need? = Yes. In **Tools → Groups** each group of tools has its own switch. These are optional limits: a group that is off is not offered to AI apps. = 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. = Does AtlasMCP count or limit tool calls? = No, never, in any version. The AI app talks straight to your site, so there is no relay or quota in between. Your host's own limits are the only limits. = Does my site's data pass through AtlasMCP's servers? = No. There is no AtlasMCP account and no relay. The AI app you connect calls your site directly; your content only goes to that app. The optional services listed under External services run only when you press their buttons or opt in. = Can I undo what the AI did? = Yes. Open **Activity log → Changes**: every AI change is listed with how it looked before and after, and **Undo** puts it back (kept 7 days). Plugin and theme changes also make a checkpoint you can restore in **Versions → Checkpoints**. = Does it work with Elementor and other page builders? = Yes. The AI app reads an Elementor page as an outline of elements with ids and changes one element at a time (text, headings, buttons, images, page settings; add, move, duplicate or remove an element), saved through Elementor so the page's CSS is rebuilt, with undo. Elementor V4 atomic elements are read only. Beaver Builder, Bricks and Divi 4 pages can be read and changed by element, and block-based builders use the block tools. = Does it work with Yoast SEO, Rank Math and other SEO plugins? = Yes. The AI app reads and changes a post's SEO title, description, focus keyword, canonical address and indexing in Yoast SEO, Rank Math, All in One SEO, SEOPress, The SEO Framework and Slim SEO, and every change can be undone. = Can the AI read my Search Console, Analytics and Semrush data? = Yes, with your own accounts. Connect them under **Tools → Add from plugins → Data sources**. Keys are stored encrypted, your site talks to each service directly, and nothing is sent until you connect. = Can I see a change before it happens? = Yes. Any write tool can run as a dry run, which shows what would change and changes nothing. Removing or replacing something waits for your approval, in a panel inside the chat in apps that show panels, such as Claude. = Does it work on multisite? = Yes. Each site keeps its own MCP address, apps and undo history, and site administrators work on their own site. Network tools (sites, new sites, network plugins and settings) are for super admins only, and Network Admin lists every site with a pause switch. = 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. Approve a change inside the chat: see what will change, then Approve, Decline or Request changes. 2. Add files from your computer with the upload panel inside the chat. 3. Connections: every AI app that can use your site, what it may do and when it was last used. 4. Tools: every tool your AI apps are offered, from WordPress and from your other plugins. 5. Activity log: every change an AI app made, with Undo. 6. Safety settings: ask before deleting, new content starts as a draft, and tool call limits. 7. Add from plugins: page builders and your own Search Console, Analytics and Semrush accounts. 8. AI writing in the editor, on your own AI provider. == Changelog == = 2.0.0 (30 Oct 2026) = * New: Your AI app can do everything your WordPress role allows, in WordPress and in any plugin, with no tools to switch on first. Sites that already limited what AI apps may do keep those limits. * New: Every change an AI app makes can be undone from Activity log → Changes for 7 days. * New: Removing or replacing something waits for your approval. In apps that show panels, such as Claude, you get a panel in the chat with Approve, Decline and Request changes. * New: Add files from your computer with an upload panel in the chat, or from a web address. * New: Any change can be previewed first without changing anything. * New: Change one block of a post instead of rewriting it, compare and restore revisions, and find and replace across content after a preview. * New: Tools for Yoast SEO, Rank Math, All in One SEO, SEOPress, The SEO Framework, Slim SEO and Advanced Custom Fields. * New: Edit Elementor, Beaver Builder, Bricks and Divi 4 pages one element at a time. * New: Read your own Search Console, Analytics and Semrush figures. Nothing is sent until you connect an account. * New: A security checklist, and Wordfence and Solid Security findings for your AI app. * New: Change plugin settings, run plugin actions, manage menus, widgets, comments, roles and templates, install and update plugins with a backup first, and bulk edit WooCommerce products. * New: Checkpoints: a backup of files or tables before risky changes, with one-click restore. * New: Optional switches: new content starts as a draft, and a limit on tool calls per minute. Both are off until you turn them on. * New: Multisite support, with a Network Admin screen and tools for super admins. * New: A completely redesigned dashboard that works like a desktop app. * Changed: Workflows are now part of AtlasMCP Pro. Workflows you saved are kept and run again as soon as Pro is active. They do not run without Pro. * Changed: The plans now have monthly billing, and there is no free trial. Every plan has a 14-day money-back guarantee. * Fixed: Clearer messages when a site switches off file editing, and when a table does not exist. * If you use AtlasMCP Pro, update it to 3.0.0 as well. = 1.9.4 (20 Oct 2026) = * Improved: Works side by side with the official MCP Adapter plugin. Its own MCP server keeps working when both are installed, and AtlasMCP's tools are offered only through AtlasMCP, so your pause switch, read-only connections and access rules always apply. * Improved: The built-in MCP Adapter is updated to 0.7.1. It supports the newest MCP protocol version and includes a security fix for stored connection data. * Fixed: AI apps could not read AtlasMCP's MCP resources. Every listed resource now loads. Addresses that need a value, such as a post ID, are no longer listed as resources; the matching tools still do this. * Improved: The health check on the Connections screen tells you when the official MCP Adapter plugin is active and how the two work together. * Connected AI apps reconnect once after this update. = 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 == = 2.0.0 = Major update: your AI app can do what your role allows in any plugin, with undo and approval in the chat. Workflows now need AtlasMCP Pro; saved ones are kept. Pro users must update to Pro 3.0.0 too. Reconnect your AI app once to load the new tools. = 1.9.4 = Works side by side with the official MCP Adapter plugin, updates the built-in MCP Adapter to 0.7.1 with a security fix, and makes MCP resources readable. Connected AI apps reconnect once. Works with AtlasMCP Pro 2.4.2. = 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.