NIBWP – WordPress MCP Server - Connect Claude, ChatGPT, Cursor & Any AI Agent via MCP

MCP is an open standard that lets AI assistants call structured "tools" on external systems through an MCP server. Without an MCP server, you copy-paste content between WordPress and your AI by hand. NIBWP is that MCP server for WordPress: with it, Claude, Claude Code, ChatGPT, Gemini and Cursor connect over MCP and can read posts, create and update content, manage media and menus, and look up site data directly - through a secure, authenticated MCP connection.

Two things. First, NIBWP is a 100% self-hosted MCP server - there is no external MCP relay or cloud proxy, so your content never leaves your server (some alternative MCP plugins route every MCP request through their own infrastructure). Second, this MCP server is built on WordPress core - the official Abilities API plus Application Passwords - instead of a custom API-key system and a proprietary protocol layer. Every MCP call is capability-checked per object, and a master switch turns the MCP server off in one click.

No. NIBWP uses WordPress core Application Passwords 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.

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.

Open NIBWP → Connect, enable AI Abilities, and generate an Application Password. Copy the ready-made prompt (it already contains your endpoint, username and password) and paste it into Claude - it adds the MCP server itself. Claude Code users can also run the shown claude mcp add command.

Yes. Any MCP-compatible 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, with setup snippets for 15+ clients including Claude, Claude Code, ChatGPT, Gemini, Cursor, VS Code, GitHub Copilot, Windsurf, Zed, JetBrains, Neovim, Cline, Warp, Raycast and Ollama.

Introduced in WordPress 6.9, the Abilities API is the official way for plugins to register typed, AI-callable functions. The wordpress/mcp-adapter package bridges those abilities to the MCP protocol. NIBWP bundles the adapter and adds a curated, capability-checked ability set on top - keeping your site aligned with WordPress core's AI roadmap.

Security is enforced at several layers. Every ability requires authentication and passes WordPress capability checks plus per-object checks (per-post, per-term, per-user). Option access is limited to a non-sensitive 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.

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. NIBWP Pro adds dedicated, schema-typed integrations for ACF, Meta Box, Pods, JetEngine and ACPT.

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-typed control, NIBWP Pro adds dedicated integrations for 66 plugins and themes - including WooCommerce, Elementor, Bricks, Breakdance, Etch, Divi, Kadence, Voxel, ACF, Yoast SEO, Rank Math, SEOPress, LearnDash, Tutor LMS, MemberPress, ten form plugins and Automatic.css. See https://nibwp.com/integrations.

Pro Skills are premium, builder-aware skill packs that turn a screenshot, URL, HTML or Figma frame into a validated, on-system build - Bricks, Elementor, EtchWP, Kadence, Breakdance, Voxel, Automatic.css and Figma - plus full course generation for Tutor LMS. They are part of NIBWP Pro; see https://nibwp.com/solutions.

A Workflow is a structured playbook NIBWP injects into the agent as mandatory instructions rather than suggestions: when to use it, the standards to hold, the ordered steps, the hard constraints, the validation checks, and the report to hand back. 18 default playbooks ship across nine categories. A workflow can stay private to one site or be shared across every site on your license, so the same method runs on site one and site one hundred. Workflows are part of NIBWP Pro.

AI Jobs run real site maintenance from inside wp-admin: you state the outcome, NIBWP plans the work, asks for approval before changing anything, and returns a plain-English report. Broken-link crawls, security scans, update checks and database cleanup are available today, on a manual, daily or weekly schedule. AI Jobs are part of NIBWP Pro.

Agent View is a browser workspace where an agent opens and drives the real, rendered pages of your site while you watch - clicking elements, filling fields, resizing the viewport, auditing accessibility and reading console errors, with a selector for every element. Every change stops for approval by default. It is part of NIBWP Pro.

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-facing pages or normal admin screens.

Yes. The connection happens on the client side, so any local MCP-compatible runner such as Ollama or LM Studio can talk to your site. Your data stays on your own infrastructure.

Yes, per site. Activate it on each subsite; every site gets its own endpoint, credentials and settings.

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.