jonathansblog

borncreative

Born Creative MCP Server transforms your WordPress site into a fully authenticated remote MCP (Model Context Protocol) endpoint. It allows AI assistants — such as Claude.ai — to securely connect to your site and create, update, schedule, and manage posts, pages, media, and taxonomy, all via a standards-compliant OAuth 2.1 and JSON-RPC 2.0 interface.
Unlike local stdio-based MCP servers, this plugin exposes a remote HTTP transport, meaning your AI tools can connect to your live WordPress site without needing direct server access.
How it works
The plugin registers a set of REST API endpoints that implement the MCP streamable HTTP transport. Clients authenticate using OAuth 2.1 with PKCE (Proof Key for Code Exchange), receive a bearer access token, and then use that token to call any of the 18 built-in MCP tools.
MCP Tools included
<ul>
<li>Posts — list, get, create, update, delete, search</li>
<li>Pages — list, get, create, update, delete</li>
<li>Media — list, get, upload from URL, upload base64-encoded, delete</li>
<li>Categories — list, create, update</li>
<li>Tags — list, create</li>
<li>Yoast SEO (optional) — get and update Yoast SEO metadata (requires Yoast SEO plugin)</li>
</ul>
OAuth 2.1 Authentication
<ul>
<li>Dynamic client registration (RFC 7591)</li>
<li>Authorization code flow with PKCE</li>
<li>Access token and refresh token lifecycle management</li>
<li>Token rotation and revocation</li>
<li>Tokens are SHA-256 hashed — plaintext tokens are never stored</li>
</ul>
Advanced content features
<ul>
<li>Schedule posts by setting a future publish date</li>
<li>Set featured images</li>
<li>Add custom post meta</li>
<li>Sideload media from external URLs</li>
<li>Full category and tag assignment</li>
</ul>
Yoast SEO integration
If the Yoast SEO plugin is active, two additional MCP tools are automatically registered: <code>yoast_get_seo</code> and <code>yoast_update_seo</code>, allowing AI assistants to read and write SEO titles, descriptions, and focus keywords.

Born Creative MCP Server

A remote MCP server over HTTP with OAuth 2.1, letting AI assistants like Claude securely create, update, and schedule WordPress content.

Deepak Gupta

