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

AtlasAI Connector is the only WordPress MCP server with no limit on how many AI abilities your site can expose. 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. Your tool list is not a fixed catalogue. On top of the built-in abilities, the free plugin picks up every ability any plugin registers through the WordPress Abilities API, and turns WooCommerce’s own REST API into read-only AI tools. There is no cap on the number in either the free or the Pro version.

Generate excerpts, feature images, summaries, titles, and alt text without leaving the post — on a secure MCP server built around OAuth 2.1 with PKCE, per-role access control, and an audit trail of every AI action, so each connection only does what you allow and nothing happens on your site unseen.

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 your other plugins Most MCP plugins only expose what they wrote themselves. AtlasAI Connector turns the plugins you already run into AI tools, two ways:

Abilities API — free, unlimited. Any plugin that registers abilities through the WordPress Abilities API is picked up automatically. Nothing to configure, no per-plugin integration, and no cap on how many.

REST API to AI tools — WooCommerce free, every plugin in Pro. Most plugins do not register abilities yet, but almost all of them register REST endpoints. AtlasAI Connector reads those endpoint definitions — their parameters, types and descriptions — and turns them into AI tools. The free version does this for WooCommerce. Pro does it for every plugin on your site.

Each endpoint is graded on how well it describes itself, so you can see at a glance which tools an AI will use correctly and which need a better description first.

WooCommerce AI tools The free version connects WooCommerce to your AI assistant in read-only mode: products, store data, orders and customers. An AI can answer “how many orders came in yesterday”, “which products are low on stock”, “what did this customer buy” — and cannot change anything in your store.

Pro adds everything that writes — create and update products, fulfil orders, issue refunds, edit customers — plus the remaining WooCommerce endpoint groups: reports, coupons, settings, shipping, taxes, webhooks and more. Pro also turns every other plugin’s REST API into tools the same way.

You choose which groups are switched on, and nothing is handed to an AI client until you grant it to a role.

Unlimited abilities without slowing your site An unlimited tool list raises a fair question: what does it cost? Measured on a real store with 396 WooCommerce endpoints switched on:

Your front end is untouched. Nothing in this plugin runs for visitors. Page load times are identical with the feature on and off.

Registering hundreds of abilities takes well under a millisecond, and adds about 4 MB to peak memory on the admin screens that use them.

Endpoint discovery only runs where it is needed — the two plugin screens that list abilities — never on your posts list, your dashboard, or any other admin page.

You control the tool count. Most AI clients start choosing the wrong tool somewhere past a hundred, so the plugin shows you the number, warns you when you pass it, and lets you narrow what each role can reach.

The limit that matters is not your server. It is how many tools a model can choose between well — and this plugin is built to help you keep that number sensible.

Secure by design An MCP server hands an AI assistant real write access to your site, so this one is built to be governed rather than trusted blindly:

OAuth 2.1 with PKCE and dynamic client registration — your site is its own authorization server. No client IDs, secrets, or long-lived tokens to paste or leak, and JWT or Application Password auth is available as a fallback for headless and CI use.

Every connection maps to a WordPress user — an AI client inherits that user’s role and capabilities, so it can never exceed what the person behind it is allowed to do.

Role-based access control — choose which modules and abilities each role may use. Pro adds per-ability RBAC, tool/resource/prompt access modes, and OAuth scope enforcement.

Audit trail — with the official WordPress AI plugin’s request logging enabled, every ability and MCP tool call this plugin runs is recorded alongside the AI plugin’s own entries: the operation, the user, the duration, the outcome, and the AI provider and model where one was used.

Revoke access anytime — review connected clients under MCP Auth → Connected clients and revoke any of them in one click.

Your keys, your server — bring your own AI provider keys. Nothing is proxied through us, and no site content or credentials are sent anywhere except the provider you configured.

Works with the official WordPress AI plugin AtlasAI Connector integrates with the official AI plugin 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.

Unlimited abilities — built-in abilities for posts, pages, media, users and WooCommerce, exposed to AI as tools, resources and prompts, plus every ability any other plugin registers through the WordPress Abilities API, discovered automatically and free of charge. No numeric limit in free or 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. With the official WordPress AI plugin’s request logging enabled, every ability and MCP tool call is recorded — what ran, who triggered it, how long it took, and whether it succeeded.

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 — individually toggleable Each module can be enabled or disabled independently of the AtlasAI Connector dashboard:

AI Content Steward (8 abilities) — AI content analysis, generation, and improvement.

Posts Manager (13) — full CRUD for posts, categories, and tags.

Pages Manager (5) — CRUD for WordPress pages.

Media Manager (7) — upload, update, and manage media files.

Users Manager (7) — search, create, and manage users.

Custom Post Types Manager (6) — CRUD for any registered custom post type.

REST API Tools (3) — discover and execute any WordPress REST endpoint dynamically.

Site Info & Diagnostics (4) — site info, plugins, themes, and users at a glance.

Settings Manager (3) — view and update WordPress settings.

AI Store Manager — WooCommerce (26) — products, categories, tags, brands, orders, and sales reports. Requires WooCommerce.

Error Debugger (4) — real-time PHP error monitoring with AI fix commands (details below).

External Abilities (Pro) — automatically discovers every ability registered through the WordPress Abilities API by any plugin, however many there are, 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, 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 AtlasAI 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 every ability any plugin registers via the Abilities API.

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 …