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.

Mehul Gohil

Aculect AI Companion is a secure MCP connector for WordPress. It lets approved AI assistants such as ChatGPT, Claude, Codex, and OpenAI-compatible tools work with your WordPress content, media, comments, and site information through permission-aware workflows.
Instead of switching between WordPress admin screens, you can ask your AI assistant in plain English to draft a post, update a page, review comments, upload media, inspect safe site details, or prepare long-form content using WordPress blocks.
WordPress remains the source of truth. Aculect AI Companion checks the connected WordPress user’s permissions before every action, lets administrators choose which abilities are available, and keeps risky write actions behind configurable controls.
<h4>What is MCP for WordPress?</h4>
MCP stands for Model Context Protocol. In Aculect AI Companion, MCP gives supported AI assistants a structured, permission-controlled way to request WordPress actions. The assistant does not receive direct database access. It can only use the enabled tools exposed by WordPress and approved by an administrator.
<h4>Why use Aculect AI Companion?</h4>
<ul>
<li>Connect WordPress to ChatGPT, Claude, Codex, and OpenAI-compatible MCP clients</li>
<li>Create, update, and organize WordPress content through controlled AI workflows</li>
<li>Work with posts, pages, custom post types, categories, tags, comments, and media</li>
<li>Use block-aware content workflows instead of raw custom HTML</li>
<li>Review AI activity with sanitized audit logs</li>
<li>Control access globally, by connection, by role, and by WordPress user permissions</li>
<li>Use diagnostics to verify OAuth, MCP, endpoint, and environment readiness</li>
</ul>
Setup is designed to be simple:
<ol>
<li>Copy your connection URL from AI Companion > Connect.</li>
<li>Open your AI tool and add a new connector.</li>
<li>Paste the URL when prompted.</li>
<li>Approve the connection on the screen that appears.</li>
</ol>
After approval, Aculect AI Companion checks the connected WordPress user’s permissions before every action. You can also choose exactly what your AI assistant can do and disconnect assistants at any time.
<h4>Features</h4>
<ul>
<li>Create, edit, and publish posts, pages, and supported custom post types</li>
<li>Plan and draft long-form block content for WordPress</li>
<li>Manage categories, tags, custom taxonomies, and content groups</li>
<li>Moderate, reply to, and bulk-manage comments</li>
<li>Upload, list, update, attach, detach, and safely rename media</li>
<li>View safe site settings, active plugins, active themes, and diagnostics</li>
<li>Connect, pause, review, and disconnect AI assistants</li>
<li>Control which MCP abilities each assistant can use</li>
</ul>
<h4>Supported AI Tools</h4>
Aculect AI Companion includes setup guidance for popular AI assistants and MCP clients:
<ul>
<li>ChatGPT app with Developer Mode connectors</li>
<li>OpenAI API integrations that support remote connectors</li>
<li>Claude app, Claude Desktop, Claude Cowork, and Claude mobile</li>
<li>Claude Code</li>
<li>Claude API integrations that support remote connectors</li>
</ul>
Your AI tool must be able to reach your WordPress site over HTTPS to complete OAuth approval and send MCP requests.
<h4>Supported Abilities</h4>
Admins can enable or disable these abilities from AI Companion > Abilities after the first assistant connection is active.
Long-form content workflows:
<ul>
<li>Prepare a post outline, section plan, taxonomy recommendations, media recommendations, and SEO recommendations</li>
<li>Create a draft from validated serialized WordPress block content</li>
<li>Update an existing post with block-safe content workflows</li>
<li>Update Rank Math SEO title, description, and focus keywords when Rank Math is active</li>
</ul>
Content:
<ul>
<li>List readable content types, including custom post types</li>
<li>List posts, pages, and custom content items with pagination</li>
<li>Read one content item by ID</li>
<li>Create a post, page, or custom content item with optional featured image, author, and taxonomy assignments</li>
<li>Update title, content, excerpt, slug, status, featured image, author, or taxonomy assignments for an existing item</li>
<li>Update SEO title, SEO description, and focus keywords for supported SEO plugins</li>
</ul>
Content groups:
<ul>
<li>List available categories, tags, and custom content groups</li>
<li>List terms for a supported taxonomy with pagination</li>
<li>Create a category, tag, or custom content group</li>
<li>Update a category, tag, or custom content group</li>
<li>Assign or clear an image for supported taxonomy terms</li>
</ul>
Comments:
<ul>
<li>List comments for review with pagination</li>
<li>Read one comment by ID</li>
<li>Reply to a comment as the connected WordPress user</li>
<li>Moderate comment content or status</li>
<li>Bulk moderate multiple comments</li>
</ul>
Media:
<ul>
<li>List media library attachments with pagination</li>
<li>Read, update, trash, and safely rename media items</li>
<li>Upload media from a public URL with server-side request checks</li>
<li>Attach media to posts or detach media from posts</li>
</ul>
Site information:
<ul>
<li>View safe, non-secret site settings</li>
<li>View WordPress version, PHP version, active theme, and basic site metadata</li>
<li>List installed plugins and active state for users who can manage plugins</li>
<li>List installed themes and active state for users who can manage themes</li>
</ul>
WordPress abilities:
<ul>
<li>Discover supported public WordPress abilities registered by WordPress and plugins</li>
<li>Inspect one supported public WordPress ability</li>
<li>Run a supported public WordPress ability using the connected user’s permissions</li>
</ul>
<h3>Third Party Services</h3>
Aculect AI Companion does not send site data to an external service on activation, page load, cron, or without a site administrator connecting an AI assistant.
When a site administrator copies the connection URL into an external AI assistant and approves the connection screen in WordPress, that assistant can request the enabled abilities. Depending on the enabled abilities and the connected WordPress user’s permissions, requested data may include post titles, post content, excerpts, slugs, statuses, authors, dates, permalinks, category and tag names, media metadata, comments, and safe site settings such as site name, description, URLs, locale, timezone, date format, time format, permalink structure, and active theme name.
The external service that receives this data is the AI assistant selected and configured by the administrator. Aculect AI Companion’s built-in setup UI includes links for:
<ul>
<li>ChatGPT by OpenAI: https://chatgpt.com/, terms at https://openai.com/policies/terms-of-use/, and privacy policy at https://openai.com/policies/row-privacy-policy/</li>
<li>Claude by Anthropic: https://claude.ai/, terms at https://www.anthropic.com/legal/consumer-terms, and privacy policy at https://www.anthropic.com/legal/privacy</li>
</ul>
Administrators should review the terms and privacy policy for the AI assistant they connect. Aculect AI Companion controls the WordPress-side approval and permissions checks; it does not control how a connected external assistant processes data after the administrator authorizes access.
<h3>Development</h3>
The production package ships built assets and Composer dependencies. Development manifests such as <code>composer.json</code>, <code>composer.lock</code>, and <code>package.json</code> are intentionally excluded from release ZIP files. Generated files under <code>build/</code> are not committed to the source repository; release automation generates them before packaging.
For source code, build tooling, and exact dependency manifests, use the public GitHub repository:
https://github.com/mehul0810/aculect-ai-companion
Contributing guidelines:
https://github.com/mehul0810/aculect-ai-companion/blob/main/CONTRIBUTING.md
Security policy:
https://github.com/mehul0810/aculect-ai-companion/security/policy
From the repository checkout, use the Node.js version in <code>.nvmrc</code> and rebuild assets with:
<pre><code>npm ci
npm run build
</code></pre>
Composer dependencies for production releases are installed with:
<pre><code>composer install --no-dev --prefer-dist --optimize-autoloader
</code></pre>

Aculect AI Companion

Use ChatGPT, Claude, Codex, and other MCP AI assistants to manage WordPress content, media, comments, and site workflows.

Axtolab AI Connector vs Aculect AI Companion