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 …

StrifeBridge MCP vs IATO MCP