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.

Deepak Gupta

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


AcrossAI MCP Manager

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

AI Conduit vs AcrossAI MCP Manager