{"id":362342,"date":"2026-09-04T21:07:48","date_gmt":"2026-09-04T21:07:48","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/shim-mcp\/"},"modified":"2026-09-04T21:07:30","modified_gmt":"2026-09-04T21:07:30","slug":"shim-mcp","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/shim-mcp\/","author":16760767,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.0.2","stable_tag":"1.0.2","tested":"7.1","requires":"6.9","requires_php":"8.0","requires_plugins":null,"header_name":"Shim MCP","header_author":"Aditya Raj Singh","header_description":"Connect WordPress to AI in one click. Full MCP server with 56 WordPress abilities, no other plugins needed.","assets_banners_color":"","last_updated":"2026-09-04 21:07:30","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/dev.adityarajsingh.com\/shim-mcp\/","header_author_uri":"https:\/\/adityarajsingh.com","rating":0,"author_block_rating":0,"active_installs":0,"downloads":36,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.0.2":{"tag":"1.0.2","author":"justadityaraj","date":"2026-09-04 21:07:30","revision":3681811}},"upgrade_notice":[],"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3681819,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3681819,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.2"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[2353,569,229563,242115,253991],"plugin_category":[],"plugin_contributors":[279250],"plugin_business_model":[],"class_list":["post-362342","plugin","type-plugin","status-publish","hentry","plugin_tags-ai","plugin_tags-automation","plugin_tags-claude","plugin_tags-mcp","plugin_tags-model-context-protocol","plugin_contributors-justadityaraj","plugin_committers-justadityaraj"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/shim-mcp\/assets\/icon-128x128.png?rev=3681819","icon_2x":"https:\/\/ps.w.org\/shim-mcp\/assets\/icon-256x256.png?rev=3681819","generated":false},"screenshots":[],"raw_content":"<!--section=description-->\n<p>Shim MCP is a self-contained MCP (Model Context Protocol) server plugin for WordPress. It provides 56 abilities that let any MCP-compatible AI client manage your WordPress site -- posts, pages, media, users, plugins, menus, widgets, comments, options, and system settings. The MCP server and every ability ship in the one plugin, so no companion plugins are required.<\/p>\n\n<p>The MCP protocol layer is derived from the WordPress project's own MCP Adapter (GPL-2.0), and abilities are registered through WordPress's Abilities API, which core ships from 6.9. See the Credits section below.<\/p>\n\n<p>Key features:<\/p>\n\n<ul>\n<li>56 WordPress abilities organized across 9 domains<\/li>\n<li>MCP protocol v2025-06-18 with SSE transport<\/li>\n<li>Admin dashboard with API key generation<\/li>\n<li>Config export for Claude Code, Claude Desktop, and Cursor<\/li>\n<li>Conflict detection for legacy MCP plugins<\/li>\n<\/ul>\n\n<h3>Credits<\/h3>\n\n<p>Shim MCP builds its MCP protocol layer on two GPL-2.0 projects published by the WordPress project:<\/p>\n\n<ul>\n<li><a href=\"https:\/\/github.com\/WordPress\/mcp-adapter\">WordPress MCP Adapter<\/a> - everything under <code>includes\/Server\/<\/code> (transport, JSON-RPC routing, session management, tools\/resources\/prompts handlers, schema transformation, error and observability infrastructure) is derived from it.<\/li>\n<li><a href=\"https:\/\/github.com\/WordPress\/abilities-api\">WordPress Abilities API<\/a> - every ability is registered through this core API, which WordPress ships from 6.9.<\/li>\n<\/ul>\n\n<p>The 56 abilities, the admin dashboard, the WP-CLI stdio bridge and the packaging are original to this plugin. Full breakdown in CREDITS.md.<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Upload the plugin zip file via Plugins &gt; Add New &gt; Upload Plugin, or clone the repository into <code>wp-content\/plugins\/shim-mcp\/<\/code>.<\/li>\n<li>Activate the plugin through the Plugins menu.<\/li>\n<li>Go to Tools &gt; Shim MCP, generate an API key, and copy the config snippet into your AI client.<\/li>\n<\/ol>\n\n<!--section=faq-->\n<dl>\n<dt id=\"what%20is%20mcp%3F\"><h3>What is MCP?<\/h3><\/dt>\n<dd><p>MCP (Model Context Protocol) is an open standard that allows AI clients like Claude to interact with external systems through a structured protocol. It defines how AI tools discover and use capabilities (called \"abilities\" in WordPress) provided by a server.<\/p><\/dd>\n<dt id=\"do%20i%20need%20mcp%20adapter%20or%20the%20abilities%20api%20installed%20alongside%20this%3F\"><h3>Do I need MCP Adapter or the Abilities API installed alongside this?<\/h3><\/dt>\n<dd><p>No. Shim MCP is self-contained: it bundles its own MCP server, and the Abilities API it registers against is part of WordPress from 6.9 onwards. Nothing else is required.<\/p><\/dd>\n<dt id=\"can%20it%20edit%20wp-config.php%3F\"><h3>Can it edit wp-config.php?<\/h3><\/dt>\n<dd><p>Only if you let it. The ability that rewrites the WP_DEBUG constants is switched off until you add <code>define( 'SHIM_MCP_ALLOW_CONFIG_WRITES', true );<\/code> to wp-config.php yourself. Without that line the ability refuses, and it is refused again if DISALLOW_FILE_EDIT or DISALLOW_FILE_MODS is set, if the file is not writable, or if the rewritten contents fail a sanity check.<\/p><\/dd>\n<dt id=\"it%20warns%20me%20about%20another%20mcp%20plugin.%20why%3F\"><h3>It warns me about another MCP plugin. Why?<\/h3><\/dt>\n<dd><p>Two MCP server plugins running at once can register competing abilities and endpoints, which produces confusing results for the connected AI client. If Shim MCP detects another MCP server or a standalone Abilities API plugin, it shows a notice suggesting you run only one. This is a compatibility warning, not a judgement about the other plugin.<\/p><\/dd>\n<dt id=\"what%20ai%20clients%20are%20supported%3F\"><h3>What AI clients are supported?<\/h3><\/dt>\n<dd><p>Any MCP-compatible client works. The admin dashboard provides ready-made config snippets for Claude Code, Claude Desktop, and Cursor.<\/p><\/dd>\n<dt id=\"do%20i%20need%20https%3F\"><h3>Do I need HTTPS?<\/h3><\/dt>\n<dd><p>HTTPS is strongly recommended for production use since API credentials are transmitted with each request. The plugin will work over HTTP for local development.<\/p><\/dd>\n<dt id=\"what%20wordpress%20capabilities%20are%20required%3F\"><h3>What WordPress capabilities are required?<\/h3><\/dt>\n<dd><p>Different abilities require different WordPress capabilities. For example, content abilities require <code>edit_posts<\/code>, user abilities require <code>list_users<\/code> or <code>edit_users<\/code>, and system abilities require <code>manage_options<\/code>. See the full abilities reference in docs\/ABILITIES.md.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>1.0.2<\/h4>\n\n<ul>\n<li>The dashboard's endpoint probe is labelled and reported honestly: it confirms the REST route is reachable and protected, not that an exported client configuration can authenticate. A 401 or 403 response is never shown as \"Connected\".<\/li>\n<\/ul>\n\n<h4>1.0.1<\/h4>\n\n<ul>\n<li>Option abilities refuse to read or write options whose names look like stored credentials, and the option-name search no longer returns values at all<\/li>\n<li>Core admin files are loaded only where a function from them is used<\/li>\n<li>Removed the redirect to the settings page after activation<\/li>\n<\/ul>\n\n<h4>1.0.0<\/h4>\n\n<ul>\n<li>Initial release with 56 WordPress abilities<\/li>\n<li>Admin dashboard with API key generation<\/li>\n<li>Config export for Claude Code, Claude Desktop, Cursor<\/li>\n<li>Conflict detection for legacy MCP plugins<\/li>\n<li>SSE transport with MCP protocol v2025-06-18<\/li>\n<\/ul>","raw_excerpt":"Connect WordPress to AI in one click. Full MCP server with 56 abilities.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/362342","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=362342"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/justadityaraj"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=362342"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=362342"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=362342"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=362342"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=362342"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=362342"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}