MCP Server for WordPress – Connect Claude, ChatGPT & Gemini | AtlasAI Connector vs VigIA – AI Visibility, Analytics & Control

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.

VigIA (Spanish for “lookout” or “watchman”, incorporating “IA” – Spanish for “AI”) is a complete AI visibility toolkit for WordPress. Monitor 60+ AI crawlers, control access to your content, and optimize how AI systems discover and understand your site. What does VigIA do? Scores your AI visibility with a 100-point analyzer covering 20 checks across 5 categories Tracks AI crawlers visiting your site (GPTBot, ClaudeBot, PerplexityBot, and 60+ others) Provides detailed analytics with advanced filters, server-side pagination, and exportable reports with metadata banner Blocks unwanted crawlers via PHP (403 response) Manages robots.txt rules for AI crawlers with compliance monitoring Sends email alerts about crawler activity (daily, weekly, or monthly) Generates llms.txt files to help AI systems understand your site Serves markdown endpoints for posts, pages, taxonomy archives (categories, tags, WooCommerce product categories, custom taxonomies) and WooCommerce products with schema-like data Generates JSON-LD structured data with Site Identity and AI Discovery signals Exposes abilities for AI agents and automation tools (WordPress 6.9+) Key Features AI Visibility Analyzer * 100-point scoring system with letter grades (A+ to F) * 20 individual checks across 5 categories * Access & AI Discovery (37 pts): robots.txt, AI bot directives, Content Signals, llms.txt, sitemap, RSS feed * Structured Data & Semantic Context (25 pts): JSON-LD schemas, Open Graph, Twitter Cards, meta description, canonical URL * Content Structure & Readability (20 pts): heading hierarchy, semantic HTML5, image alt text, content/HTML ratio * AI Interaction & Distribution (8 pts): markdown delivery, AI share buttons * Access Performance (10 pts): TTFB measurement * Smart recommendations with direct links to VigIA features and plugin suggestions * Analyze any page on your site with URL autocomplete selector * Results cached for 24 hours with manual re-analyze option Analytics Dashboard * Total visits, unique crawlers, and pages crawled statistics * Timeline chart with daily breakdown * Category distribution (AI Training, AI Search, AI Assistant, Data Scraper) * Top crawlers and most crawled pages tables with paginated navigation * Share Buttons & AI-powered Summaries integration: see share button clicks per page * Recent activity log with content type and HTTP status columns (color coded by status family) * Advanced filters: multi-select crawler picker, content type, HTTP status code, and configurable date range * Server-side pagination with four-button pager (first, previous, next, last) — operates over the full database, not just the latest 500 rows * Period comparison functionality * CSV export with a metadata banner (site name, site URL, export type, date range, export timestamp, applied filters) * “Export filtered CSV” button that downloads exactly what the active filters return, with vigia-filtered-YYYY-MM-DD.csv filename * Content type detection distinguishes Home, Post, Page, Product, custom CPTs, Category archive, Tag archive, Date/Author archive, Feed, Sitemap, REST API, File, Admin / login attempts (/wp-admin, /wp-login.php), WordPress system (admin-ajax, xmlrpc, wp-cron, wp-comments-post), 404 Not found, and Other Crawler Blocking * Block crawlers via PHP with 403 Forbidden response * Quick block dropdown in analytics dashboard * Manage blocks from Extras page * Works on any server (Apache, Nginx, LiteSpeed, etc.) Robots.txt Management * Add Disallow rules for AI crawlers * Visual preview of your robots.txt * Compliance monitoring: see which crawlers ignore your rules * One-click blocking for non-compliant crawlers * Works with both physical and virtual robots.txt Email Alerts * Daily, weekly, or monthly reports * Three detail levels: Minimal, Normal, Complete * Non-compliant crawler warnings * Activity comparison with previous period Markdown for Agents * Serve posts, pages and any public post type as optimized markdown for AI agents * Serve taxonomy archive pages (categories, tags, WooCommerce product categories, custom taxonomies) as markdown — disabled by default, opt in per taxonomy * Dedicated .md URL endpoints (e.g., /your-post.md, /category/news.md, /product-category/electronics.md) * Accept: text/markdown content negotiation on posts and taxonomy archive pages * Discoverability via Link HTTP headers and HTML tags * YAML frontmatter for posts: title, date, modified, author, image, categories, tags, post type, lang * YAML frontmatter for taxonomy terms: title, description, url, type, taxonomy, parent, count, image (term meta), lang * WooCommerce product frontmatter adds schema-like fields: sku, product_type, price, regular_price, sale_price, currency, availability, stock_quantity, rating, rating_count, review_count * Taxonomy term body includes the term description (rendered through the_content), the list of direct child terms in hierarchical taxonomies, and an excerpt of the latest posts/products assigned to the term * Product listings inside product_cat archives include an inline summary with formatted price, “was X” on sale items, star rating and out-of-stock flag * Respects blocking rules (blocked crawlers get 403) and LLMs.txt exclusion filters * Per-term noindex detection from Yoast SEO, Rank Math, All in One SEO and SEOPress * Analytics integration: tracks markdown requests per crawler * X-Markdown-Tokens response header * Filters: vigia_markdown_post_eligible, vigia_markdown_term_eligible, vigia_markdown_term_posts_limit * Follows the Cloudflare Markdown for Agents standard LLMs.txt Generator * Select content by post type with one click * Filter by taxonomies (categories, tags, custom) * Manual include/exclude with AJAX search * Exclude by URL patterns (wildcards supported) * SEO plugin integration (auto-exclude noindex content) * Auto-regeneration (daily, weekly, monthly) * Robots.txt integration (add llms.txt and llms-full.txt references) * Generate llms.txt and llms-full.txt files * Full content or excerpt mode * Compatible with Yoast SEO, Rank Math, All in One SEO, SEOPress, The SEO Framework, and Native SEO NoIndexer JSON-LD Structured Data * Generate WebSite and Organization/Person schema for site identity * AI Discovery: ReadAction pointers to llms.txt, llms-full.txt, and Markdown for Agents endpoints * Social profiles and sameAs links for brand identity across the web * SearchAction for Google sitelinks search box * Media library integration for logo selection * SEO plugin conflict detection (Yoast, Rank Math, AIOSEO, SEOPress, The SEO Framework) * Choose output page (front page or any published page) * Live JSON-LD preview with real-time updates * Smart integration with LLMs.txt and Markdown for Agents features Supported AI Crawlers VigIA monitors 60+ AI crawlers including: OpenAI: GPTBot, OAI-SearchBot, OAI-AdsBot, ChatGPT-User Anthropic: ClaudeBot, Claude-SearchBot, Claude-User, Claude-Code Google: Google-Extended, GoogleOther, Gemini-Deep-Research, Google-NotebookLM Perplexity: PerplexityBot, Perplexity-User Meta: Meta-ExternalAgent, FacebookBot, Meta-WebIndexer Amazon: Amazonbot, Amzn-SearchBot, bedrockbot Mistral: MistralAI-User, MistralAI-Index Microsoft: BingBot ByteDance: Bytespider Apple: Applebot-Extended And many more… Privacy Focused VigIA stores visitor data locally in your WordPress database. No data is sent to external servers. Abilities API VigIA is one of the first WordPress plugins to implement the Abilities API introduced in WordPress 6.9. This API allows AI agents, automation tools, and external systems to discover and interact with VigIA’s functionality in a standardized, secure way. What are Abilities? Abilities are self-contained units of functionality that VigIA exposes through WordPress’s central registry. Each ability has defined inputs, outputs, and permissions, making it easy for automation tools to understand and use them. Available Abilities VigIA registers the following abilities: Analytics vigia/get-crawler-stats – Get statistics about AI crawler visits (total visits, unique crawlers, pages crawled) vigia/get-top-crawlers – Get a ranked list of most active AI crawlers vigia/get-top-pages – Get the most crawled pages on your site Blocking vigia/get-blocked-items – List all blocked crawlers and IP addresses vigia/block-crawler – Block a crawler by User-Agent pattern vigia/unblock-crawler – Remove an existing block Robots.txt vigia/get-robots-rules – Get current AI crawler rules in robots.txt vigia/add-robots-disallow – Add a Disallow directive for a crawler vigia/remove-robots-rule – Remove a robots.txt rule Use Cases Automated monitoring: AI agents can query crawler statistics and alert you to anomalies Reactive blocking: Automation tools can block crawlers that repeatedly ignore robots.txt External dashboards: Aggregate data from multiple WordPress sites with VigIA installed WP-CLI integration: Future command-line access through the Abilities API n8n / Make workflows: Build custom automation flows using VigIA’s abilities Requirements The Abilities API ships with WordPress 6.9 and later. On older WordPress versions, VigIA works normally but abilities and MCP are not available. MCP Server (Model Context Protocol) VigIA exposes its 9 abilities as native MCP tools to any MCP-compatible client (Claude Code, Cursor, Claude Desktop, Codex CLI, Antigravity, Continue, Cline, Zed and similar) using the official WordPress MCP Adapter. The adapter ships bundled with the plugin, so the MCP endpoint is active right after installation — no Composer step or terminal access required. Requirements WordPress 6.9 or later (provides the Abilities API) Quick connect (recommended) Open VigIA > Extras > MCP and click “Generate password and connection commands”. The plugin creates a dedicated Application Password named VigIA MCP and renders ready-to-paste commands for Claude Code, Cursor, Claude Desktop and a generic block (URL + Authorization header) for any other MCP client. The plain password is shown only once. If you lose it, revoke the entry from the same panel and generate a new one. Endpoint https://your-site.example/wp-json/vigia/v1/mcp The endpoint uses HTTP Basic auth with the WordPress Application Password. The user must have the manage_options capability. Connecting Claude Code Quick Connect builds the full command for you. The shape is: claude mcp add --transport http vigia https://your-site.example/wp-json/vigia/v1/mcp --header "Authorization: Basic BASE64_OF_USER_AND_APP_PASSWORD" Claude Code merges the new entry into its config file automatically — no risk of breaking other servers. Connecting Cursor Save the JSON block from Quick Connect as ~/.cursor/mcp.json. You can also reach this file from inside Cursor at Settings → Cursor Settings → MCP. If the file already exists with other content, see the FAQ. Claude Desktop and other clients Claude Desktop does not speak HTTP MCP, so it needs a small bridge and a config file of its own. Any other client (Codex CLI, Continue, Cline, Antigravity, Zed, or your own) takes the two raw values Quick Connect exposes: the server URL and the Authorization header. Both cases are covered in the FAQ, together with how to merge VigIA into a config file that already exists without losing what is in it. Read-only mode If you only want your AI to consult VigIA (not change anything), enable “Read-only mode” in the MCP tab. While on, write actions (block, unblock, robots changes) return a permission denied error. Read actions (statistics, top crawlers, blocked items, robots rules) keep working. The toggle stores a vigia_mcp_read_only option that hooks into the vigia_can_write_via_abilities filter. Developers can still force read-only from a mu-plugin: add_filter( 'vigia_can_write_via_abilities', '__return_false' ); The mu-plugin filter at the default priority takes precedence over the toggle. Who can reach the endpoint The endpoint requires the capability to manage options, the same one every tool behind it already asked for. The vigia_mcp_transport_capability filter can lower that bar; each tool keeps its own permission check. After connecting Restart your MCP client after adding the server so it picks up the new tools. Then try a few prompts to confirm everything is wired up: “Show me VigIA crawler stats for the last 7 days.” “List the top 5 most crawled pages on this site.” “Add a robots.txt Disallow rule for TestBot and then list the current AI crawler rules.” The third example exercises a read + write + read round-trip, which is the most complete sanity check. Support Need private support or custom development? Do you need one-on-one help, priority troubleshooting, or a custom feature, integration, or tweak built specifically for your site? I offer private support and custom development. Just contact me and tell me what you need. Need help or have suggestions? Official website WordPress support forum YouTube channel Documentation and tutorials Love the plugin? Please leave us a 5-star review and help spread the word! About AyudaWP We are specialists in WordPress security, SEO, AI and performance optimization plugins. We create tools that solve real problems for WordPress site owners while maintaining the highest coding standards and accessibility requirements.