Title: Born Creative MCP Server Author: jonathansblog Published: Òkúdù 16, 2026 Last modified: Òkúdù 16, 2026 --- Ṣàwárí àwọn plugin ![](https://s.w.org/plugins/geopattern-icon/born-creative-mcp-server.svg) # Born Creative MCP Server Láti ọwọ́ [jonathansblog](https://profiles.wordpress.org/jonathansblog/) [Ṣe ìgbàsílẹ̀](https://downloads.wordpress.org/plugin/born-creative-mcp-server.zip) * [Àwọn àlàyé](https://yor.wordpress.org/plugins/born-creative-mcp-server/#description) * [Àwọn àgbéyẹ̀wò](https://yor.wordpress.org/plugins/born-creative-mcp-server/#reviews) * [Ìgbéwọlẹ̀](https://yor.wordpress.org/plugins/born-creative-mcp-server/#installation) * [Ìdàgbàsókè](https://yor.wordpress.org/plugins/born-creative-mcp-server/#developers) [Ìrànlọ́wọ́](https://wordpress.org/support/plugin/born-creative-mcp-server/) ## Àpèjúwe 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** * **Posts** — list, get, create, update, delete, search * **Pages** — list, get, create, update, delete * **Media** — list, get, upload from URL, upload base64-encoded, delete * **Categories** — list, create, update * **Tags** — list, create * **Yoast SEO** _(optional)_ — get and update Yoast SEO metadata (requires Yoast SEO plugin) **OAuth 2.1 Authentication** * Dynamic client registration (RFC 7591) * Authorization code flow with PKCE * Access token and refresh token lifecycle management * Token rotation and revocation * Tokens are SHA-256 hashed — plaintext tokens are never stored **Advanced content features** * Schedule posts by setting a future publish date * Set featured images * Add custom post meta * Sideload media from external URLs * Full category and tag assignment **Yoast SEO integration** If the Yoast SEO plugin is active, two additional MCP tools are automatically registered:` yoast_get_seo` and `yoast_update_seo`, allowing AI assistants to read and write SEO titles, descriptions, and focus keywords. ## Ìgbéwọlẹ̀ 1. Upload the `born-creative-mcp-server` folder to `/wp-content/plugins/`. 2. Activate the plugin through the **Plugins** menu in WordPress. 3. Navigate to **Settings > MCP Server** to review configuration options. 4. Ensure your site uses HTTPS — required for OAuth 2.1 in production. 5. If using nginx, ensure your server config permits access to `/.well-known/` paths. 6. Connect your MCP client (e.g. Claude.ai) using the OAuth authorization server URL displayed in the plugin settings. ## FAQ ### What is MCP? Model Context Protocol (MCP) is an open standard that allows AI assistants to interact with external tools and data sources in a structured way. This plugin implements the MCP server side of that protocol over HTTP. ### Which AI assistants are supported? Any MCP-compatible client that supports the streamable HTTP transport and OAuth 2.1 with PKCE. Claude.ai (claude.ai/settings/integrations) is the primary tested client. ### Is HTTPS required? Yes, for production use. OAuth 2.1 requires HTTPS to protect bearer tokens and authorization codes in transit. The plugin will function over HTTP for local development only. ### Can any WordPress user authorise an MCP client? No. Only authenticated WordPress users can complete the OAuth consent flow. The MCP session inherits that userÌtumọ̀ Yorùbá: ’s capabilities, so content tools are limited to what that user is permitted to do within WordPress. ### Does this plugin store access tokens in the database? Tokens are stored as SHA-256 hashes — the plaintext token is only ever visible to the client at the moment it is issued. This means tokens cannot be recovered from the database if compromised. ### What database tables does the plugin create? Four tables are created on activation (using your configured table prefix): born_mcp_oauth_clients,` born_mcp_oauth_codes`, `born_mcp_oauth_tokens`, `born_mcp_sessions`. All tables are removed on uninstall. ### Does the plugin support Yoast SEO? Yes. If Yoast SEO is active, two additional tools — `yoast_get_seo` and `yoast_update_seo`— are automatically registered. No additional configuration is needed. ## Àwọn àgbéyẹ̀wò Kò sí àwọn àgbéyẹ̀wò fún plugin yìí. ## Àwọn Olùkópa & Olùgbéejáde “Born Creative MCP Server” jẹ́ ètò ìṣàmúlò orísun ṣíṣí sílẹ̀. Àwọn ènìyàn wọ̀nyí ti ṣe ìkópa sí plugin yìí. Àwọn Olùkópa * [ jonathansblog ](https://profiles.wordpress.org/jonathansblog/) * [ borncreative ](https://profiles.wordpress.org/borncreative/) [Túmọ̀ “Born Creative MCP Server” sí èdè rẹ.](https://translate.wordpress.org/projects/wp-plugins/born-creative-mcp-server) ### Ṣe o nífẹ̀ẹ́ sí ìdàgbàsókè? [Ṣàwárí koodu](https://plugins.trac.wordpress.org/browser/born-creative-mcp-server/), ṣàyẹ̀wò [ibi ìpamọ́ SVN](https://plugins.svn.wordpress.org/born-creative-mcp-server/), tàbí ṣe àgbékalẹ̀ sí [àkọsílẹ̀ ìdàgbàsókè](https://plugins.trac.wordpress.org/log/born-creative-mcp-server/) nípasẹ̀ [RSS](https://plugins.trac.wordpress.org/log/born-creative-mcp-server/?limit=100&mode=stop_on_copy&format=rss). ## Àkọsílẹ̀ àwọn àyípadà #### 0.0.1 * Initial release. * OAuth 2.1 with PKCE authorization code flow. * Dynamic client registration (RFC 7591). * 18 MCP tools: posts, pages, media, categories, tags, and optional Yoast SEO. * Streamable HTTP MCP transport (JSON-RPC 2.0). * SHA-256 token hashing, token rotation, and revocation. * Admin settings page and active connections view. * Automatic `.well-known/oauth-authorization-server` metadata endpoint. ## Àkójọpọ̀ Meta * Ẹ̀yà **0.0.6** * Ìgbàgbọ́hùn tó kẹ́yìn **oṣù 4 sẹ́yìn** * Àwọn ìgbéwọlẹ̀ tó ṣiṣẹ́ **Tó kéré sí 10** * Ẹ̀yà WordPress ** 6.0 tàbí ju bẹ́ẹ̀ lọ ** * Dánwò dé **6.9.10** * Ẹ̀yà PHP ** 8.1 tàbí ju bẹ́ẹ̀ lọ ** * Èdè * [English (US)](https://wordpress.org/plugins/born-creative-mcp-server/) * Àwọn àmì * [AI](https://yor.wordpress.org/plugins/tags/ai/)[Claude](https://yor.wordpress.org/plugins/tags/claude/) [mcp](https://yor.wordpress.org/plugins/tags/mcp/)[oauth](https://yor.wordpress.org/plugins/tags/oauth/) [rest-api](https://yor.wordpress.org/plugins/tags/rest-api/) * [Ìwòye Tó Péye](https://yor.wordpress.org/plugins/born-creative-mcp-server/advanced/) ## Àwọn ìbò Kò sí ìwádìí tí a tíì fi ránṣẹ́. [Your review](https://wordpress.org/support/plugin/born-creative-mcp-server/reviews/#new-post) [Wo gbogbo àwọn àgbéyẹ̀wò](https://wordpress.org/support/plugin/born-creative-mcp-server/reviews/) ## Àwọn Olùkópa * [ jonathansblog ](https://profiles.wordpress.org/jonathansblog/) * [ borncreative ](https://profiles.wordpress.org/borncreative/) ## Ìrànlọ́wọ́ Nǹkan wà tí o fẹ́ sọ? Ṣé o nílò ìrànlọ́wọ́? [Wo àpéjọ ìrànlọ́wọ́](https://wordpress.org/support/plugin/born-creative-mcp-server/)