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

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. How do I connect Claude, ChatGPT or Gemini to WordPress? Activate the plugin and your 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, Claude Desktop, ChatGPT, Cursor, Windsurf, Claude Code, or Gemini CLI as a custom connector, and approve the consent screen in your browser — no manual tokens to copy. Headless and CI clients can fall back to JWT or Application Password auth. Step-by-step guides for each client are below under “Connecting AI Agents”. Does it work with my other plugins? Yes. 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. Does it work with WooCommerce? Yes. 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”, or “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. Do unlimited abilities slow down your site? No. Nothing in this plugin runs for visitors, so page load times are identical whether the feature is on or off. Measured on a real store with 396 WooCommerce endpoints switched on, registering hundreds of abilities takes under a millisecond and adds about 4 MB to peak memory — only on the two admin screens that list abilities, never on your dashboard or posts list. The real limit is not your server but how many tools a model can choose between well: most AI clients start picking the wrong tool past a hundred, so the plugin shows you the count, warns you when you pass it, and lets you narrow what each role can reach. Is an MCP server on WordPress secure? An MCP server hands an AI assistant real write access to your site, so this one is built to be governed, not trusted blindly: OAuth 2.1 with PKCE and dynamic client registration — your site is its own authorization server, with no client IDs, secrets, or long-lived tokens to leak. JWT and Application Password auth work as a fallback for headless and CI use. Every connection maps to a WordPress user — an AI client inherits that user’s role and can never exceed what the person behind it may 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 is recorded: the operation, the user, the duration, the outcome, and the AI provider used. Revoke access anytime — review and revoke connected clients under MCP Auth → Connected clients in one click. Your keys, your server — bring your own AI provider keys; nothing is proxied through us. 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, respect its per-feature toggles, and inherit its editorial Guidelines in every prompt so generated content stays on brand. You can hide the AI plugin’s duplicate experiments — per experiment or globally — 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 choose 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 tools for posts, pages, media, users and WooCommerce, plus every ability any other plugin registers through the WordPress Abilities API, discovered automatically. No numeric limit in free or Pro. Secure by design — OAuth 2.1 with PKCE and dynamic client registration, plus JWT and Application Password support, and per-role access control so each connection only sees what its WordPress user may use. Works on WordPress 6.8+ — bundles the Abilities API and MCP Adapter, so you need not wait for the core versions where these ship. Multi-provider AI — OpenAI, Google Gemini, or Anthropic Claude via the WordPress AI Client; provider keys set once are shared with 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, categories, tags, and brands, review orders, and pull sales reports by chatting with your AI assistant. All 26 store abilities run through the same MCP server, workflows, and role-based access control, and register only when WooCommerce is active. AI Content Generator: Write Blog Posts, Pages and Product Descriptions Six experiment panels run on your configured AI provider (OpenAI, Google Gemini, or Anthropic Claude), in both the Block Editor and the Classic Editor: Content Generation — an AI blog post generator and article writer built into WordPress. Give it a topic, pick an AI-generated title, edit the outline, then generate the full post and preview it before a single block reaches your editor. Works for blog posts, landing pages, any custom post type, and WooCommerce product descriptions. 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 and tone/style presets — free. Pro extends every experiment with a prompt templates library, batch variants, generation history, model tuning, “Explain This Generation”, and keyboard shortcuts. Pro also lets Content Generation read your own site, so drafts link to posts and products that actually exist instead of invented URLs. 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 Every ability is registered through the standard WordPress Abilities API and exposed over MCP via the official MCP Adapter — both bundled as vendor dependencies, so everything works on WordPress 6.8+ today, before these APIs ship in 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 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. 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 every ability 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.

