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, permission-controlled gateway with 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 permissions, 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>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>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. Confirmation tokens required for publish, trash, and restore operations. 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>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>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 content safely. One-click Roll Back on every write.

WisdmLabs

Your AI assistant is smart — but it knows nothing about your specific WordPress site. AI Conduit fixes that. Once installed, your AI can look up your blog posts, check your WooCommerce orders, pull student progress from LearnDash, or summarise your site’s data — just by asking, in plain language.
Think of it as giving your AI a secure window into your WordPress database. It can read and report. It can never edit, delete, or change anything.
<h4>WordPress 7.0 has AI infrastructure — so why AI Conduit?</h4>
WordPress 7.0 shipped the Abilities API, AI Client, Connectors screen, and MCP Adapter. For the first time, WordPress has a standardised way for plugins to talk to AI assistants. The architecture is sound. The vision is right. And for most WordPress sites today, none of it does anything useful yet.
Here’s why. The Abilities API is a registry — it only matters if plugins populate it. WordPress 7.0 ships with two baseline abilities. WooCommerce is leading the way, but the vast majority of the plugin ecosystem hasn’t registered anything yet. Until they do, your AI can see the registry, but there’s nothing in it for your site.
The bigger gap is your custom work. Most production sites have custom post types, meta fields, and bespoke integrations that no plugin author can register on your behalf. The only native path to exposing them is custom PHP — writing schemas and permission callbacks for every field you want your AI to read. That’s a developer project, not an afternoon’s work.
AI Conduit closes both gaps. Point and click to give your AI read access to anything in your database — standard fields, custom post types, custom meta, even data added by plugins that haven’t registered abilities yet. No PHP. No waiting on someone else’s roadmap. Working in minutes, not months.
<h4>What can you use it for?</h4>
<ul>
<li>Customer Support — Ask your AI “what did customer John order last week?” and get the answer without opening WooCommerce. Save hours every week.</li>
<li>E-commerce — “Show me all orders over $5,000 this month.” Your AI assistant pulls the data, you make the decision. No exports, no spreadsheets.</li>
<li>Content Teams — “List all posts published in the last 30 days with fewer than 500 words.” Your AI does the audit in seconds — not hours.</li>
<li>Course Creators — With LearnDash, ask “which students haven’t completed Module 3?” and follow up personally — without running a single report.</li>
<li>Site Owners — “Give me a weekly digest of new signups, published posts, and comments.” Your AI becomes a personal briefing assistant for your site.</li>
<li>Agencies — Build tools once. Use them across client sites. Pull the metrics your clients care about without touching phpMyAdmin or writing SQL.</li>
</ul>
<h4>How it works — three simple steps</h4>
<ol>
<li>Install and activate the plugin. Upload to WordPress the same way you install any other plugin. Takes about two minutes.</li>
<li>Build your first tool with drag-and-drop. Choose what data your AI can see — posts, orders, users, comments. No code required. Point, click, configure.</li>
<li>Connect your AI and start asking questions. Paste one connection URL into Claude Desktop or your preferred AI app. Your assistant now knows your site.</li>
</ol>
<h4>Your data stays safe</h4>
<ul>
<li>Read-only access — Your AI can never edit, delete, or publish anything on your site. Ever.</li>
<li>Role-based controls — Decide exactly which WordPress roles can access which tools.</li>
<li>Full request log — Every query your AI makes is logged so you always know what was asked.</li>
</ul>
<h4>Everything included</h4>
<ul>
<li>Visual tool builder — No code. Drag blocks to define what your AI can access.</li>
<li>Rich data sources — Posts, pages, users, comments, and custom fields — all queryable.</li>
<li>Smart filters — Narrow by date, category, author, custom field value, and more.</li>
<li>Cross-data queries — Combine posts with their authors or comments with their posts in one query.</li>
<li>Import & export tools — Save your tool configuration as JSON and reuse it across sites instantly.</li>
<li>Rate limiting — Set caps on how often the AI can query your site to prevent overload.</li>
</ul>
<h4>Who is this plugin for?</h4>
<ul>
<li>WooCommerce store owners — Query orders, customers, and product data without leaving your AI chat.</li>
<li>LearnDash course creators — Track enrolments, completions, and quiz scores through natural conversation.</li>
<li>Content editors & bloggers — Audit your content library, find gaps, and surface your best posts with ease.</li>
<li>WordPress developers — Build custom MCP tools for clients. Extensible with your own block types.</li>
</ul>
<h4>Works with your favourite AI tools</h4>
AI Conduit connects to any AI app that supports the Model Context Protocol (MCP). That includes:
<ul>
<li>Claude Desktop</li>
<li>Cursor</li>
<li>Any MCP-compatible client</li>
</ul>
New AI tools are adding MCP support every month — any compatible client will work automatically.

AI Conduit

Give your AI assistant a secure, read-only window into your WordPress site. Works with Claude Desktop, Cursor, and any MCP-compatible AI.

Axtolab AI Connector vs AI Conduit