MCP Server for WordPress – Connect Claude, ChatGPT & Gemini | AtlasAI Connector

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.

Most WordPress MCP plugins give you a server only, with a fixed list of tools. AtlasAI Connector 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.

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.

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.

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.

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.

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.

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.

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.

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.

Any provider the WordPress AI Client supports, including OpenAI (GPT models), Google Gemini, and Anthropic Claude. Configure providers under Settings → Connectors.

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.

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.

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, AtlasAI Connector can read their REST API and turn those endpoints into AI tools — free for WooCommerce, and for every plugin on your site with Pro.

Not in the free version. Free connects WooCommerce read-only, so an AI can answer questions about products, orders and customers but cannot alter them. Pro adds the endpoints that write. 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.

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.

Yes. The free plugin includes the full MCP server, unlimited abilities, third-party plugin support through the Abilities API, read-only WooCommerce tools, one-click OAuth 2.1, role-based access control, all five AI experiments in both editors, three workflows, and the Error Debugger. Pro adds reach on top — the free plugin never stops working.

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.

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.

Yes! AtlasAI 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.

Yes. Each module has an independent toggle in the AtlasAI Connector dashboard. Disabled modules do not register their abilities or expose them via MCP.

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].

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.

Click the "Contact Support" button in the AtlasAI Connector dashboard, or visit: https://atlasaidev.com/contact-us/