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.

videowhisper

VideoWhisper Site Manager lets you manage WordPress posts and pages through external AI assistants such as ChatGPT (Custom GPT + Actions), Claude (MCP: web, desktop, mobile, CLI), and Codex (MCP). It exposes authenticated WordPress endpoints and setup guidance while you keep using your own AI account and subscription.
It provides:
<ul>
<li>A secure REST layer for content operations (list, read, create, update, revert, reset)</li>
<li>An MCP (Model Context Protocol) endpoint for Claude.ai, Claude Desktop, Claude CLI, Claude mobile apps, and Codex MCP clients</li>
<li>A generated OpenAPI schema URL for GPT Actions import</li>
<li>Guided onboarding with copy/paste values for ChatGPT Builder, Claude connector setup, and Codex MCP setup</li>
<li>Turnkey OAuth onboarding for shared GPT / shared MCP workflows through a compatible Relay & OAuth Server</li>
<li>WordPress Application Password onboarding for direct site-owned integrations</li>
<li>Frontend user connection shortcode support for connected account workflows</li>
<li>Safety controls: HTTPS enforcement, draft-first behavior, publish gating, read/write rate limiting, write quotas, IP allowlists, audit logs</li>
<li>Extension points through WordPress hooks for custom authentication, tools, settings, content types, and admin UI additions</li>
</ul>
The plugin does not call OpenAI, Anthropic, or any AI provider directly. Your WordPress site exposes authenticated endpoints and setup guidance. You connect it to ChatGPT, Claude, or Codex yourself with your own account and subscription.
<h4>Ideal for</h4>
<ul>
<li>Site owners who want to draft, edit, or review WordPress content by chat</li>
<li>Teams using a dedicated WordPress user (recommended: Editor) for AI-assisted publishing workflows</li>
<li>Mobile workflows: configure on desktop, use the GPT or Claude connector on phone/tablet</li>
<li>Developer workflows where Codex can use MCP tools to inspect and update WordPress content</li>
</ul>
<h4>Supported Authentication</h4>
The onboarding flow recommends using one authentication option for clarity, but development and migration setups can enable more than one.
<ul>
<li>Turnkey OAuth – recommended for most sites. Users connect through a compatible Relay & OAuth Server and can operate one or more connected sites from the same shared GPT or MCP connector.</li>
<li>Application Passwords – direct WordPress authentication over HTTPS using WordPress core Application Passwords. Best for admin-owned custom GPT/MCP setups where credentials are managed by the site operator.</li>
<li>Extension-provided authentication – developers can add custom OAuth, token validation, alternate connector metadata, or other authentication flows with the hooks listed below.</li>
</ul>
<h4>Connecting ChatGPT</h4>
<ol>
<li>Install and activate VideoWhisper Site Manager.</li>
<li>Open VideoWhisper Site Manager > Onboarding.</li>
<li>Create (or link) a dedicated WordPress user (recommended role: Editor).</li>
<li>Choose Turnkey OAuth for a shared GPT workflow, or create an Application Password from the onboarding page for a direct site-owned GPT.</li>
<li>In ChatGPT Builder (desktop), create a Custom GPT and import the plugin OpenAPI schema URL.</li>
<li>Use the provided copy/paste values for Configure, Actions, authentication, and privacy policy fields.</li>
<li>Test on desktop, then use the same GPT on mobile.</li>
</ol>
<h4>Connecting Claude (MCP)</h4>
The free plugin includes an MCP endpoint at <code>/wp-json/videowhisper-site-manager/v1/mcp</code>.
Claude.ai (web):
<ol>
<li>Go to <code>claude.ai/customize/connectors</code>.</li>
<li>Click the + button in the Connectors sidebar → Add custom connector.</li>
<li>Set a name and paste the MCP endpoint URL.</li>
<li>Authorize via Turnkey OAuth when connected to a compatible Relay & OAuth Server, or use an Application Password for direct setup.</li>
<li>The connector also works in the Claude mobile apps (iOS and Android) and desktop once authorized.</li>
</ol>
Claude CLI:
claude mcp add –transport http “YourSiteName” “https://yoursite.com/wp-json/videowhisper-site-manager/v1/mcp”
Automatic OAuth authorization requires a compatible Relay & OAuth Server. Without that connection, use WordPress Application Passwords over HTTPS.
<h4>Connecting Codex (MCP)</h4>
The onboarding flow includes Codex setup values for both direct and Turnkey MCP architectures. Codex can connect to the same Streamable HTTP MCP endpoint at <code>/wp-json/videowhisper-site-manager/v1/mcp</code>.
<ol>
<li>Open VideoWhisper Site Manager > Onboarding and enable Codex in the AI Tools selection step.</li>
<li>Choose Turnkey OAuth for shared relay access, or Application Passwords for direct site-owned MCP access.</li>
<li>Copy the generated Codex <code>config.toml</code> block or OAuth login command from the Codex onboarding tab.</li>
<li>Restart or reload Codex MCP settings, then use <code>/mcp</code> in Codex to confirm the WordPress MCP server is active.</li>
</ol>
<h3>Features</h3>
<ul>
<li>MCP endpoint for Claude.ai, Claude Desktop, Claude CLI, Claude mobile apps, and Codex — implements MCP Streamable HTTP transport (protocol 2025-03-26)</li>
<li>ChatGPT / GPT Actions integration via generated OpenAPI schema URL (<code>/wp-json/videowhisper-site-manager/v1/openapi</code>)</li>
<li>Dynamic agent guide at <code>/wp-json/videowhisper-site-manager/v1/agent-guide</code> with Markdown by default and JSON via <code>?format=json</code>; MCP also exposes guide resources for MCP-aware clients</li>
<li>Shared AI action registry keeps MCP tools and OpenAPI schemas aligned for ChatGPT, Claude, and Codex integrations; extra OpenAPI actions are grouped by module with an <code>action</code> subaction field to stay under GPT operation limits</li>
<li>GPT Actions onboarding aligned with current auth UI, including Application Password and Turnkey OAuth setup paths</li>
<li>One-click Application Password creation for the dedicated operator user (plaintext shown once, not stored long-term)</li>
<li>Guided onboarding with copyable values for:
<ul>
<li>GPT Name, Description, Instructions, Conversation Starters</li>
<li>MCP endpoint URL, Claude connector setup instructions (Claude.ai, Desktop, CLI), and Codex MCP configuration snippets</li>
<li>Action authentication values, Schema URL, Privacy Policy URL</li>
<li><code>curl</code> examples and credential samples</li>
</ul>
</li>
<li>Authentication options:
<ul>
<li><code>Turnkey OAuth</code> for shared GPT / shared MCP workflows through a compatible Relay & OAuth Server</li>
<li><code>Application Passwords</code> for direct site-owned admin integrations</li>
<li>hook-based extension points for additional authentication methods</li>
</ul>
</li>
<li>REST endpoints for listing, reading, creating, and updating WordPress posts/pages</li>
<li>Context endpoint for site and content context used by MCP tools</li>
<li>Optional read-only Live Support Tickets CRM integration for authenticated users to list their own conversations and retrieve messages through OpenAPI/MCP tools</li>
<li>Content revert/reset helpers backed by revision snapshots</li>
<li><code>dry_run</code> support for safer create/update previews before writing</li>
<li>Draft-first workflow and optional publish permission (<code>Allow publish</code>)</li>
<li>HTTPS enforcement for plugin endpoints by default (with dev-only HTTP override setting)</li>
<li>Per-user rate limiting with separate defaults for read traffic (10/minute), write actions (5/minute), and hourly write quotas (30/hour)</li>
<li>FansPaysite support for frontend shortcode styling, dark/light mode, and Pro menu icon fields when the FansPaysite theme is active</li>
<li>IP allowlists for Application Password and Turnkey OAuth traffic</li>
<li>External OAuth URL hardening (HTTPS-only with external-host validation)</li>
<li>Configurable short cache TTL for external bearer-token validation (default: 10s)</li>
<li>Categories and tags support</li>
<li>Generic SEO metadata fields (plugin-owned keys)</li>
<li>Audit logging endpoint for administrators</li>
<li>Settings endpoint for administrators</li>
<li>Public protected resource metadata for OAuth-aware clients</li>
<li>Provider Terms of Use and Privacy Policy links when supplied by connected services</li>
<li>User connection shortcode (<code>[vwsm_user_connect]</code>) for account-based connection flows</li>
<li>Admin notices and onboarding reminders for incomplete setup</li>
<li>Recommended GPT/Claude/Codex capabilities guidance</li>
</ul>
<h3>Current AI Actions and Tools</h3>
The shared registry exposes the same capabilities to ChatGPT Actions, Claude MCP, and Codex MCP when settings and user permissions allow them. OpenAPI may group extra actions by module; MCP lists the individual tool names.
Core tools: <code>get_site_context</code>, <code>list_content</code>, <code>get_content</code>, <code>get_logs</code>, <code>create_content</code>, <code>update_content</code>.
Conditional core tools: <code>revert_action</code>, <code>reset_action</code> when log state tools are enabled.
Plugin integration tools: <code>get_site_context</code> includes brief permission-aware <code>available_integrations</code> metadata, while <code>plugins_list</code> lists compatible plugins, agent instructions, whitelisted option documentation, and plugin-specific tools visible to the authenticated user. Site Manager Pro adds <code>plugin_list_options</code>, <code>plugin_get_options</code>, and <code>plugin_update_option</code> for admin-only whitelisted option configuration. Other plugins can register tools with <code>vwsm_ai_plugin_integrations</code>; Site Manager exposes them automatically through MCP, the dynamic agent guide, and grouped OpenAPI <code>/actions/{module}</code> paths.
Live Support Tickets read-only tools when CRM access is enabled: <code>crm_list_my_conversations</code>, <code>crm_get_my_conversation_messages</code>.
Agent documentation: <code>/wp-json/videowhisper-site-manager/v1/agent-guide</code>, <code>/wp-json/videowhisper-site-manager/v1/agent-guide?surface=mcp</code>, <code>/wp-json/videowhisper-site-manager/v1/agent-guide?surface=actions</code>, and <code>/wp-json/videowhisper-site-manager/v1/agent-guide?format=json</code>.
<h3>Extension Hooks</h3>
Developers can extend this plugin without editing core files. Common hooks include:
<ol>
<li>Settings and admin UI: <code>vwsm_settings_defaults</code>, <code>vwsm_settings_normalized</code>, <code>vwsm_admin_settings_save</code>, <code>vwsm_rest_settings_payload</code>, <code>vwsm_settings_tab_label</code>, <code>vwsm_settings_form_publishing_rows</code>, <code>vwsm_settings_form_security_rows</code>, <code>vwsm_settings_form_rate_limits_rows</code>, <code>vwsm_settings_form_logs_revisions_rows</code>, <code>vwsm_settings_form_turnkey_oauth_rows</code>, <code>vwsm_settings_form_authentication_rows</code>, <code>vwsm_settings_form_application_passwords_rows</code>, <code>vwsm_settings_form_content_rows</code>, <code>vwsm_settings_form_admin_rows</code>, <code>vwsm_settings_form_attachments_rows</code>, <code>vwsm_settings_form_fomantic_rows</code>, <code>vwsm_settings_form_after_core_rows</code>, <code>vwsm_auth_methods_section</code>.</li>
<li>Authentication and OAuth metadata: <code>vwsm_oauth_server_url</code>, <code>vwsm_authorization_server_url</code>, <code>vwsm_rest_401_headers</code>, <code>vwsm_external_oauth_onboarding_urls</code>, <code>vwsm_onboarding_oauth_tab_content</code>, <code>vwsm_handle_external_register_gpt</code>.</li>
<li>OpenAPI, MCP, and tools: <code>vwsm_ai_actions</code>, <code>vwsm_ai_plugin_integrations</code>, <code>vwsm_ai_plugin_option_integrations</code>, <code>vwsm_ai_plugin_action_dispatch</code>, <code>vwsm_ai_action_native_openapi_tools</code>, <code>vwsm_mcp_server_name</code>, <code>vwsm_mcp_extra_tools</code>, <code>vwsm_mcp_dispatch_tool</code>, <code>vwsm_mcp_site_context</code>, <code>vwsm_openapi_components</code>, <code>vwsm_openapi_document</code>, <code>vwsm_write_rate_limit_mcp_tools</code>.</li>
<li>Content and sanitization: <code>vwsm_allowed_content_types</code>, <code>vwsm_revision_limit</code>, <code>vwsm_revision_gradient</code>, <code>vwsm_supported_extra_allowed_html_tags</code>, <code>vwsm_allow_extra_allowed_html_tags</code>.</li>
<li>User connection workflows: <code>vwsm_user_connect_handle_post</code>, <code>vwsm_user_connect_after_sections</code>, <code>vwsm_user_connect_tools_data</code>, <code>vwsm_user_connect_gpt_url</code>.</li>
<li>Operator and environment behavior: <code>vwsm_default_operator_username</code>, <code>vwsm_use_current_user_mode</code>.</li>
</ol>
<h3>Disclaimer</h3>
This plugin provides infrastructure for operating a WordPress site with external AI chatbots and agents. The site owner is solely responsible for the actions enabled through this functionality, including content created or changed by AI tools, credentials and access tokens, backups, privacy compliance, and any publishing or policy consequences.
AI-generated content can be inaccurate, defamatory, plagiarized, non-compliant, or otherwise unsuitable for publication. Review AI output and tool activity before publishing. Keep publishing disabled unless you fully understand and accept the risk.
Use HTTPS, protect Application Passwords and OAuth credentials, restrict access where possible, monitor logs, and maintain independent backups. Use at your own risk.
<h3>Privacy</h3>
This plugin stores the following data on your WordPress site:
<ul>
<li>Plugin settings in WordPress options (for example: publish, rate limit, HTTPS, IP allowlist, authentication, and provider URL settings)</li>
<li>Audit log entries in a custom database table (<code>*_vwsm_audit_logs</code>)</li>
<li>Optional dedicated operator user ID reference in WordPress options (when using onboarding helper)</li>
<li>Short-lived transient for one-time Application Password display after creation (plaintext is not stored long-term)</li>
<li>Short-lived transient cache for external bearer-token validation, when Turnkey OAuth is used</li>
<li>Optional connected service account tokens, site keys, server URLs, and provider policy links used for remote account and Turnkey OAuth workflows</li>
</ul>
Audit logs may include:
<ul>
<li>Authenticated WordPress user ID</li>
<li>Request route and method</li>
<li>Sanitized request/response summaries</li>
<li>Timestamp and IP address</li>
</ul>
This plugin does not send data to third-party AI services by itself. 
This plugin does not include telemetry/analytics tracking by default.
Site owners are responsible for:
<ul>
<li>Securing the site with HTTPS</li>
<li>Managing WordPress users and Application Passwords</li>
<li>Configuring GPT sharing safely (recommended: Only Me)</li>
<li>Reviewing the privacy implications of any external AI service connected to the site’s API</li>
</ul>

AI Site Manager – Using ChatGPT Claude Codex

Manage WordPress content from ChatGPT, Claude, and Codex using secure REST, OpenAPI, MCP, Turnkey OAuth, or WordPress Application Passwords.

Axtolab AI Connector vs AI Site Manager – Using ChatGPT Claude Codex