WisdmLabs

<p>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.</p>
<p>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.</p>
<h4>WordPress 7.0 has AI infrastructure — so why AI Conduit?</h4>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<h4>What can you use it for?</h4>
<ul>
<li><strong>Customer Support</strong> — Ask your AI “what did customer John order last week?” and get the answer without opening WooCommerce. Save hours every week.</li>
<li><strong>E-commerce</strong> — “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><strong>Content Teams</strong> — “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><strong>Course Creators</strong> — With LearnDash, ask “which students haven’t completed Module 3?” and follow up personally — without running a single report.</li>
<li><strong>Site Owners</strong> — “Give me a weekly digest of new signups, published posts, and comments.” Your AI becomes a personal briefing assistant for your site.</li>
<li><strong>Agencies</strong> — 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><strong>Install and activate the plugin.</strong> Upload to WordPress the same way you install any other plugin. Takes about two minutes.</li>
<li><strong>Build your first tool with drag-and-drop.</strong> Choose what data your AI can see — posts, orders, users, comments. No code required. Point, click, configure.</li>
<li><strong>Connect your AI and start asking questions.</strong> 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><strong>Read-only access</strong> — Your AI can never edit, delete, or publish anything on your site. Ever.</li>
<li><strong>Role-based controls</strong> — Decide exactly which WordPress roles can access which tools.</li>
<li><strong>Full request log</strong> — Every query your AI makes is logged so you always know what was asked.</li>
</ul>
<h4>Everything included</h4>
<ul>
<li><strong>Visual tool builder</strong> — No code. Drag blocks to define what your AI can access.</li>
<li><strong>Rich data sources</strong> — Posts, pages, users, comments, and custom fields — all queryable.</li>
<li><strong>Smart filters</strong> — Narrow by date, category, author, custom field value, and more.</li>
<li><strong>Cross-data queries</strong> — Combine posts with their authors or comments with their posts in one query.</li>
<li><strong>Import & export tools</strong> — Save your tool configuration as JSON and reuse it across sites instantly.</li>
<li><strong>Rate limiting</strong> — 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><strong>WooCommerce store owners</strong> — Query orders, customers, and product data without leaving your AI chat.</li>
<li><strong>LearnDash course creators</strong> — Track enrolments, completions, and quiz scores through natural conversation.</li>
<li><strong>Content editors & bloggers</strong> — Audit your content library, find gaps, and surface your best posts with ease.</li>
<li><strong>WordPress developers</strong> — Build custom MCP tools for clients. Extensible with your own block types.</li>
</ul>
<h4>Works with your favourite AI tools</h4>
<p>AI Conduit connects to any AI app that supports the Model Context Protocol (MCP). That includes:</p>
<ul>
<li>Claude Desktop</li>
<li>Cursor</li>
<li>Any MCP-compatible client</li>
</ul>
<p>New AI tools are adding MCP support every month — any compatible client will work automatically.</p>


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.

videowhisper

<p>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.</p>
<p>It provides:</p>
<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>
<p>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.</p>
<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>
<p>The onboarding flow recommends using one authentication option for clarity, but development and migration setups can enable more than one.</p>
<ul>
<li><strong>Turnkey OAuth</strong> – 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><strong>Application Passwords</strong> – 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><strong>Extension-provided authentication</strong> – 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 <strong>VideoWhisper Site Manager > Onboarding</strong>.</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>
<p>The free plugin includes an MCP endpoint at <code>/wp-json/videowhisper-site-manager/v1/mcp</code>.</p>
<p><strong>Claude.ai (web):</strong></p>
<ol>
<li>Go to <code>claude.ai/customize/connectors</code>.</li>
<li>Click the <strong>+</strong> button in the Connectors sidebar <span aria-hidden="true" class="wp-exclude-emoji">→</span> <strong>Add custom connector</strong>.</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 <strong>Claude mobile apps</strong> (iOS and Android) and desktop once authorized.</li>
</ol>
<p><strong>Claude CLI:</strong></p>
<p>claude mcp add –transport http “YourSiteName” “https://yoursite.com/wp-json/videowhisper-site-manager/v1/mcp”</p>
<p>Automatic OAuth authorization requires a compatible Relay & OAuth Server. Without that connection, use WordPress Application Passwords over HTTPS.</p>
<h4>Connecting Codex (MCP)</h4>
<p>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>.</p>
<ol>
<li>Open <strong>VideoWhisper Site Manager > Onboarding</strong> 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><strong>MCP endpoint</strong> for Claude.ai, Claude Desktop, Claude CLI, Claude mobile apps, and Codex — implements MCP Streamable HTTP transport (protocol 2025-03-26)</li>
<li><strong>ChatGPT / GPT Actions</strong> integration via generated OpenAPI schema URL (<code>/wp-json/videowhisper-site-manager/v1/openapi</code>)</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>Extension Hooks</h3>
<p>Developers can extend this plugin without editing core files. Common hooks include:</p>
<ol>
<li><strong>Settings and admin UI:</strong> <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><strong>Authentication and OAuth metadata:</strong> <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><strong>OpenAPI, MCP, and tools:</strong> <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><strong>Content and sanitization:</strong> <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><strong>User connection workflows:</strong> <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><strong>Operator and environment behavior:</strong> <code>vwsm_default_operator_username</code>, <code>vwsm_use_current_user_mode</code>.</li>
</ol>
<h3>Disclaimer</h3>
<p>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.</p>
<p>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.</p>
<p>Use HTTPS, protect Application Passwords and OAuth credentials, restrict access where possible, monitor logs, and maintain independent backups. Use at your own risk.</p>
<h3>Privacy</h3>
<p>This plugin stores the following data on your WordPress site:</p>
<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>
<p>Audit logs may include:</p>
<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>
<p>This plugin does not send data to third-party AI services by itself.<br />
This plugin does not include telemetry/analytics tracking by default.</p>
<p>Site owners are responsible for:</p>
<ul>
<li>Securing the site with HTTPS</li>
<li>Managing WordPress users and Application Passwords</li>
<li>Configuring GPT sharing safely (recommended: <strong>Only Me</strong>)</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.

AI Conduit vs AI Site Manager – Using ChatGPT Claude Codex