MCP Manager uses the standard <code>@automattic/mcp-wordpress-remote@latest</code> package with WordPress Application Passwords for the default remote flow. It also includes an optional experimental direct Claude Connectors mode backed by a WordPress-hosted OAuth approval flow.
MCP Manager is a WordPress plugin that enables seamless integration with Model Context Protocol (MCP) servers, allowing AI assistants and code editors to safely access your WordPress instance through secure application passwords.
<h4>Key Features</h4>
<ul>
<li>
Multi-Client Support: Configure MCP for:
<ul>
<li>VS Code with Copilot</li>
<li>Claude Desktop App</li>
<li>GitHub Copilot & Codex</li>
<li>OpenAI ChatGPT Codex</li>
<li>Custom MCP Clients</li>
</ul>
</li>
<li>
Secure Authentication: Uses WordPress native Application Passwords system
<ul>
<li>One-click password generation</li>
<li>Secure credential management</li>
<li>Password revocation support</li>
<li>Per-server Access Control still enforced after authentication</li>
</ul>
</li>
<li>
Easy Configuration:
<ul>
<li>Copy-paste ready JSON configurations</li>
<li>Per-provider configuration file paths</li>
<li>Automatic top-level key detection</li>
</ul>
</li>
<li>
Format #1 Standard: Uses the Automattic-recommended MCP configuration format
<ul>
<li>npx command execution</li>
<li>@automattic/mcp-wordpress-remote@latest package</li>
<li>Full environment variable support</li>
</ul>
</li>
</ul>
<h4>How It Works</h4>
<ol>
<li>Navigate to Settings → MCP Manager</li>
<li>Select your MCP client (VS Code, Claude, GitHub Copilot, ChatGPT, or Custom)</li>
<li>Click “Generate New Application Password”</li>
<li>Copy the ready-to-use JSON configuration</li>
<li>Paste into your client’s configuration file</li>
<li>Restart your MCP client</li>
</ol>
All application passwords are managed through WordPress’s native Application Passwords system and appear in your profile under Account Management.
<h4>CLI Connection and Authorization Flow</h4>
MCP Manager also supports a browser-assisted CLI connection flow for local MCP clients.
Typical command:
<pre><code>npx -y @acrossai/mcp-manager --siteurl=https://example.com --server=default-mcp-server
</code></pre>
Flow summary:
<ol>
<li>The CLI checks <code>/wp-json/acrossai-mcp-manager/v1/health</code></li>
<li>The CLI starts auth with <code>/wp-json/acrossai-mcp-manager/v1/auth/start</code></li>
<li>WordPress returns an <code>auth_code</code> and frontend <code>auth_url</code></li>
<li>The CLI opens the frontend approval page at <code>/acrossai-mcp-manager/</code></li>
<li>If needed, the user signs in through normal WordPress login</li>
<li>The signed-in user approves access in the browser</li>
<li>The CLI polls <code>/auth/status</code> until the request is approved</li>
<li>The CLI fetches the approved user’s accessible servers from <code>/servers</code></li>
<li>The CLI exchanges the approved code at <code>/auth/exchange</code></li>
<li>WordPress creates a one-time Application Password and the CLI writes the MCP client config</li>
</ol>
Terminology:
<ul>
<li>Sign in / Log in = WordPress account authentication</li>
<li>Connect = starting the CLI-to-site linking flow</li>
<li>Authorize / Approve access = granting the CLI permission in the browser</li>
</ul>
Important notes:
<ul>
<li>The frontend authorization page must never be cached</li>
<li>Auth codes are single-use</li>
<li><code>/servers</code> and <code>/auth/exchange</code> respect per-server access control</li>
<li>User-facing copy should say CLI Connections rather than npm Login</li>
<li>Generated remote MCP configs use Application Passwords and explicitly disable OAuth discovery in <code>@automattic/mcp-wordpress-remote</code></li>
</ul>
<h4>Experimental Direct Claude Connectors</h4>
An optional Claude Connectors Screen (Experimental) setting can enable a direct OAuth flow for Claude’s hosted connectors.
When the global feature toggle is enabled and a specific server is configured in its Claude Connector tab, the plugin exposes:
<ul>
<li><code>/.well-known/oauth-authorization-server</code></li>
<li><code>/.well-known/oauth-protected-resource?resource=<mcp-url></code></li>
<li><code>/acrossai-mcp-connectors/oauth/authorize/</code></li>
<li><code>/wp-json/acrossai-mcp-manager/v1/connector/oauth/token</code></li>
</ul>
Important notes:
<ul>
<li>Disabled by default</li>
<li>The Application Password flow remains available and supported</li>
<li>The master experimental toggle is global, but OAuth client settings are stored per server</li>
<li>Direct connector approval signs Claude in as a WordPress user</li>
<li>Per-server Access Control still applies to every MCP request after OAuth</li>
<li>Public HTTPS is recommended for hosted connector usage</li>
</ul>
<h4>Provider Configuration Paths</h4>
<ul>
<li>VS Code: ~/.config/Code/User/globalStorage/Copilot.copilot-chat/mcp.json (top-level key: “servers”)</li>
<li>Claude: ~/Library/Application Support/Claude/claude_desktop_config.json (top-level key: “mcpServers”)</li>
<li>GitHub Copilot: ~/.gh-copilot/config.json (top-level key: “servers”)</li>
<li>OpenAI ChatGPT: ~/.config/chatgpt/config.json (top-level key: “servers”)</li>
<li>Custom: ./your-project/.mcp/config.json (top-level key: configurable)</li>
</ul>
<h4>Requirements</h4>
<ul>
<li>WordPress 5.9 or higher</li>
<li>PHP 7.4 or higher</li>
<li>WordPress Application Passwords support (built-in since WP 5.6)</li>
</ul>
<h3>Support & Contribution</h3>
For issues, feature requests, or contributions, visit the plugin repository.
Questions? Check the FAQ section or look for documentation in the plugin settings page.
<h3>Development</h3>
This plugin follows WordPress coding standards and best practices: 
– PHP 7.4+ compatible 
– Full object-oriented architecture 
– Secure nonce verification 
– Proper capability checks 
– Sanitized input validation 
– Escaped output
<h3>License</h3>
This plugin is licensed under the GPL-2.0-or-later license. See LICENSE file for details.
<h3>Credits</h3>
MCP Manager is built with: 
– WordPress native APIs 
– Automattic’s MCP WordPress Remote package 
– WordPress Application Passwords system
Developed with ❤️ for the WordPress community.

AcrossAI MCP Manager

Connect WordPress to MCP clients like VS Code, Claude, and Copilot using secure application passwords.

Born Creative MCP Server vs AcrossAI MCP Manager