wp-admin forgets. OpenStation doesn’t. You know the moment. You’re deep in a post and you need one image from the Media Library. You click over, find it, click back, and everything you had going is gone. Your scroll position, your half-typed thought, the three other things you had queued up in your head. That’s not a bug you hit. That’s the design. wp-admin shows you one screen at a time, and every navigation throws the last one away. It has worked this way since 2003, like a fridge that empties itself every time you close the door. WordPress has rebuilt almost everything else. The editor, the site editor, the patterns, the styles. The admin’s one-screen-at-a-time model is the layer nobody touched. OpenStation touches it. Install it and admin screens become draggable, resizable windows. Edit a post while the Media Library sits open next to it. Drag an image from one window straight into the other. Keep comments open in the corner. Reload the browser and your window layout — open pages, positions, sizes, and window states — comes back where you left it. OpenStation itself is free, GPL, and opt-in per user. One click in the admin bar turns it on for you. One click turns it off. Nobody else on your site sees anything change, and deactivating the plugin restores the classic admin exactly. No Core patches and no lock-in. Optional AI providers may charge for their service. Built and maintained by Automattic, the company behind WordPress.com, Jetpack, WooCommerce, and Tumblr. Work on more than one thing at once Admin pages open as windows, including pages added by most other plugins. Drag them, resize them, snap them, tile them, minimize them to a taskbar. The admin menu becomes a dock of icons. Two editors open at once is one click away. Never lose your place Moving between open windows leaves each page in place. Across reloads, OpenStation remembers your open pages, window positions, sizes and states, virtual desktops, and focus. Closing a window with unsaved changes warns you first. A desk you can actually put things on Drop posts, media, and links right onto the wallpaper. Sort them into folders. Trash them to a Trash that actually holds things. The stuff you’re working on this week can just sit out where you can see it. One desktop per job Virtual desktops, the way your operating system does them. One for writing. One for the store. One for comment triage. One for that redesign you keep poking at. Switch between them without closing anything. Find anything with Cmd+K The full WordPress command palette, plus slash commands from your plugins, all under one keystroke. Turn on the optional AI assistant and you can ask it things like “which post had the comment asking for the recipe?” and it searches your own content to answer. (Requires an AI provider configured in Settings → Connectors on WordPress 7.0+. Details under “External services” below.) See how your site fits together The Corkboard is an interactive, zoomable map of how your posts, pages, and products link to each other. Pan around it. Find the orphans. Find the hubs. Running a store? Orders, Products, Coupons, and Customers become browsable folders with stock and sale ribbons. Open a customer to see their lifetime spend and what they buy most. Follow a product to its buyers, or a coupon to who redeemed it. Make it yours Wallpapers, from color presets to animated scenes to your own photo. Live widgets pinned to the desktop: drafts, stats, recent comments, a focus timer. Uploadable desktop themes, including a built-in Legacy theme that brings the old WordPress blue back in one click. And Mio, a soft-body desk companion that drifts across your wallpaper and gets bumped around by your windows. Off by default. You’ll turn it on. For developers Extend OpenStation through documented PHP and JavaScript APIs. Register windows, icons, wallpapers, widgets, commands, and settings tabs through stable openstation_register_* PHP APIs and a typed JavaScript API; customize dock items through documented hooks; add AI tools with the WordPress Abilities API. Copy-paste examples live in the developer docs on GitHub. External services No external service is required for OpenStation’s desktop interface. The optional AI Assistant and two user-initiated enrichment features make the external requests described below. AI Assistant The optional AI Assistant sends data to the AI provider you configure in WordPress’s Settings → Connectors (for example OpenAI, Anthropic, or Google). Generation is routed through WordPress 7.0’s built-in AI Client, which supplies the credentials stored in Connectors. The plugin never handles an API key itself. With no provider configured in Connectors, no external AI requests are made. When the AI Assistant is enabled and a user invokes it (via Cmd+K or the slash-command palette): What is sent: the user’s prompt, the conversation history for the active session, and tool-call metadata. The plugin’s built-in tools (search_posts, search_pages, search_comments) run WordPress’s native keyword search and may include excerpts of the matching posts/pages/comments in tool results, which are then sent back to the provider as part of the agentic loop. When it is sent: on user-initiated AI requests, and (if an administrator enables “Score new comments with AI”) on comment-save hooks for spam analysis. Posts, pages, and taxonomy terms are not sent automatically. Why it is sent: to obtain model completions and tool-call decisions that drive the AI Assistant. Who provides the service: whichever provider you configured in Settings → Connectors. Which provider (and endpoint) receives the data depends entirely on that configuration. Review the chosen provider’s own terms and privacy policy (e.g. OpenAI, Anthropic, or Google). URL shortcut favicons When an authorized user creates a desktop shortcut to an external URL, OpenStation asks that URL for its page HTML and favicon so the shortcut can display the site’s icon. The request is made from your WordPress server and sends the requested URL, the server’s IP address, an OpenStation user-agent string, and normal HTTP request metadata to the operator of that site. This happens only when a user creates the shortcut. The destination site’s terms and privacy policy apply. WordPress.org plugin information When an authorized user opens or refreshes parts of OpenStation’s Plugins window, OpenStation may request public plugin details, update metadata, and review excerpts from WordPress.org. These requests send plugin slugs, the site’s locale, and normal HTTP request metadata to WordPress.org. This information is used only to display and manage plugins. Review the WordPress.org Privacy Policy. OpenStation’s OAuth relay does not contact a service by itself. Third-party plugins that configure the relay may contact their own providers and are responsible for disclosing those services. Credits OpenStation is brought to you by Automattic. The plugin is open source under GPLv2-or-later; contributions are welcome on GitHub. Third-party libraries The plugin bundles the following third-party JavaScript library, loaded on demand only when a feature that needs it is in use: PixiJS (MIT License) — used by the Corkboard window, built-in canvas wallpapers (e.g. the animated WordPress logo), the Mio desk companion, and the Inkfall typing game. PixiJS is loaded from the plugin’s own assets/vendor/ directory; no CDN requests are made. Data files The Inkfall game’s word list (assets/games/inkfall/words.txt) is generated from the following sources (attribution also ships in the file’s header): FrequencyWords by Hermit Dave (CC-BY-SA 4.0) — English word-frequency ranking derived from the OpenSubtitles corpus. english-words by dwyl (Unlicense) — used as a validity filter. LDNOOBW English list (CC-BY 4.0) — used as an exclusion filter.