Title: StrifeBridge MCP
Author: strifero
Published: <strong>May 5, 2026</strong>
Last modified: May 28, 2026

---

Search plugins

![](https://ps.w.org/strifebridge-mcp/assets/icon-256x256.png?rev=3523249)

# StrifeBridge MCP

 By [strifero](https://profiles.wordpress.org/strifero/)

[Download](https://downloads.wordpress.org/plugin/strifebridge-mcp.2.3.0.zip)

 * [Details](https://vec.wordpress.org/plugins/strifebridge-mcp/#description)
 * [Reviews](https://vec.wordpress.org/plugins/strifebridge-mcp/#reviews)
 *  [Installation](https://vec.wordpress.org/plugins/strifebridge-mcp/#installation)
 * [Development](https://vec.wordpress.org/plugins/strifebridge-mcp/#developers)

 [Support](https://wordpress.org/support/plugin/strifebridge-mcp/)

## Description

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

 1. Install and activate the plugin
 2. Go to Settings and copy your Connector URL (the bearer token is embedded in the
    path)
 3. Paste the URL into your AI assistant as a custom MCP connector
 4. 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.

## Installation

 1. Upload the plugin files to the `/wp-content/plugins/strifebridge-mcp` directory,
    or install the plugin through the WordPress Plugins screen directly
 2. Activate the plugin through the Plugins screen in WordPress
 3. Go to Settings → StrifeBridge MCP to get your Connector URL
 4. Paste the Connector URL into Claude.ai (Settings → Integrations → Add custom connector)
    or your preferred MCP-capable AI tool
 5. Ask the AI to manage your site

## FAQ

### What is MCP?

MCP stands for Model Context Protocol. It is an open standard developed by Anthropic
that lets AI assistants connect to external tools and data sources. An MCP server
exposes a set of named tools that an AI can call directly, instead of the AI having
to construct raw HTTP requests.

### Do I need a Claude.ai paid plan?

No. Claude.ai free users can add one custom connector, and StrifeBridge MCP works
as a custom connector. Pro and Team plans can add multiple connectors.

### Does this work with ChatGPT or Gemini?

No. ChatGPT and Gemini use different protocols and do not currently support MCP.

### Does this work on WordPress.com?

No. Only self-hosted WordPress installs (WordPress.org) are supported.

### Does this work on WordPress Multisite?

Not yet. Multisite support is on the roadmap.

### Is my site safe if I install this?

Every request to the plugin requires a bearer token. The token is generated when
you activate the plugin and can be rotated from Settings at any time. There is also
an Emergency Lockdown button in Settings that immediately disables the entire API.
The plugin makes no outbound network calls.

### What happens if the AI makes a mistake?

Always keep backups of your site, and test any significant changes on a staging 
environment first. The plugin includes safety measures (WordPress secret key blacklisting,
one-click lockdown, individual tool group toggles) but it cannot prevent an AI from
making an unintended edit to a post or option if you asked it to.

### Why would I use an MCP plugin instead of just asking the AI for code?

Speed and accuracy. Instead of asking the AI for code, switching tabs, copying it
into SFTP or the admin panel, and hoping it works, you describe what you want and
the AI does it directly. For small repetitive edits, the time savings compound fast.

### Can I add my own MCP tools?

Yes. The plugin exposes extension hooks (`sbmcp_register_rest_routes`, `sbmcp_mcp_tools`,`
sbmcp_mcp_tool_call`, `sbmcp_tool_groups`) that let you register additional routes
and tools from your own code.

### Can I disable individual tool groups?

Yes. Settings → StrifeBridge MCP has toggles for every tool group (posts, media,
options, menus, users, plugins, widgets, taxonomies, system). Turn off anything 
you do not want the AI to access.

## Reviews

There are no reviews for this plugin.

## Contributors & Developers

“StrifeBridge MCP” is open source software. The following people have contributed
to this plugin.

Contributors

 *   [ strifero ](https://profiles.wordpress.org/strifero/)

[Translate “StrifeBridge MCP” into your language.](https://translate.wordpress.org/projects/wp-plugins/strifebridge-mcp)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/strifebridge-mcp/),
check out the [SVN repository](https://plugins.svn.wordpress.org/strifebridge-mcp/),
or subscribe to the [development log](https://plugins.trac.wordpress.org/log/strifebridge-mcp/)
by [RSS](https://plugins.trac.wordpress.org/log/strifebridge-mcp/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 2.3.0

 * Security: Emergency Lockdown now also disables the WordPress Abilities surface,
   not just the MCP and REST endpoints that use the bearer token. Previously, clicking
   Disable API left every tool callable through the Abilities API and MCP Adapter
   path.
 * Security: Plugin internal options (the sbmcp_ prefixed options that store the
   API token, lockdown state, tool group toggles, and the abilities switch) are 
   now blocked from the options tool entirely. Previously a token holder with the
   Options group enabled could switch tool groups back on that an administrator 
   had disabled.
 * Cleanup: uninstall now also removes the sbmcp_abilities_disabled option.

#### 2.2.0

 * New: StrifeBridge tools are now registered as native WordPress Abilities on WordPress
   7.0 and later, so they appear in the core ability registry and can be called 
   through the MCP Adapter by any compatible AI client. The existing StrifeBridge
   MCP endpoint is unchanged and continues to work on all supported versions.
 * The abilities surface runs under the authenticated WordPress user and gates every
   tool with a real capability check (for example edit_posts, upload_files, manage_options),
   independent of the StrifeBridge bearer token.
 * Per tool group toggles in Settings also apply to the abilities surface: a disabled
   group is not exposed as abilities.
 * The abilities bridge can be turned off entirely with the sbmcp_enable_abilities
   filter or the sbmcp_abilities_disabled option.
 * No effect on WordPress versions below 7.0, where the Abilities API does not exist.

#### 2.1.0

 * Verified compatible with WordPress 7.0.
 * Fix: `update_post` now honors `featured_media` (or `thumbnail_id`) to set or 
   remove a post’s featured image. Previously the parameter was silently ignored.
 * Fix: `create_post` now accepts `featured_media` (or `thumbnail_id`) to set a 
   featured image at creation time.
 * Improvement: `list_options` adds an explicit `keys` parameter so callers can 
   fetch a specific allowlist of options instead of dumping the whole options table.
 * Improvement: `list_options` now truncates oversized option values (configurable
   via `max_value_bytes`, default 4096 bytes). Prevents giant serialized transients
   from overwhelming response sizes. Truncated rows are marked with `_truncated:
   true` and `_original_bytes`.

#### 2.0.0

 * Initial release as StrifeBridge MCP for WordPress
 * MCP server with token authentication at `/wp-json/strifebridge/v1/`
 * Posts and pages: create, read, update, delete
 * Media library: list, upload, delete
 * Options: read, write (with security blacklist)
 * Users: list
 * Plugins: list, activate, deactivate, delete
 * Menus: full management of menus and menu items
 * Taxonomies: full management of terms
 * Widgets: list sidebars, read widgets, update widget configuration
 * System: site info, flush rewrite rules
 * Emergency Lockdown button
 * Per-tool-group toggles
 * Extension hooks for add-on plugins

## Meta

 *  Version **2.3.0**
 *  Last updated **1 month ago**
 *  Active installations **20+**
 *  WordPress version ** 5.6 or higher **
 *  Tested up to **7.0**
 *  PHP version ** 7.4 or higher **
 *  Language
 * [English (US)](https://wordpress.org/plugins/strifebridge-mcp/)
 * Tags
 * [AI](https://vec.wordpress.org/plugins/tags/ai/)[automation](https://vec.wordpress.org/plugins/tags/automation/)
   [Claude](https://vec.wordpress.org/plugins/tags/claude/)[mcp](https://vec.wordpress.org/plugins/tags/mcp/)
   [rest-api](https://vec.wordpress.org/plugins/tags/rest-api/)
 *  [Advanced View](https://vec.wordpress.org/plugins/strifebridge-mcp/advanced/)

## Ratings

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/strifebridge-mcp/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/strifebridge-mcp/reviews/)

## Contributors

 *   [ strifero ](https://profiles.wordpress.org/strifero/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/strifebridge-mcp/)