=== MCP Server for WordPress – Connect Claude, ChatGPT & Gemini | AtlasAI Connector === Contributors: hasanazizul, atlasaidev Donate link: https://atlasaidev.com/ Tags: mcp, mcp-server, ai, claude, chatgpt Requires at least: 6.8 Tested up to: 7.0 Requires PHP: 7.4 Stable tag: 1.6.5 License: GPLv2 or later License URI: https://www.gnu.org/licenses/gpl-2.0.html MCP server for WordPress to connect Claude, ChatGPT & Gemini via one-click OAuth. 80+ AI abilities, block editor AI, RBAC & WooCommerce. == Description == **AtlasAI Connector is the only WordPress MCP server that pairs 80+ built-in AI abilities with AI writing tools in both the Block Editor and the Classic Editor.** 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. On top of the 80+ built-in abilities, Pro auto-discovers **10+ external abilities** from the official WordPress AI plugin, WooCommerce, and WordPress core — so abilities other plugins expose become AI tools too. Generate excerpts, feature images, summaries, titles, and alt text without leaving the post — while **role-based access control** and **one-click OAuth 2.1 connect** keep every AI connection under your control. = Connect Claude to WordPress = Activate the plugin and your WordPress MCP server endpoint goes live at `/wp-json/awfah_mcp/mcp`. Enable one-click OAuth 2.1 under **MCP Auth**, paste that URL into Claude.ai or Claude Desktop as a custom connector, approve the consent screen, and Claude is connected to WordPress — no manual tokens to copy. = Connect ChatGPT, Cursor, Windsurf & Claude Code to WordPress = The same MCP endpoint connects ChatGPT (via OpenAI connectors), Cursor, Windsurf, Claude Code, Gemini CLI, and any other MCP-compatible client. Use one-click OAuth 2.1 where the client supports it, or fall back to JWT and Application Password authentication — per-client setup guides are included in the documentation. = Works with the official WordPress AI plugin = AtlasAI Connector integrates with the official [AI plugin](https://wordpress.org/plugins/ai/) instead of running a parallel system: * Our five AI experiments appear as **feature cards on its Settings → AI screen**, right beside the built-in ones. * They **respect the AI plugin's per-feature toggles** — one screen controls everything. * The AI plugin's **editorial Guidelines are injected into every prompt** automatically, so generated content stays on brand. * You can **hide the AI plugin's duplicate experiments** — per experiment or globally — from the AtlasAI Connector dashboard, so editors see one AI button, not two. = Classic Editor supported = All five AI experiments also work in the **Classic Editor** — unlike the official AI plugin, which is Block Editor only: * Excerpt generation, title suggestions, and post summarization on the classic edit screen. * AI feature image generation in the Featured Image box. * Image alt text from the media modal — the AI is sent the actual image (vision), so it describes what is really in it. If your site still runs the Classic Editor — as millions do — you get the same AI tools without switching editors. = Why AtlasAI Connector? = * **Connect any AI client** — Claude Desktop, Claude.ai, ChatGPT, Cursor, Windsurf, Gemini CLI, or any MCP-compatible tool, over standard JSON-RPC 2.0. * **MCP server + AI content in one plugin** — most WordPress MCP plugins do one or the other. AtlasAI Connector does both. * **80+ ready-to-use abilities** — exposed to AI as tools, resources, and prompts, including 26 WooCommerce store abilities, plus 10+ auto-discovered external abilities (Pro). * **Secure by design** — OAuth 2.1 with PKCE + dynamic client registration, plus JWT and Application Password support, and per-role access control so each AI connection only sees what its WordPress user is allowed to use. * **Works on WordPress 6.8+** — bundles the WordPress Abilities API and MCP Adapter, so you do not have to wait for the WordPress versions where these ship in core. * **Multi-provider AI** — OpenAI, Google Gemini, or Anthropic Claude via the WordPress AI Client; provider keys set once under Settings → Connectors are shared with WordPress core AI features. * **Workflow builder** — combine abilities into reusable workflows from the dashboard or the post editor meta box. = Modules — 80+ abilities, individually toggleable = Each module can be enabled or disabled independently of the **AtlasAI Connector** dashboard: 1. **AI Content Steward (8 abilities)** — AI content analysis, generation, and improvement. 2. **Posts Manager (13)** — full CRUD for posts, categories, and tags. 3. **Pages Manager (5)** — CRUD for WordPress pages. 4. **Media Manager (7)** — upload, update, and manage media files. 5. **Users Manager (7)** — search, create, and manage users. 6. **Custom Post Types Manager (6)** — CRUD for any registered custom post type. 7. **REST API Tools (3)** — discover and execute any WordPress REST endpoint dynamically. 8. **Site Info & Diagnostics (4)** — site info, plugins, themes, and users at a glance. 9. **Settings Manager (3)** — view and update WordPress settings. 10. **AI Store Manager — WooCommerce (26)** — products, categories, tags, brands, orders, and sales reports. Requires WooCommerce. 11. **Error Debugger (4)** — real-time PHP error monitoring with AI fix commands (details below). 12. **External Abilities (Pro)** — auto-discovers 10+ abilities registered by the official WordPress AI plugin, WooCommerce, and WordPress core, and exposes them through the same MCP server, workflows, and access control. = WooCommerce AI Agent — 26 Store Abilities = Turn Claude or ChatGPT into a WooCommerce AI agent: search and manage products, product categories, tags, and brands, review orders, and pull sales reports by chatting with your connected AI assistant. All 26 store abilities go through the same MCP server, workflows, and role-based access control, and register only when WooCommerce is active. = AI Content Generation in the Block Editor & Classic Editor = Five experiment panels run on your configured AI provider (OpenAI, Google Gemini, or Anthropic Claude), in both the Block Editor and the Classic Editor: * **Excerpt Generation** — one-click, SEO-friendly excerpts with tone/style presets. * **Title Suggestions** — multiple SEO-friendly title ideas to pick from. * **Summarization** — concise, neutral post summaries. * **Feature Image Generation** — AI feature images generated from your post content. * **Alt Text Generation** — vision-based alt text: the AI is sent the actual image, not just the filename, so descriptions reflect what is really in the picture. Every panel ships with editable prompts, tone/style presets, and ready-made prompt templates — free. **Pro extends every experiment** with a **prompt templates library** (save and reuse your own prompts), **batch variants** (generate and compare multiple variations at once), **generation history** (review and restore past results per post), "Explain This Generation", and keyboard shortcuts. = Error Debugger = Monitor PHP errors from plugins and themes in real time — no configuration required. Free: an error log grouped by file, email alerts with a copy-paste **Fix Command** for any AI assistant, and an admin dashboard widget. Pro: an **MCP Fix Command** you paste into Claude Desktop or Cursor so the AI reads the file, creates a backup, and applies the fix — plus Slack/Discord webhooks, a Backups Manager, and extended sources (Core, MU-Plugins, Drop-ins). = WordPress Abilities API Support = AtlasAI Connector is built on the **WordPress Abilities API** — every ability is registered through the standard API and exposed over MCP via the official MCP Adapter. Both are bundled as vendor dependencies, so everything works on WordPress 6.8+ today, before these APIs ship in your version of core. With Pro, abilities that other plugins register via the Abilities API are auto-discovered and become MCP tools too. = Works with the WordPress AI ecosystem = AtlasAI Connector is built on the same **AI Building Blocks** as WordPress core — the **AI Client** and the **Abilities API**. Add your provider key once under **Settings → Connectors**, using the official [AI Provider for OpenAI](https://wordpress.org/plugins/ai-provider-for-openai/), [AI Provider for Google](https://wordpress.org/plugins/ai-provider-for-google/), or [AI Provider for Anthropic](https://wordpress.org/plugins/ai-provider-for-anthropic/) plugins, and AtlasAI Connector reuses it for its MCP server and AI experiments — no duplicate setup. = AtlasAI Connector Pro = [AtlasAI Connector Pro](https://atlasaidev.com/atlas-ai-connector-pro/) adds: * **Unlimited Workflows** — free version allows 3. * **T/R/P Access Modes** — per-ability Tool/Resource/Prompt toggles for fine-grained MCP control. * **Advanced AI Experiments** — prompt templates library, batch variants, explain reasoning, generation history, keyboard shortcuts. * **Workflow Prompt Builders** — 6 pre-built prompt workflows (SEO Audit, Content Brief, Site Overview, and more). * **External Abilities** — auto-discover abilities from the official WordPress AI plugin, WooCommerce, and core. * **Per-Ability RBAC** — assign individual abilities (not just modules) to each WordPress role. * **Error Debugger Pro** — MCP Fix Command with automatic backups, Slack/Discord webhooks, Backups Manager. * **Priority Support** — plus a 7-day free trial, no credit card required. == Connecting AI Agents == = Connect your AI client = First, in WordPress admin go to **AtlasAI Connector → MCP Auth**, enable **One-click OAuth 2.1 connect**, and copy your server URL — it looks like `https://your-site.com/wp-json/awfah_mcp/mcp`. Then: * **Claude Desktop** — Settings → Connectors → **Add custom connector**, paste the server URL. Your browser opens the OAuth consent screen automatically — click **Allow** and your abilities appear as tools. * **Claude.ai (web)** — Settings → Connectors → **Add custom connector**, paste the server URL, and approve the consent screen that opens in your browser. * **ChatGPT** — Settings → **Apps & Connectors** → enable Developer Mode → create a new connector with the server URL (requires a ChatGPT plan with connector support). The OAuth consent opens in your browser. * **Cursor** — Settings → **MCP** → Add new MCP server and paste the server URL (or add it to `.cursor/mcp.json` as a `"url"` entry), then approve the OAuth prompt in your browser. * **Windsurf** — Windsurf Settings → **Cascade → MCP servers** → add a server with the URL as `serverUrl` in `mcp_config.json`, refresh, and approve the browser consent. * **Gemini CLI** — run `gemini mcp add --transport http wordpress https://your-site.com/wp-json/awfah_mcp/mcp`, then `/mcp auth` inside the CLI to complete the browser consent. In every case the OAuth browser consent happens automatically — no client IDs, secrets, or tokens to copy. If your client cannot complete OAuth (headless/CI use, plain-HTTP local sites, or a subdirectory WordPress install), use the fallback instead: a **JWT token or WordPress Application Password** sent as an `Authorization: Bearer` header — full steps under **MCP Auth → Documentation → "MCP Client Setup Guide"**. = How the OAuth connection works (in brief) = AtlasAI Connector is its own OAuth 2.1 authorization server — your WordPress site is the identity provider. A connecting client discovers the server from `.well-known` metadata (RFC 9728 / RFC 8414), registers itself via Dynamic Client Registration (RFC 7591), and completes a PKCE authorization-code exchange (RFC 7636) after you approve the consent screen in your browser. The access token maps to your WordPress user, so your role and the per-role Access Control govern exactly what the connection can do. Review or revoke connected clients anytime under **MCP Auth → Connected clients**. By default only users who can edit posts may authorize a connection (change it with the `awfah_oauth_authorize_min_capability` filter). = Role-based MCP access = Different WordPress users see different abilities depending on their role. Configure it under the **Access Control** tab: pick a role, check the abilities (and workflows) it may use, and save — changes apply immediately to every MCP connection authenticated as that role. An Administrator connection can use all 80+ abilities while an Editor connection is limited to content abilities only, and you can run both side by side in the same AI client using two accounts. == 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. AtlasAI Connector 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 AtlasAI Connector different from other WordPress MCP plugins? = Most WordPress MCP plugins give you a server only. AtlasAI Connector pairs the full MCP server (80+ abilities, OAuth 2.1, role-based access control, workflows) 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 connect Claude to WordPress? = Enable **one-click OAuth 2.1** under **MCP Auth**, then add your server URL (`https://your-site.com/wp-json/awfah_mcp/mcp`) as a custom connector in Claude.ai or Claude Desktop and approve the consent screen — no tokens to copy. See the **Connect your AI client** section above for ChatGPT, Cursor, Windsurf, and Gemini CLI steps. = 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? = One-click OAuth discovery uses `.well-known` URLs at the **domain root**, so it requires WordPress installed at the root of the domain (`https://example.com`, not `https://example.com/blog`) and served over HTTPS. On subdirectory installs, connect with the **JWT or Application Password** fallback instead — see **MCP Auth → Documentation**. = Does it work with the Classic Editor? = Yes. All five AI experiments — 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 26 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 abilities does the plugin register? = Over **80 abilities** across 11 modules: Content Steward (8), Posts (13), Pages (5), Media (7), Users (7), Custom Post Types (6), REST API Tools (3), Site Info (4), Settings (3), WooCommerce Store Manager (26), and Error Debugger (4) — plus 10+ external abilities auto-discovered from the official WordPress AI plugin, WooCommerce, and core with Pro. = Does it work with WordPress versions before 6.9? = Yes. AtlasAI Connector 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 AtlasAI Connector free? = Yes. The free plugin includes the full MCP server, 80+ abilities, one-click OAuth 2.1, role-based access control, all five AI experiments in both editors, three workflows, and the Error Debugger. Pro adds advanced features 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. Connected OAuth clients can be revoked at any time from MCP Auth. = 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 revoke any client with one click. The AI never gets more power than the WordPress user it connects as. = Is there a Pro version? = Yes! [AtlasAI Connector Pro](https://atlasaidev.com/atlas-ai-connector-pro/) unlocks unlimited workflows, T/R/P access modes, advanced AI experiments (templates, batch variants, explain, history, shortcuts), workflow prompt builders, external abilities, 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 AtlasAI Connector 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 `[AtlasAI Connector]`. = 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 AtlasAI Connector dashboard, or visit: https://atlasaidev.com/contact-us/ --- == Screenshots == 1. AtlasAI Connector 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.6.5 (19 Jul 2026) = * Compatibility and polish update — improved MCP responses for strict AI clients, fixed special-character display, and refreshed the plugin listing. = 1.6.4 (18 Jul 2026) = The AI writing tools now plug into the official WordPress AI plugin and work in the Classic Editor. * **Official WordPress AI plugin integration** — the five AI writing tools (excerpt, title, summary, featured image, and alt text) now appear as experiments inside the official AI plugin alongside its own, so you can manage them all in one place. They keep working as before when that plugin isn't installed. * **Classic Editor support** — all five AI writing tools are now available in the Classic Editor, not just the block editor. * **Editorial guidelines everywhere** — your saved editorial guidelines are now applied when generating titles, featured images, and alt text, so results follow your site's style. * **Smarter alt text** — alt text is now generated by analyzing the actual image, producing accurate descriptions instead of guesses based on the surrounding text. * **Live setup checklist** — the Home screen's "Get started" steps now reflect your real setup: they tick when OAuth is enabled and an AI client is connected, and untick if you revoke access. * Consistent "AtlasAI Connector" naming across the dashboard. = 1.6.3 (29 Jun 2026) = * Documented compatibility with the WordPress AI ecosystem — Atlas AI Connector works with the WordPress AI plugin and the official OpenAI, Google, and Anthropic connector plugins, sharing the same Settings → Connectors keys. * Updated plugin tags. = 1.6.1 (29 Jun 2026) = Fixes a critical error that could prevent the plugin from loading on some sites. * Fixed a critical error that, on some installations, stopped the plugin from loading correctly. Updating is strongly recommended. = 1.6.0 (29 Jun 2026) = Redesigned dashboard, new AI Experiments settings, and a dedicated Plans & pricing page. * **New dashboard** — a simpler side menu with a Home overview that shows your setup at a glance. * **AI Experiments settings** — turn each block-editor AI tool on or off and choose which provider it uses. * **Plans & pricing page** — compare Free and Pro side by side, with the 14-day money-back guarantee and 7-day free trial. * **Clearer connections** — the renamed "AI Connectors" panel shows what's connected at a glance. * **Easier setup** — a step-by-step guide for connecting Claude, ChatGPT, and Cursor. * **WordPress 7.0 ready** — works with the new built-in AI Client in WordPress 7.0, and still supports earlier versions. * **Choose your AI provider and model** — pick a default provider and model for all AI generation, and override it per request from the editor. Fixes image and text generation sometimes running on a different provider than the one you selected. * Stability and compatibility fixes. = 1.5.7 (24 Jun 2026) = Feature: OAuth 2.1 one-click connect for the MCP server. * **OAuth 2.1 + Dynamic Client Registration** — MCP clients (Claude, ChatGPT, Cursor) can now connect by pasting only your server URL; no manual JWT/token copying. Implements OAuth 2.1 with mandatory PKCE (S256), RFC 7591 dynamic client registration, RFC 8414/9728 discovery metadata, refresh-token rotation, and RFC 7009 revocation. * **Built-in authorization server** — your WordPress site is the identity provider; access tokens map to WordPress users, and the existing per-role/per-ability access control still governs what each connection can do. * **MCP Auth page** — new "One-click OAuth 2.1 connect" panel with an enable toggle, the paste-to-client server URL, and a connected-clients list with one-click revoke. * Disabled by default — enable it from **Atlas AI Connector → MCP Auth**. Application Passwords and JWT continue to work. * Note: remote clients (e.g. Claude.ai) require your site to be served over HTTPS. = 1.5.6 (24 Jun 2026) = Added opt-in usage tracking. * **Usage tracking (opt-in):** Atlas AI Connector can now send anonymized usage data to help prioritize the roadmap. Nothing is sent unless you explicitly click "Allow" on the admin notice. Collected data: site URL/name/language, active/inactive plugin counts, admin name/email, which modules are enabled, and anonymized feature flags/counts (workflows, providers, RBAC). No post content, API keys, or MCP tokens are ever collected. You can opt out at any time. = 1.5.5 (24 Jun 2026) = Listing & discoverability update. * Rewrote the plugin title, tags, and description to better describe the MCP server for WordPress and the AI clients it connects (Claude, ChatGPT, Gemini, Cursor). * Clarified positioning: Atlas AI Connector is both an MCP server and a block-editor AI content toolkit. * No functional code changes. = 1.5.4 (10 May 2026) = update title, tags = 1.5.1 (05 May 2026) = UI improvement: New Overview page added to the admin dashboard. * **Overview page (new):** * Added a new "Overview" tab as the default landing page in the Atlas AI Connector dashboard. * Three subtabs: Welcome, Pricing, and Feature Comparison. * Welcome subtab: plugin stats, getting started info, support links, compatible MCP clients, and AI providers. * Pricing subtab: Annual/Lifetime plan toggle with 3 pricing tiers. Emphasizes the 7-day free trial (no credit card required). * Feature Comparison subtab: Free vs Pro comparison table with 27 features. * 7-day free trial CTA prominently displayed for non-Pro users. * **Dashboard navigation:** * "Overview" is now the default active tab when opening the Atlas AI Connector dashboard. * Tab order updated: Overview → Dashboard → Workflows → Access Control → Analytics → Error Debugger → Documentation → Plugins. = 1.5.0 (13 Apr 2026) = Feature release: Error Debugger module with PHP error monitoring, email alerts, and a fix command for your AI assistant. * **Error Debugger module (new):** * Monitor PHP errors from plugins and themes in real time — no configuration required to start tracking. * Error Log tab shows all errors grouped by file, with severity badges, source info, timestamps, and occurrence counts. * Read the full source context around any error directly in the dashboard. * Mark errors as fixed to keep the log tidy. * **Email notifications:** * Receive an email alert whenever a PHP error occurs. * Configurable recipient email, severity levels (Fatal, Warning, Notice, Deprecated), and rate limit to avoid duplicate emails. * Configure which sources to monitor: Plugins and Themes (free). * **Fix Command in every error email:** * Every notification includes a "How to Fix" block — a pre-filled text snippet you can copy and paste into any AI assistant (ChatGPT, Claude, Gemini, etc.) to get step-by-step fix instructions. * No AI subscription required — works with any AI chat service. * **Admin dashboard widget:** * "Atlas AI Connector — Recent Errors" widget on the WordPress admin dashboard shows the last 5 errors and a 24-hour error count at a glance. * Can be toggled off from the Error Debugger settings without disabling the module. * **Debug log coverage:** * Scans `debug.log` on every admin page load to catch startup fatal errors that occur before the plugin loads (e.g. during plugin activation or update). * **Error Trends and Spike Alerts (Pro):** * Weekly digest email and spike alert notifications available with Atlas AI Connector Pro. = 1.4.2 (10 Apr 2026) = Feature release: Enhanced Plugins page with remote data, social proof, and cross-sell improvements. * **Remote plugin data:** * Plugin information now fetched from a central GitHub repository with 24-hour transient caching. * New "Check for Updates" button to manually refresh plugin data without waiting for cache expiry. * Hardcoded fallback ensures the page works even if the remote fetch fails. * **WP.org API integration:** * Star ratings and active install counts fetched from the WordPress.org Plugin API. * Cached separately with 24-hour transient for performance. * **Enhanced plugin cards:** * Plugin icons from WordPress.org displayed on each card. * NEW badge for recently launched plugins. * PRO badge for plugins with a Pro version available. * RECOMMENDED badge for complementary plugins based on the current plugin. * YOU'RE HERE badge with blue border highlight for the current plugin. * **Pro upsell & engagement:** * "Go Pro" button appears only when the Pro version is not installed. * "Configure" button for active plugins links directly to their settings page. * Top banner: "You're using [Plugin Name]. Complete your AI toolkit." * Google Analytics UTM parameters on all outbound links for conversion tracking. * **Card ordering:** * Priority-based ordering with recommended plugins shown first. * Shuffle within same priority for fair rotation. * **Compatibility:** * Tested up to WordPress 7.0. = 1.4.1 (10 Mar 2026) = Maintenance release: Workflow engine redesign with AI-powered parameter resolution and bug fixes. * **Workflow engine redesign:** * Moved workflow execution from `Content_Steward_Controller` to dedicated `Workflows_Controller` with new `POST /awfah/v1/workflows/run` endpoint. * Generic ability execution via Abilities API — all 80+ abilities from any module now work in workflows (previously limited to 6 Content Steward abilities). * Backward-compatible: old `/content/run-workflow` endpoint delegates to the new controller. * **AI-powered workflow parameter resolution:** * Three-tier input resolution: explicit per-ability params > AI extraction from prompt > fallback defaults. * New "Use AI to extract ability parameters from prompt" checkbox in the post meta box. * AI uses each ability's `input_schema` as a JSON Schema constraint to extract structured parameters from natural language prompts. * Enables abilities that require specific parameters (e.g., `name` for add-category) to work directly from workflow prompts. * **Bug fixes:** * Fixed `post_id` to `id` mapping for abilities that require `id` in their input schema. * Fixed readme.txt short description exceeding WordPress.org 150-character limit. = 1.4.0 (07 Mar 2026) = Feature release: Pro plugin support, AI experiments in the block editor, backward compatibility with pre-6.9 WordPress, and MCP handler fixes. * **Pro plugin support:** * Added Pro plugin detection (`awfah_is_pro_active()`) and integration hooks. * Pro upsell banner on dashboard and dismissible admin notice. * Pro features section in dashboard showing feature status (active/locked). * Pro URL linked throughout the plugin to [Atlas AI Connector Pro](https://atlasaidev.com/atlas-ai-connector-pro/). * **AI Experiments in the block editor:** * Excerpt Generation experiment - generate AI excerpts directly from the post sidebar. * Image Generation experiment - generate AI feature images from the Featured Image panel. * Multi-provider support with model selection dropdown. * Editable prompts with per-post and global prompt saving. * Pro features: templates library, batch mode, explain reasoning, generation history, keyboard shortcuts. * **Backward compatibility:** * WordPress Abilities API and MCP Adapter are now bundled as vendor dependencies. * Plugin works on WordPress 6.8+ (previously required 6.9 where these APIs ship in core). * Minimum WordPress requirement lowered from 6.9 to 6.4. * **MCP handler fixes:** * Fixed Resources handler to properly pass input to ability execute callbacks. * Fixed Prompts handler for correct prompt identifier resolution. * Added `providers/{provider}/models` REST endpoint for model selection. * **Content Steward abilities expanded:** * Added `awfah-content/summarize` ability for AI-powered content summarization. * Added `awfah-content/generate-alt-text` ability for vision-based image alt text generation. * Content Steward module now has 8 abilities (previously 6). * **Dashboard improvements:** * Analytics view placeholder for future usage tracking. * Updated documentation with Pro features section. * Updated ability counts across all UI surfaces. = 1.3.0 (20 Feb 2026) = Feature release: External abilities, role-based workflow assignments, WooCommerce dependency handling, and MCP response fixes. * **External Abilities module (new):** * Automatically discovers abilities registered by WordPress core and third-party plugins via `wp_get_abilities()`. * External abilities appear in the Dashboard, Workflows, Access Control, and MCP server. * Grouped by source namespace (e.g., "External: core", "External: mcp-adapter") in Access Control. * Toggleable on/off from the Dashboard like any other module. * **Role-based workflow assignments:** * Workflows can now be assigned to "All roles" or specific WordPress roles during creation. * New "Workflows" sub-tab in Access Control for per-role workflow assignment. * Dual-layer access: `role_workflows` settings override takes precedence, falls back to workflow's own `assigned_roles` field. * Workflows endpoint supports `?context=admin` for unfiltered admin access. * **WooCommerce dependency handling:** * AI Store Manager module is now visible but disabled when WooCommerce is not active. * Shows "WooCommerce required" badge on Dashboard and Access Control. * Toast error on toggle attempt when WooCommerce is missing. * Backend guard prevents enabling the module without WooCommerce. * **MCP response fix:** * Fixed `structuredContent` validation error for list endpoints (tags, categories, posts, pages, media, users). * Sequential array responses are now wrapped in `{ "results": [...] }` to satisfy MCP protocol requirements. * Applied across all 8 ability files. * **Documentation:** * Added External Abilities section to the Documentation tab. * Updated readme with External Abilities feature description. = 1.2.1 (18 Feb 2026) = Added: Plugins page added. = 1.2.0 (12 Feb 2026) = Major release: 70+ abilities across 9 modules, MCP server, JWT auth, and workflow builder. * **New modules (7):** * Pages Manager - 5 abilities for WordPress page CRUD. * Media Manager - 7 abilities for media upload, update, delete, and file retrieval. * Users Manager - 7 abilities for user CRUD, current user, and role listing. * Custom Post Types Manager - 6 abilities for any registered custom post type. * REST API Tools - 3 abilities to discover and execute any REST API endpoint dynamically. * Site Info & Diagnostics - 4 abilities for site info, plugins, themes, and user info. * Settings Manager - 3 abilities to view and update all WordPress settings. * **AI Store Manager (WooCommerce) - now fully functional:** * 25 abilities covering products, categories, tags, brands, orders, and reports. * Requires WooCommerce to be active (automatic detection). * **Independent module toggles:** * Each of the 11 modules now has its own on/off toggle in the dashboard. * Previously all new modules were bundled under the Content Steward toggle. * **JWT authentication for MCP:** * Generate tokens via `POST /wp-json/jwt-auth/v1/token`. * List active tokens via `GET /wp-json/jwt-auth/v1/tokens`. * Revoke tokens via `POST /wp-json/jwt-auth/v1/revoke`. * HS256 signing with per-site secret key. * Configurable expiration (1 hour to 30 days). * **Workflow builder improvements:** * Drag-and-drop abilities into workflows from the admin dashboard. * Prompt preview now correctly updates when abilities are added or removed. * Post editor meta box prompt preview also updates correctly with each ability change. * **Bug fixes:** * Fixed shallow merge of module settings causing new modules to not appear. * Fixed ability registration timing error on post edit screens. * Fixed workflow prompt always showing first ability's text instead of all selected abilities. = 1.1.0 (13 Jan 2026) = * Added: Documentation tab in the dashboard. = 1.0.0 = * Initial public release. * Added AI Content Steward module (6 abilities). * Added AI Providers dashboard. * Added module toggles with "Coming soon" labels for future modules. --- == Upgrade Notice == = 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.