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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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.

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

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 .

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.

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.

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.

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.

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.

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.

Yes. AtlasMCP Pro 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.

Workflows (“when this happens, do that”) are part of AtlasMCP Pro . 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.

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.

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

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.

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 ow