axtolab

Axtolab AI Connector for WordPress connects your WordPress site to AI agents like Claude, ChatGPT, and any MCP-compatible tool. AI agents can safely create drafts, edit content, manage media, work with taxonomies, and integrate with Yoast SEO — all through a secure gateway with per-connection tool access, sensitive-action consent, and Roll Back / Undo on every write.
How it works: The plugin adds a REST API gateway to your WordPress site. A lightweight MCP server runs on your local machine and translates AI tool calls into WordPress REST requests. The plugin enforces per-connection permissions and allow / ask first / block consent for sensitive actions, validates requests, captures every write into a Roll Back / Undo changelog, and logs actions.
<h4>Key Features</h4>
<ul>
<li>Roll Back / Undo on every write — every AI-driven change captures a before/after snapshot. Revert any tool call with one click from the Logs & Roll Back admin page.</li>
<li>Sensitive-action consent — choose whether publishing, trash/delete/restore, WooCommerce price/coupon updates, and AI image actions run automatically, ask first, or are blocked for each connection.</li>
<li>Content Management — Create, edit, and manage posts, pages, and custom post types. Clone existing content as drafts. View and restore revisions. Generate shareable preview links.</li>
<li>Media Library — Upload images from URL, local file, or drag-and-drop portal. Search and browse existing media. Set featured images. Insert, replace, and remove inline images.</li>
<li>WooCommerce Tools — When WooCommerce is active, list products and orders, update product prices, bulk-adjust prices, and create guarded coupons with Roll Back capture.</li>
<li>Stock Photos — Search and import free stock photos from Unsplash and Pexels with automatic attribution.</li>
<li>Yoast SEO — Read SEO and readability scores. Update focus keyphrase, SEO title, and meta description. Preview rendered meta tags.</li>
<li>Authors & Taxonomies — Assign authors from an allowlist. Create and assign categories, tags, and custom taxonomy terms.</li>
<li>Per-connection privilege model — every MCP connection authenticates as a WordPress user via Application Password. The connection’s capability set determines which AI tools can be called; the user’s WP role determines which objects they can act on. Both layers must allow an action for it to succeed. The plugin never creates WordPress users — admins create the Application Password under their own (or a dedicated) WordPress profile and paste it into the connection wizard. Sensitive-action behavior controls can require approval or block actions after the tool permission check passes. Allowlist-driven content type and taxonomy controls. Rate limiting on authentication endpoints.</li>
<li>Two authentication methods — Application Passwords (for Desktop AI clients) and OAuth 2.1 with PKCE (for Web AI clients like ChatGPT and Claude Web).</li>
<li>Upload Portal — Drag-and-drop media uploads with time-limited tokens. No WordPress login required for the upload session.</li>
</ul>
<h4>Available MCP Tools</h4>
The connector exposes a categorized tool surface to MCP-compatible AI clients. All tools are documented and discoverable via the standard MCP <code>tools/list</code> JSON-RPC method.
<ul>
<li>Search & Discovery — <code>wp_find_content</code> (filter + search), <code>wp_list_content_types</code>, <code>wp_get_content</code>, <code>wp_site_info</code>, <code>wp_getting_started</code></li>
<li>Content Authoring — <code>wp_create_draft</code>, <code>wp_update_content</code>, <code>wp_publish_content</code>, <code>wp_clone_content</code>, <code>wp_get_preview_link</code></li>
<li>Trash & Revisions — <code>wp_trash_content</code>, <code>wp_restore_content</code>, <code>wp_list_revisions</code>, <code>wp_restore_revision</code></li>
<li>Media — <code>wp_search_media</code>, <code>wp_get_media</code>, <code>wp_update_media</code>, <code>wp_set_featured_image</code>, <code>wp_upload_media_from_url</code></li>
<li>Inline Images (Gutenberg-aware) — <code>wp_insert_inline_image</code>, <code>wp_replace_inline_image</code>, <code>wp_remove_inline_image</code></li>
<li>Authors & Taxonomy — <code>wp_list_authors</code>, <code>wp_assign_author</code>, <code>wp_list_terms</code>, <code>wp_create_term</code>, <code>wp_assign_terms</code></li>
<li>Yoast SEO — <code>wp_get_yoast_analysis</code>, <code>wp_update_yoast_metadata</code>, <code>wp_get_yoast_head_preview</code></li>
<li>WooCommerce — <code>wp_woo_list_products</code>, <code>wp_woo_get_product</code>, <code>wp_woo_update_product_price</code>, <code>wp_woo_bulk_update_prices</code>, <code>wp_woo_list_orders</code>, <code>wp_woo_get_order</code>, <code>wp_woo_create_coupon</code></li>
<li>Stock Photos — <code>wp_search_stock_photos</code>, <code>wp_import_stock_photo</code> (Unsplash + Pexels with auto-attribution)</li>
<li>Image Providers — <code>wp_generate_image</code>, <code>wp_list_image_providers</code>, <code>wp_confirm_image</code> with site-owner supplied provider API keys</li>
<li>Upload Portal — <code>wp_create_upload_session</code>, <code>wp_get_upload_session</code> (drag-and-drop with time-limited tokens)</li>
<li>Connection Introspection — <code>wp_get_my_capabilities</code> returns the calling connection’s capability groups, named preset (if any), and the resolved tool list — letting AI agents plan work without trial-and-error.</li>
<li>Custom Post Type support — Default allowlist accepts <code>post</code>, <code>page</code>, <code>featured_item</code>. To accept ANY registered public post type (e.g. WooCommerce <code>product</code>, EDD <code>download</code>, custom CPTs), set the allowlist to <code>["*"]</code> in MCP Gateway settings. <code>wp_list_content_types</code> then expands the wildcard to the live list of public types on the site.</li>
<li>Audit Log — every tool call is recorded with timestamp, source, and redacted parameters</li>
<li>Rate Limiting — per-IP token bucket on every authenticated endpoint</li>
</ul>
<h4>What’s Included</h4>
Axtolab AI Connector is fully featured with no limits. No publish limits, no connection caps, no feature gates.
Everything included free:
<ul>
<li>Create, edit, publish, and schedule content with AI agents</li>
<li>Unlimited connections — connect Claude, ChatGPT, and any MCP agent</li>
<li>Upload and manage media (URL, local file, drag-and-drop portal)</li>
<li>Search and import stock photos (Unsplash, Pexels)</li>
<li>Generate images through supported providers when you configure your own provider API key</li>
<li>WooCommerce read/write tools for products, orders, prices, and coupons when WooCommerce is active</li>
<li>Yoast SEO integration</li>
<li>Both authentication methods (App Passwords, OAuth 2.1)</li>
<li>All taxonomy and author management</li>
</ul>
The free core is feature-complete and useful on its own. Separate plugins may extend it, but no built-in feature in this WordPress.org package requires a license key.
<h4>Getting Started</h4>
<ol>
<li>Install and activate the plugin</li>
<li>Go to AI Connector > Connections in wp-admin</li>
<li>Click “+ Add new connection” and follow the wizard — it walks you through creating an Application Password on your WordPress profile (or on a dedicated WP user if you prefer the production-grade setup), pasting it into the connection, and choosing what that connection can do</li>
<li>Click the “Download Extension (.mcpb)” button on the setup page to grab the Claude Desktop bundle from GitHub Releases, then drag it into Claude Desktop’s Extensions panel — or connect a compatible client through MCP-over-HTTP</li>
<li>Start using your AI agent with WordPress</li>
</ol>
<h3>External Services</h3>
This plugin connects to the following external services only when the corresponding feature is configured or used. Provider API keys are supplied by the site owner. The plugin does not send telemetry or analytics to Axtolab.
<h4>Claude (Anthropic) — OAuth Callback</h4>
<ul>
<li>Service: Anthropic’s Claude products at https://claude.ai and https://claude.com</li>
<li>Type: OAuth 2.1 authorization-code callback redirect (no inbound network call from Anthropic during this step)</li>
<li>Endpoints (registered redirect URIs):
<ul>
<li><code>https://claude.ai/api/mcp/auth_callback</code></li>
<li><code>https://claude.com/api/mcp/auth_callback</code></li>
</ul>
</li>
<li>When used: When a logged-in WordPress administrator authorizes a Claude AI client to connect to their WordPress site via the plugin’s OAuth 2.1 flow. The plugin’s <code>/oauth/authorize</code> endpoint redirects the administrator’s browser to one of these URLs after consent.</li>
<li>Data sent in redirect: A one-time, short-lived OAuth authorization code plus the original <code>state</code> parameter. No personal data, no site content, no credentials.</li>
<li>Terms: <a href="https://www.anthropic.com/legal/consumer-terms" rel="nofollow ugc">Anthropic Consumer Terms</a></li>
<li>Privacy: <a href="https://www.anthropic.com/legal/privacy" rel="nofollow ugc">Anthropic Privacy Policy</a></li>
</ul>
<h4>ChatGPT (OpenAI) — OAuth Callback</h4>
<ul>
<li>Service: OpenAI’s ChatGPT custom-connector platform and OpenAI apps platform</li>
<li>Type: OAuth 2.1 authorization-code callback redirect (no inbound network call from OpenAI during this step)</li>
<li>Endpoints (registered redirect URIs):
<ul>
<li><code>https://chatgpt.com/connector_platform_oauth_redirect</code></li>
<li><code>https://platform.openai.com/apps-manage/oauth</code></li>
</ul>
</li>
<li>When used: When a logged-in WordPress administrator authorizes ChatGPT (or an OpenAI Apps Platform client) to connect to their WordPress site via the plugin’s OAuth 2.1 flow. The plugin’s <code>/oauth/authorize</code> endpoint redirects the administrator’s browser to one of these URLs after consent.</li>
<li>Data sent in redirect: A one-time, short-lived OAuth authorization code plus the original <code>state</code> parameter. No personal data, no site content, no credentials.</li>
<li>Terms: <a href="https://openai.com/policies/terms-of-use" rel="nofollow ugc">OpenAI Terms of Use</a></li>
<li>Privacy: <a href="https://openai.com/policies/privacy-policy" rel="nofollow ugc">OpenAI Privacy Policy</a></li>
</ul>
<h4>GitHub Releases (Claude Desktop installer bundle download)</h4>
<ul>
<li>Service: GitHub Releases — the Axtolab AI Connector for WordPress (Free) public repository</li>
<li>Type: Static binary file download (HTTP GET, no inbound request from GitHub to the WordPress site)</li>
<li>Endpoint: API host <code>github.com</code>, path <code>/Axtolab/axtolab-ai-connector-for-wordpress-free/releases/latest/download/axtolab-ai-connector.mcpb</code> (HTTPS).</li>
<li>When used: When a logged-in WordPress administrator clicks the “Download Extension (.mcpb)” button on the AI Connector setup page. The administrator’s browser is redirected to GitHub Releases to fetch the file. The plugin itself does not initiate an outbound request to GitHub; the user’s browser does, when they click the link. Filterable via <code>axtolab_ai_connector_mcpb_download_url</code> if a site owner wants to self-host the bundle.</li>
<li>Data sent: Standard HTTP browser request headers only. No WordPress site data, content, credentials, or telemetry is sent.</li>
<li>Terms: <a href="https://docs.github.com/en/site-policy/github-terms/github-terms-of-service" rel="nofollow ugc">GitHub Terms of Service</a></li>
<li>Privacy: <a href="https://docs.github.com/en/site-policy/privacy-policies/github-general-privacy-statement" rel="nofollow ugc">GitHub Privacy Statement</a></li>
</ul>
<h4>Local MCP clients (Claude Desktop, Cursor, Claude Code, VS Code)</h4>
<ul>
<li>Service: A local AI client running on the site administrator’s own computer.</li>
<li>When used: When the site administrator installs the <code>.mcpb</code> bundle (downloaded from GitHub Releases via the AI Connector setup page) into a local AI client such as Claude Desktop. That client then connects inbound to the site’s REST API using credentials issued during setup. The plugin does not initiate any outbound network call to these clients.</li>
<li>Data sent: Only what the AI client requests through tool calls the administrator has approved. The plugin does not send unsolicited data.</li>
</ul>
<h4>Unsplash (Stock Photo Search)</h4>
<ul>
<li>Service: <a href="https://unsplash.com/" rel="nofollow ugc">Unsplash</a></li>
<li>Endpoint: API host <code>api.unsplash.com</code>, path <code>/search/photos</code> (HTTPS).</li>
<li>When used: When an AI agent searches for stock photos via the stock photo tool</li>
<li>Data sent: Search query, orientation preference</li>
<li>Terms: <a href="https://unsplash.com/terms" rel="nofollow ugc">Unsplash Terms</a></li>
<li>Privacy: <a href="https://unsplash.com/privacy" rel="nofollow ugc">Unsplash Privacy Policy</a></li>
</ul>
<h4>Pexels (Stock Photo Search)</h4>
<ul>
<li>Service: <a href="https://www.pexels.com/" rel="nofollow ugc">Pexels</a></li>
<li>Endpoint: API host <code>api.pexels.com</code>, path <code>/v1/search</code> (HTTPS).</li>
<li>When used: When an AI agent searches for stock photos via the stock photo tool</li>
<li>Data sent: Search query, orientation preference</li>
<li>Terms: <a href="https://www.pexels.com/terms-of-service/" rel="nofollow ugc">Pexels Terms of Service</a></li>
<li>Privacy: <a href="https://www.pexels.com/privacy-policy/" rel="nofollow ugc">Pexels Privacy Policy</a></li>
</ul>
<h4>Google Imagen (AI Image Generation)</h4>
<ul>
<li>Service: <a href="https://cloud.google.com/vertex-ai/generative-ai/docs/image/overview" rel="nofollow ugc">Google Cloud AI</a></li>
<li>Endpoint: API host <code>generativelanguage.googleapis.com</code>, path <code>/v1beta/models/imagen-3.0-generate-002:predict</code> (HTTPS).</li>
<li>When used: When an AI agent generates images using the Google Imagen provider and the site owner has configured a Google API key</li>
<li>Data sent: Text prompt, aspect ratio, safety filter level</li>
<li>Terms: <a href="https://cloud.google.com/terms" rel="nofollow ugc">Google Cloud Terms</a></li>
<li>Privacy: <a href="https://policies.google.com/privacy" rel="nofollow ugc">Google Privacy Policy</a></li>
</ul>
<h4>OpenAI (AI Image Generation)</h4>
<ul>
<li>Service: <a href="https://openai.com/" rel="nofollow ugc">OpenAI</a></li>
<li>Endpoint: API host <code>api.openai.com</code>, path <code>/v1/images/generations</code> (HTTPS).</li>
<li>When used: When an AI agent generates images using the OpenAI provider and the site owner has configured an OpenAI API key</li>
<li>Data sent: Text prompt, image size, quality setting</li>
<li>Terms: <a href="https://openai.com/policies/terms-of-use" rel="nofollow ugc">OpenAI Terms of Use</a></li>
<li>Privacy: <a href="https://openai.com/policies/privacy-policy" rel="nofollow ugc">OpenAI Privacy Policy</a></li>
</ul>
All API keys are stored encrypted using AES-256-CBC with WordPress security salts and are only decrypted at the time of the API call.
<h3>Support</h3>
<ul>
<li>WordPress.org plugin support forum — https://wordpress.org/support/plugin/axtolab-ai-connector/ (please use this for general questions; replies are public so the next merchant searching for the same answer can find it).</li>
<li>Email support — support@axtolab.com (for license, account, or anything sensitive).</li>
<li>Documentation — https://axtolab.com/docs/ai-connector-free</li>
<li>Bug reports — use the WordPress.org support forum for public issues or email support for sensitive reports.</li>
</ul>
The same support entry points are also surfaced inside wp-admin: a “Need help?” footer on every Axtolab settings page, and “Settings · Support” / “Email support · WordPress.org forum · Docs” rows on the Plugins admin row for this plugin.

