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.

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.

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.

What you can do

Create, update, and delete posts, pages, and custom post types
Upload files to the media library and manage attachments
Read and write WordPress options, with a security blacklist for sensitive keys
Manage navigation menus, taxonomy terms, and widgets
List, activate, deactivate, and delete plugins
List users and inspect their roles
Get site info, flush rewrite rules

How it works

Install and activate the plugin
Go to Settings and copy your Connector URL (the bearer token is embedded in the path)
Paste the URL into your AI assistant as a custom MCP connector
Ask the assistant to do things on your site

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.

Compatible with

Claude.ai (web and desktop) — primary integration
Claude Desktop app
Cursor
Windsurf
Any MCP-capable agent framework

Security

StrifeBridge MCP was designed with security as a first-class concern:

Bearer token authentication on every request, validated with constant-time hash_equals()
WordPress secret keys, auth salts, and the plugin’s own token are blacklisted from the options API
Emergency Lockdown button in Settings disables the entire API with one click
Every tool group (posts, media, menus, etc.) can be individually toggled off from Settings
The plugin includes no outbound network calls, no analytics, and no tracking

Compatibility with self-hosted WordPress

StrifeBridge MCP works on any self-hosted WordPress installation running WordPress 5.6 or higher. WordPress.com and WordPress Multisite are not currently supported.

Extending StrifeBridge MCP

StrifeBridge MCP exposes extension hooks that let add-on plugins register additional MCP tools without modifying the core plugin. Developers can hook into sbmcp_register_rest_routes, sbmcp_mcp_tools, sbmcp_mcp_tool_call, sbmcp_tool_groups, and sbmcp_admin_after_settings 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.