strifero

<p>StrifeBridge MCP turns your WordPress site into an MCP (Model Context Protocol) endpoint that AI assistants like Claude can connect to directly. Instead of describing a change to an AI and then applying it yourself, you ask and it happens.</p>
<p>Want to add a blog post? Ask Claude. Need to update a menu item? Ask Claude. Wondering which pages are missing SEO metadata? Ask Claude to check and fix them.</p>
<p>StrifeBridge MCP exposes a structured, token-authenticated REST API and MCP server inside your WordPress install. AI assistants that support MCP (Claude.ai, Claude Desktop, Cursor, Windsurf, and any MCP-capable agent framework) can connect to it and perform tasks across your site through natural language.</p>
<h4>What you can do</h4>
<ul>
<li>Create, update, and delete posts, pages, and custom post types</li>
<li>Upload files to the media library and manage attachments</li>
<li>Read and write WordPress options, with a security blacklist for sensitive keys</li>
<li>Manage navigation menus, taxonomy terms, and widgets</li>
<li>List, activate, deactivate, and delete plugins</li>
<li>List users and inspect their roles</li>
<li>Get site info, flush rewrite rules</li>
</ul>
<h4>How it works</h4>
<ol>
<li>Install and activate the plugin</li>
<li>Go to Settings and copy your Connector URL (the bearer token is embedded in the path)</li>
<li>Paste the URL into your AI assistant as a custom MCP connector</li>
<li>Ask the assistant to do things on your site</li>
</ol>
<p>No middleware, no third-party relay service. Every request goes from your AI assistant directly to your own WordPress site. You own the endpoint, you own the token, and you can revoke access at any time from Settings.</p>
<h4>Compatible with</h4>
<ul>
<li>Claude.ai (web and desktop) — primary integration</li>
<li>Claude Desktop app</li>
<li>Cursor</li>
<li>Windsurf</li>
<li>Any MCP-capable agent framework</li>
</ul>
<h4>Security</h4>
<p>StrifeBridge MCP was designed with security as a first-class concern:</p>
<ul>
<li>Bearer token authentication on every request, validated with constant-time <code>hash_equals()</code></li>
<li>WordPress secret keys, auth salts, and the plugin’s own token are blacklisted from the options API</li>
<li>Emergency Lockdown button in Settings disables the entire API with one click</li>
<li>Every tool group (posts, media, menus, etc.) can be individually toggled off from Settings</li>
<li>The plugin includes no outbound network calls, no analytics, and no tracking</li>
</ul>
<h4>Compatibility with self-hosted WordPress</h4>
<p>StrifeBridge MCP works on any self-hosted WordPress installation running WordPress 5.6 or higher. WordPress.com and WordPress Multisite are not currently supported.</p>
<h4>Extending StrifeBridge MCP</h4>
<p>StrifeBridge MCP exposes extension hooks that let add-on plugins register additional MCP tools without modifying the core plugin. Developers can hook into <code>sbmcp_register_rest_routes</code>, <code>sbmcp_mcp_tools</code>, <code>sbmcp_mcp_tool_call</code>, <code>sbmcp_tool_groups</code>, and <code>sbmcp_admin_after_settings</code> to add routes, tools, admin UI, and tool groups. This is how separately distributed add-ons extend the plugin with features like file editing, database queries, and user management.</p>


StrifeBridge MCP

Connect your WordPress site to Claude and other AI assistants through the Model Context Protocol. Manage posts, media, menus, and more in plain Englis …

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.

StrifeBridge MCP vs AI Conduit