Axtolab AI Connector

Let AI agents read, draft, edit, and publish WordPress with per-connection permissions, consent gates, and Roll Back.

Deepak Gupta

MCP Manager uses the standard <code>@automattic/mcp-wordpress-remote@latest</code> package with WordPress Application Passwords for the default remote flow. It also includes an optional experimental direct Claude Connectors mode backed by a WordPress-hosted OAuth approval flow.
MCP Manager is a WordPress plugin that enables seamless integration with Model Context Protocol (MCP) servers, allowing AI assistants and code editors to safely access your WordPress instance through secure application passwords.
<h4>Key Features</h4>
<ul>
<li>
Multi-Client Support: Configure MCP for:
<ul>
<li>VS Code with Copilot</li>
<li>Claude Desktop App</li>
<li>GitHub Copilot & Codex</li>
<li>OpenAI ChatGPT Codex</li>
<li>Custom MCP Clients</li>
</ul>
</li>
<li>
Secure Authentication: Uses WordPress native Application Passwords system
<ul>
<li>One-click password generation</li>
<li>Secure credential management</li>
<li>Password revocation support</li>
<li>Per-server Access Control still enforced after authentication</li>
</ul>
</li>
<li>
Easy Configuration:
<ul>
<li>Copy-paste ready JSON configurations</li>
<li>Per-provider configuration file paths</li>
<li>Automatic top-level key detection</li>
</ul>
</li>
<li>
Format #1 Standard: Uses the Automattic-recommended MCP configuration format
<ul>
<li>npx command execution</li>
<li>@automattic/mcp-wordpress-remote@latest package</li>
<li>Full environment variable support</li>
</ul>
</li>
</ul>
<h4>How It Works</h4>
<ol>
<li>Navigate to Settings → MCP Manager</li>
<li>Select your MCP client (VS Code, Claude, GitHub Copilot, ChatGPT, or Custom)</li>
<li>Click “Generate New Application Password”</li>
<li>Copy the ready-to-use JSON configuration</li>
<li>Paste into your client’s configuration file</li>
<li>Restart your MCP client</li>
</ol>
All application passwords are managed through WordPress’s native Application Passwords system and appear in your profile under Account Management.
<h4>CLI Connection and Authorization Flow</h4>
MCP Manager also supports a browser-assisted CLI connection flow for local MCP clients.
Typical command:
<pre><code>npx -y @acrossai/mcp-manager --siteurl=https://example.com --server=default-mcp-server
</code></pre>
Flow summary:
<ol>
<li>The CLI checks <code>/wp-json/acrossai-mcp-manager/v1/health</code></li>
<li>The CLI starts auth with <code>/wp-json/acrossai-mcp-manager/v1/auth/start</code></li>
<li>WordPress returns an <code>auth_code</code> and frontend <code>auth_url</code></li>
<li>The CLI opens the frontend approval page at <code>/acrossai-mcp-manager/</code></li>
<li>If needed, the user signs in through normal WordPress login</li>
<li>The signed-in user approves access in the browser</li>
<li>The CLI polls <code>/auth/status</code> until the request is approved</li>
<li>The CLI fetches the approved user’s accessible servers from <code>/servers</code></li>
<li>The CLI exchanges the approved code at <code>/auth/exchange</code></li>
<li>WordPress creates a one-time Application Password and the CLI writes the MCP client config</li>
</ol>
Terminology:
<ul>
<li>Sign in / Log in = WordPress account authentication</li>
<li>Connect = starting the CLI-to-site linking flow</li>
<li>Authorize / Approve access = granting the CLI permission in the browser</li>
</ul>
Important notes:
<ul>
<li>The frontend authorization page must never be cached</li>
<li>Auth codes are single-use</li>
<li><code>/servers</code> and <code>/auth/exchange</code> respect per-server access control</li>
<li>User-facing copy should say CLI Connections rather than npm Login</li>
<li>Generated remote MCP configs use Application Passwords and explicitly disable OAuth discovery in <code>@automattic/mcp-wordpress-remote</code></li>
</ul>
<h4>Experimental Direct Claude Connectors</h4>
An optional Claude Connectors Screen (Experimental) setting can enable a direct OAuth flow for Claude’s hosted connectors.
When the global feature toggle is enabled and a specific server is configured in its Claude Connector tab, the plugin exposes:
<ul>
<li><code>/.well-known/oauth-authorization-server</code></li>
<li><code>/.well-known/oauth-protected-resource?resource=<mcp-url></code></li>
<li><code>/acrossai-mcp-connectors/oauth/authorize/</code></li>
<li><code>/wp-json/acrossai-mcp-manager/v1/connector/oauth/token</code></li>
</ul>
Important notes:
<ul>
<li>Disabled by default</li>
<li>The Application Password flow remains available and supported</li>
<li>The master experimental toggle is global, but OAuth client settings are stored per server</li>
<li>Direct connector approval signs Claude in as a WordPress user</li>
<li>Per-server Access Control still applies to every MCP request after OAuth</li>
<li>Public HTTPS is recommended for hosted connector usage</li>
</ul>
<h4>Provider Configuration Paths</h4>
<ul>
<li>VS Code: ~/.config/Code/User/globalStorage/Copilot.copilot-chat/mcp.json (top-level key: “servers”)</li>
<li>Claude: ~/Library/Application Support/Claude/claude_desktop_config.json (top-level key: “mcpServers”)</li>
<li>GitHub Copilot: ~/.gh-copilot/config.json (top-level key: “servers”)</li>
<li>OpenAI ChatGPT: ~/.config/chatgpt/config.json (top-level key: “servers”)</li>
<li>Custom: ./your-project/.mcp/config.json (top-level key: configurable)</li>
</ul>
<h4>Requirements</h4>
<ul>
<li>WordPress 5.9 or higher</li>
<li>PHP 7.4 or higher</li>
<li>WordPress Application Passwords support (built-in since WP 5.6)</li>
</ul>
<h3>Support & Contribution</h3>
For issues, feature requests, or contributions, visit the plugin repository.
Questions? Check the FAQ section or look for documentation in the plugin settings page.
<h3>Development</h3>
This plugin follows WordPress coding standards and best practices: 
– PHP 7.4+ compatible 
– Full object-oriented architecture 
– Secure nonce verification 
– Proper capability checks 
– Sanitized input validation 
– Escaped output
<h3>License</h3>
This plugin is licensed under the GPL-2.0-or-later license. See LICENSE file for details.
<h3>Credits</h3>
MCP Manager is built with: 
– WordPress native APIs 
– Automattic’s MCP WordPress Remote package 
– WordPress Application Passwords system
Developed with ❤️ for the WordPress community.

AcrossAI MCP Manager

Connect WordPress to MCP clients like VS Code, Claude, and Copilot using secure application passwords.

Axtolab AI Connector vs AcrossAI MCP Manager