Mark Jansen

Albert

<p>Every well-run site deserves a proper butler. Albert stands at the door of your WordPress site, ready to welcome AI assistants like Claude and ChatGPT and put them to work.</p>
<h4>An open door for AI assistants</h4>
<p>Install Albert, grant an AI assistant access, and it can start managing your site — writing and editing posts, organizing media, moderating comments, and handling day-to-day tasks. No custom code, no complicated setup. Albert takes care of the introductions.</p>
<h4>A well-stocked service tray</h4>
<p>Albert presents AI assistants with a curated set of abilities — the tasks they’re permitted to carry out on your site. When plugins like WooCommerce or Advanced Custom Fields are active, Albert extends the service with additional abilities tailored to each one.</p>
<h4>The butler manages the household</h4>
<p>Not every guest needs access to every room. From the admin panel, you decide exactly which abilities are on the tray and which stay behind closed doors. You remain in charge — Albert just makes sure your instructions are followed.</p>
<h4>Proper credentials at the door</h4>
<p>Every AI assistant must present proper credentials before Albert lets them in. Connections are secure, scoped, and fully under your control.</p>
<h3>Privacy Policy</h3>
<p>Albert does not collect, store, or transmit any user data to external servers. All authentication tokens are stored locally in your WordPress database. When you authorize an AI assistant, that assistant will have access to perform actions on your WordPress site according to the permissions you grant. You control which abilities are enabled and can revoke any session at any time.</p>
<h3>Credits</h3>
<p>Developed by Mark Jansen – Your Mark Media<br />
Website: https://yourmark.nl<br />
Plugin URL: https://github.com/YourMark/albert-ai-butler</p>
<p>Built with:<br />
* league/oauth2-server for OAuth 2.0 implementation<br />
* Model Context Protocol (MCP) for AI assistant connectivity<br />
* WordPress Coding Standards</p>


Albert – The AI Butler


I was looking for a better way to give GPT access to my WordPress site. Previously I would allow it to connect using WP CLI over SSH, but it's hard to manage (scoped) permissions that way. With Albert I was able to allow my AI agent access to my WordPress sites with very granular permissions, so I could be sure it would not accidentally perform a destructive action. Installation was smooth. Plugin setting pages look clean. No PHP errors or notices in my logs. Glad I took the plunge and gave this plugin a try.


First! Great plugin to connect WordPress to GPT.


I needed something to sit between ChatGPT/Claude and WordPress so end users could drive the site by just talking, like “create a project for this client” or “add this document” (based on the conversation context). I was dreading wiring up MCP and OAuth myself. Turns out I didn’t have to! My non-technical users connect their assistant by pasting one MCP URL and signing in with their normal WordPress account through oauth, and because of that, every action respects existing WordPress capabilities, so the AI can’t do anything the user couldn’t.



Albert builds on the WordPress Abilities API, so I added my own AI-callable actions by writing a few small classes (id, description, input schema, permission callback) and they showed up as MCP tools right away and in Albert’s admin page with enable/disable toggles.


a clean way to let ChatGPT actually do things in WordPress

At your service — Albert connects AI assistants to your WordPress site so they can manage content, handle tasks, and keep things running smoothly.

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 …

Albert – The AI Butler vs StrifeBridge MCP