First public release.<\/p>"},"ratings":[],"assets_icons":{"icon-256x256.png":{"filename":"icon-256x256.png","revision":3578835,"resolution":"256x256","location":"assets","locale":"","width":512,"height":512},"icon-512x512.png":{"filename":"icon-512x512.png","revision":3578835,"resolution":"512x512","location":"assets","locale":"","width":512,"height":512}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3580648,"resolution":"1544x500","location":"assets","locale":"","width":3088,"height":1000},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3580648,"resolution":"772x250","location":"assets","locale":"","width":3088,"height":1000}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3578835,"resolution":"1","location":"assets","locale":"","width":980,"height":501},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3578835,"resolution":"2","location":"assets","locale":"","width":1242,"height":509},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3578835,"resolution":"3","location":"assets","locale":"","width":966,"height":550},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3578835,"resolution":"4","location":"assets","locale":"","width":1250,"height":609}},"screenshots":{"1":"The NIBWP Connect screen \u2014 enable AI Abilities, generate an Application Password, and copy the ready\u2011made connection prompt.","2":"Dashboard \u2014 exposed abilities, memory entries and the live REST endpoint.","3":"Claude Desktop connected to NIBWP, reading and updating posts over MCP.","4":"Claude Code wired to NIBWP as a remote MCP server during an agentic build."}},"plugin_section":[],"plugin_tags":[2353,229563,263572,242115,260626],"plugin_category":[],"plugin_contributors":[267930],"plugin_business_model":[],"class_list":["post-327075","plugin","type-plugin","status-publish","hentry","plugin_tags-ai","plugin_tags-claude","plugin_tags-claude-code","plugin_tags-mcp","plugin_tags-mcp-server","plugin_contributors-nibwp","plugin_committers-nibwp"],"banners":{"banner":"https:\/\/ps.w.org\/nibwp\/assets\/banner-772x250.png?rev=3580648","banner_2x":"https:\/\/ps.w.org\/nibwp\/assets\/banner-1544x500.png?rev=3580648","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/nibwp\/assets\/icon-256x256.png?rev=3578835","icon_2x":"https:\/\/ps.w.org\/nibwp\/assets\/icon-256x256.png?rev=3578835","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/nibwp\/assets\/screenshot-1.png?rev=3578835","caption":"The NIBWP Connect screen \u2014 enable AI Abilities, generate an Application Password, and copy the ready\u2011made connection prompt."},{"src":"https:\/\/ps.w.org\/nibwp\/assets\/screenshot-2.png?rev=3578835","caption":"Dashboard \u2014 exposed abilities, memory entries and the live REST endpoint."},{"src":"https:\/\/ps.w.org\/nibwp\/assets\/screenshot-3.png?rev=3578835","caption":"Claude Desktop connected to NIBWP, reading and updating posts over MCP."},{"src":"https:\/\/ps.w.org\/nibwp\/assets\/screenshot-4.png?rev=3578835","caption":"Claude Code wired to NIBWP as a remote MCP server during an agentic build."}],"raw_content":"\n
NIBWP is the self\u2011hosted WordPress MCP server.<\/strong> It turns your site into a Model Context Protocol (MCP) server<\/strong> so AI assistants like Claude, Claude Code, ChatGPT, Google Gemini and Cursor<\/strong> can read and manage your content through one standard, authenticated endpoint \u2014 no copy\u2011pasting, no scraping, and no external relay touching your data<\/strong>.<\/p>\n\n Every request runs inside your own WordPress install: there is no cloud proxy, no account and no separate API key. NIBWP authenticates with WordPress core Application Passwords<\/strong> and is built directly on the WordPress 6.9 Abilities API<\/strong> and the official WordPress 6.9 shipped the Abilities API<\/strong> \u2014 the official mechanism for plugins to register typed, AI\u2011callable functions. NIBWP bundles the official Some WordPress MCP plugins route every request through their own cloud servers \u2014 your content leaves your site. Others bolt on a custom API\u2011key system and a large proprietary tool set. NIBWP takes the opposite approach: 100% self\u2011hosted<\/strong> (no external relay), built on WordPress core<\/strong> (Abilities API + Application Passwords), with a focused, capability\u2011checked ability set \u2014 free, no account, no external calls<\/strong>.<\/p>\n\n The free plugin is fully functional on its own. NIBWP Pro<\/strong> turns 30+ popular WordPress plugins<\/strong> into AI\u2011callable, schema\u2011typed MCP tools \u2014 no glue code. Activate an integration and your agents read and write it through clean, typed calls:<\/p>\n\n Browse the full directory at https:\/\/nibwp.com\/integrations<\/p>\n\n NIBWP Pro Skills<\/strong> teach agents a specific builder or framework so the output is correct, on\u2011system and production\u2011ready \u2014 not a guess. Turn a screenshot, URL or Figma frame<\/strong> into a validated build:<\/p>\n\n Common use cases: content automation<\/strong> (draft, summarize and update posts), SEO at scale<\/strong> (audit and bulk\u2011optimize through typed tools) and WooCommerce ops<\/strong> (read and manage products and orders).<\/p>\n\n Explore Pro Skills at https:\/\/nibwp.com\/solutions<\/p>\n\n Premium integrations and Pro Skills are part of NIBWP Pro<\/strong>, a paid upgrade available at https:\/\/nibwp.com \u2014 they are not included in this free plugin.<\/p>\n\n\n MCP is an open standard that lets AI assistants call structured \"tools\" on external systems. Without it, you copy\u2011paste content between WordPress and your AI by hand. With NIBWP, Claude, Claude Code, ChatGPT, Gemini and Cursor can read posts, create and update content, manage media and menus, and look up site data directly \u2014 through a secure, authenticated connection.<\/p><\/dd>\n Two things. First, NIBWP is 100% self\u2011hosted<\/strong> \u2014 there is no external relay or cloud proxy, so your content never leaves your server (some alternatives route every MCP request through their own infrastructure). Second, it is built on WordPress core<\/strong> \u2014 the official Abilities API plus Application Passwords \u2014 instead of a custom API\u2011key system and a proprietary protocol layer. Access is capability\u2011checked per object, and a master switch turns everything off in one click.<\/p><\/dd>\n No. NIBWP uses WordPress core Application Passwords<\/strong> for authentication. You generate one on the Connect screen, paste it into your AI client, and revoke it whenever you like. There is no separate API key, no account, and no subscription.<\/p><\/dd>\n No. NIBWP is pure PHP and runs inside your existing WordPress install on any standard host. There is no Node.js requirement, no cloud relay, and no external service dependency.<\/p><\/dd>\n Open NIBWP \u2192 Connect<\/strong>, enable AI Abilities, and generate an Application Password. Copy the ready\u2011made prompt (it already contains your endpoint, username and password) and paste it into Claude \u2014 it adds the MCP server itself. Claude Code users can also run the shown Yes. Any MCP\u2011compatible client can connect using the site's MCP endpoint and an Application Password sent as HTTP Basic auth. The Connect screen shows the exact endpoint and credentials.<\/p><\/dd>\n Introduced in WordPress 6.9, the Abilities API is the official way for plugins to register typed, AI\u2011callable functions. The Security is enforced at several layers. Every ability requires authentication and passes WordPress capability checks plus per\u2011object checks (per\u2011post, per\u2011term, per\u2011user). Option access is limited to a non\u2011sensitive allowlist, and sensitive option and meta values (passwords, secrets, API keys, auth salts, session tokens, capabilities) are filtered out. Comment creation respects your moderation and \"comments open\" settings. A master switch disables every ability for the whole site in one click.<\/p><\/dd>\n Yes. NIBWP exposes post, term and user meta abilities. Because those plugins store data as standard WordPress meta, an AI agent can read and write their fields the same way a human editor would.<\/p><\/dd>\n The free plugin reads and writes any post type and meta, so it already covers products, custom fields and most builder content generically. For deeper, schema\u2011typed control, NIBWP Pro<\/strong> adds dedicated integrations for 30+ plugins \u2014 including WooCommerce, Elementor, Bricks, Etch, Divi, ACF, Yoast SEO, Rank Math, SEOPress, LearnDash, Tutor LMS, MemberPress, Fluent Forms, Gravity Forms and Automatic.css. See https:\/\/nibwp.com\/integrations.<\/p><\/dd>\n Pro Skills are premium skill packs that turn a screenshot, URL or Figma frame into a validated, on\u2011system build for a specific builder \u2014 Bricks, Elementor, EtchWP and Automatic.css \u2014 plus full course generation for Tutor LMS. They are part of NIBWP Pro; see https:\/\/nibwp.com\/solutions.<\/p><\/dd>\n No. The MCP endpoint is a REST route that only runs when an authenticated AI client makes a request. It does not execute on visitor\u2011facing pages or normal admin screens.<\/p><\/dd>\n Yes. The connection happens on the client side, so any local MCP\u2011compatible runner such as Ollama or LM Studio can talk to your site. Your data stays on your own infrastructure.<\/p><\/dd>\n Yes, per site. Activate it on each subsite; every site gets its own endpoint, credentials and settings.<\/p><\/dd>\n The master switch stops NIBWP from registering any abilities, so the site exposes nothing over MCP until you turn it back on. Existing Application Passwords are left untouched.<\/p><\/dd>\n\n<\/dl>\n\n\nwordpress\/mcp-adapter<\/code>, so it stays lightweight and aligned with WordPress core instead of shipping a proprietary protocol layer.<\/p>\n\nWhy NIBWP<\/h4>\n\n
\n
What your AI can do<\/h4>\n\n
\n
Works with Claude, Claude Code & any MCP client<\/h4>\n\n
\n
Built on the official WordPress Abilities API<\/h4>\n\n
wordpress\/mcp-adapter<\/code> and exposes your site through it, so your install is MCP\u2011ready in a way that stays aligned with WordPress core's AI roadmap \u2014 no proprietary, soon\u2011to\u2011diverge protocol layer.<\/p>\n\nHow it compares<\/h4>\n\n
Premium integrations (NIBWP Pro)<\/h4>\n\n
\n
Pro Skills \u2014 design in, validated build out<\/h4>\n\n
\n
\n
nibwp<\/code> folder to \/wp-content\/plugins\/<\/code>.<\/li>\n\n
What is the Model Context Protocol (MCP)?<\/h3><\/dt>\n
How is NIBWP different from other WordPress MCP plugins?<\/h3><\/dt>\n
Do I need an API key or an account?<\/h3><\/dt>\n
Does NIBWP require Node.js, a proxy or a cloud service?<\/h3><\/dt>\n
How do I connect Claude Desktop or Claude Code?<\/h3><\/dt>\n
claude mcp add<\/code> command.<\/p><\/dd>\nDoes it work with Cursor, VS Code, Windsurf, ChatGPT or Gemini?<\/h3><\/dt>\n
What is the WordPress Abilities API?<\/h3><\/dt>\n
wordpress\/mcp-adapter<\/code> package bridges those abilities to the MCP protocol. NIBWP bundles the adapter and adds a curated, capability\u2011checked ability set on top \u2014 keeping your site aligned with WordPress core's AI roadmap.<\/p><\/dd>\nIs my site safe?<\/h3><\/dt>\n
Can AI read and write my custom fields (ACF, Meta Box, Pods, JetEngine)?<\/h3><\/dt>\n
Does NIBWP work with WooCommerce, Elementor, Bricks, Yoast or Rank Math?<\/h3><\/dt>\n
What are Pro Skills?<\/h3><\/dt>\n
Will it slow down my site?<\/h3><\/dt>\n
Can I use local AI models (Ollama, LM Studio)?<\/h3><\/dt>\n
Does it work on multisite?<\/h3><\/dt>\n
What happens when I turn AI Abilities off?<\/h3><\/dt>\n
1.0.0<\/h4>\n\n
\n
wordpress\/mcp-adapter<\/code>.<\/li>\n