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 …

Mehul Gohil

<p>Aculect AI Companion is a secure MCP connector for WordPress. It lets approved AI assistants such as ChatGPT, Claude, Codex, and OpenAI-compatible tools work with your WordPress content, media, comments, and site information through permission-aware workflows.</p>
<p>Instead of switching between WordPress admin screens, you can ask your AI assistant in plain English to draft a post, update a page, review comments, upload media, inspect safe site details, or prepare long-form content using WordPress blocks.</p>
<p>WordPress remains the source of truth. Aculect AI Companion checks the connected WordPress user’s permissions before every action, lets administrators choose which abilities are available, and keeps risky write actions behind configurable controls.</p>
<h4>What is MCP for WordPress?</h4>
<p>MCP stands for Model Context Protocol. In Aculect AI Companion, MCP gives supported AI assistants a structured, permission-controlled way to request WordPress actions. The assistant does not receive direct database access. It can only use the enabled tools exposed by WordPress and approved by an administrator.</p>
<h4>Why use Aculect AI Companion?</h4>
<ul>
<li>Connect WordPress to ChatGPT, Claude, Codex, and OpenAI-compatible MCP clients</li>
<li>Create, update, and organize WordPress content through controlled AI workflows</li>
<li>Work with posts, pages, custom post types, categories, tags, comments, and media</li>
<li>Use block-aware content workflows instead of raw custom HTML</li>
<li>Review AI activity with sanitized audit logs</li>
<li>Control access globally, by connection, by role, and by WordPress user permissions</li>
<li>Use diagnostics to verify OAuth, MCP, endpoint, and environment readiness</li>
</ul>
<p>Setup is designed to be simple:</p>
<ol>
<li>Copy your connection URL from AI Companion > Connect.</li>
<li>Open your AI tool and add a new connector.</li>
<li>Paste the URL when prompted.</li>
<li>Approve the connection on the screen that appears.</li>
</ol>
<p>After approval, Aculect AI Companion checks the connected WordPress user’s permissions before every action. You can also choose exactly what your AI assistant can do and disconnect assistants at any time.</p>
<h4>Features</h4>
<ul>
<li>Create, edit, and publish posts, pages, and supported custom post types</li>
<li>Plan and draft long-form block content for WordPress</li>
<li>Manage categories, tags, custom taxonomies, and content groups</li>
<li>Moderate, reply to, and bulk-manage comments</li>
<li>Upload, list, update, attach, detach, and safely rename media</li>
<li>View safe site settings, active plugins, active themes, and diagnostics</li>
<li>Connect, pause, review, and disconnect AI assistants</li>
<li>Control which MCP abilities each assistant can use</li>
</ul>
<h4>Supported AI Tools</h4>
<p>Aculect AI Companion includes setup guidance for popular AI assistants and MCP clients:</p>
<ul>
<li>ChatGPT app with Developer Mode connectors</li>
<li>OpenAI API integrations that support remote connectors</li>
<li>Claude app, Claude Desktop, Claude Cowork, and Claude mobile</li>
<li>Claude Code</li>
<li>Claude API integrations that support remote connectors</li>
</ul>
<p>Your AI tool must be able to reach your WordPress site over HTTPS to complete OAuth approval and send MCP requests.</p>
<h4>Supported Abilities</h4>
<p>Admins can enable or disable these abilities from AI Companion > Abilities after the first assistant connection is active.</p>
<p>Long-form content workflows:</p>
<ul>
<li>Prepare a post outline, section plan, taxonomy recommendations, media recommendations, and SEO recommendations</li>
<li>Create a draft from validated serialized WordPress block content</li>
<li>Update an existing post with block-safe content workflows</li>
<li>Update Rank Math SEO title, description, and focus keywords when Rank Math is active</li>
</ul>
<p>Content:</p>
<ul>
<li>List readable content types, including custom post types</li>
<li>List posts, pages, and custom content items with pagination</li>
<li>Read one content item by ID</li>
<li>Create a post, page, or custom content item with optional featured image, author, and taxonomy assignments</li>
<li>Update title, content, excerpt, slug, status, featured image, author, or taxonomy assignments for an existing item</li>
<li>Update SEO title, SEO description, and focus keywords for supported SEO plugins</li>
</ul>
<p>Content groups:</p>
<ul>
<li>List available categories, tags, and custom content groups</li>
<li>List terms for a supported taxonomy with pagination</li>
<li>Create a category, tag, or custom content group</li>
<li>Update a category, tag, or custom content group</li>
<li>Assign or clear an image for supported taxonomy terms</li>
</ul>
<p>Comments:</p>
<ul>
<li>List comments for review with pagination</li>
<li>Read one comment by ID</li>
<li>Reply to a comment as the connected WordPress user</li>
<li>Moderate comment content or status</li>
<li>Bulk moderate multiple comments</li>
</ul>
<p>Media:</p>
<ul>
<li>List media library attachments with pagination</li>
<li>Read, update, trash, and safely rename media items</li>
<li>Upload media from a public URL with server-side request checks</li>
<li>Attach media to posts or detach media from posts</li>
</ul>
<p>Site information:</p>
<ul>
<li>View safe, non-secret site settings</li>
<li>View WordPress version, PHP version, active theme, and basic site metadata</li>
<li>List installed plugins and active state for users who can manage plugins</li>
<li>List installed themes and active state for users who can manage themes</li>
</ul>
<p>WordPress abilities:</p>
<ul>
<li>Discover supported public WordPress abilities registered by WordPress and plugins</li>
<li>Inspect one supported public WordPress ability</li>
<li>Run a supported public WordPress ability using the connected user’s permissions</li>
</ul>
<h3>Third Party Services</h3>
<p>Aculect AI Companion does not send site data to an external service on activation, page load, cron, or without a site administrator connecting an AI assistant.</p>
<p>When a site administrator copies the connection URL into an external AI assistant and approves the connection screen in WordPress, that assistant can request the enabled abilities. Depending on the enabled abilities and the connected WordPress user’s permissions, requested data may include post titles, post content, excerpts, slugs, statuses, authors, dates, permalinks, category and tag names, media metadata, comments, and safe site settings such as site name, description, URLs, locale, timezone, date format, time format, permalink structure, and active theme name.</p>
<p>The external service that receives this data is the AI assistant selected and configured by the administrator. Aculect AI Companion’s built-in setup UI includes links for:</p>
<ul>
<li>ChatGPT by OpenAI: https://chatgpt.com/, terms at https://openai.com/policies/terms-of-use/, and privacy policy at https://openai.com/policies/row-privacy-policy/</li>
<li>Claude by Anthropic: https://claude.ai/, terms at https://www.anthropic.com/legal/consumer-terms, and privacy policy at https://www.anthropic.com/legal/privacy</li>
</ul>
<p>Administrators should review the terms and privacy policy for the AI assistant they connect. Aculect AI Companion controls the WordPress-side approval and permissions checks; it does not control how a connected external assistant processes data after the administrator authorizes access.</p>
<h3>Development</h3>
<p>The production package ships built assets and Composer dependencies. Development manifests such as <code>composer.json</code>, <code>composer.lock</code>, and <code>package.json</code> are intentionally excluded from release ZIP files. Generated files under <code>build/</code> are not committed to the source repository; release automation generates them before packaging.</p>
<p>For source code, build tooling, and exact dependency manifests, use the public GitHub repository:</p>
<p>https://github.com/mehul0810/aculect-ai-companion</p>
<p>Contributing guidelines:</p>
<p>https://github.com/mehul0810/aculect-ai-companion/blob/main/CONTRIBUTING.md</p>
<p>Security policy:</p>
<p>https://github.com/mehul0810/aculect-ai-companion/security/policy</p>
<p>From the repository checkout, use the Node.js version in <code>.nvmrc</code> and rebuild assets with:</p>
<pre><code>npm ci
npm run build
</code></pre>
<p>Composer dependencies for production releases are installed with:</p>
<pre><code>composer install --no-dev --prefer-dist --optimize-autoloader
</code></pre>


Aculect AI Companion

Use ChatGPT, Claude, Codex, and other MCP AI assistants to manage WordPress content, media, comments, and site workflows.

StrifeBridge MCP vs Aculect AI Companion