

AtlasAI Connector dashboard with module toggles and provider status.
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.
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.
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.
AtlasAI Connector integrates with the official AI plugin instead of running a parallel system:
All five AI experiments also work in the Classic Editor — unlike the official AI plugin, which is Block Editor only:
If your site still runs the Classic Editor — as millions do — you get the same AI tools without switching editors.
Each module can be enabled or disabled independently of the AtlasAI Connector dashboard:
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.
Five experiment panels run on your configured AI provider (OpenAI, Google Gemini, or Anthropic Claude), in both the Block Editor and the Classic Editor:
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.
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).
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.
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, AI Provider for Google, or AI Provider for Anthropic plugins, and AtlasAI Connector reuses it for its MCP server and AI experiments — no duplicate setup.
AtlasAI Connector Pro adds:
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:
.cursor/mcp.json as a "url" entry), then approve the OAuth prompt in your browser.serverUrl in mcp_config.json, refresh, and approve the browser consent.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”.
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).
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.