Description
NIBWP is the self-hosted WordPress MCP server. It turns your WordPress site into a Model Context Protocol (MCP) server so AI assistants like Claude, Claude Code, ChatGPT, Google Gemini and Cursor can read and manage your content over MCP through one standard, authenticated MCP endpoint – no copy-pasting, no scraping, and no external MCP relay touching your data. Every WordPress action is exposed as an MCP tool your MCP client calls directly.
Every MCP request runs inside your own WordPress install: there is no cloud MCP proxy, no account and no separate API key. NIBWP authenticates each MCP call with WordPress core Application Passwords and is built directly on the WordPress 6.9 Abilities API and the official wordpress/mcp-adapter, which maps your site’s abilities to MCP tools – so the MCP server stays lightweight and aligned with WordPress core instead of shipping a proprietary protocol layer.
A true MCP server for WordPress
NIBWP is a native MCP server: it speaks the Model Context Protocol directly, so any MCP client connects to the same MCP endpoint and calls the same MCP tools. Because the MCP server runs on your own host, every MCP request and MCP response stays on your infrastructure – no third-party MCP gateway, no MCP relay, and no data leaving your WordPress site. Point your MCP client at the WordPress MCP endpoint, authenticate with an Application Password, and start issuing MCP calls. Whether you run one WordPress MCP server or many, each site is an independent MCP endpoint you fully control.
Why NIBWP
- Self-hosted – your data never leaves your server. No cloud relay, no proxy. Every MCP call is a direct, authenticated REST request to your own site.
- Standard, revocable auth. Uses core Application Passwords – generate one per AI client, revoke it any time from the Connect screen. No separate API key, no account, no subscription.
- Permissioned by design. Every ability runs through WordPress capability checks and per-object checks (per-post, per-term, per-user), so an AI agent can only do what the connected account is allowed to do.
- Safe options & meta. Option reading/writing is restricted to a non-sensitive allowlist; passwords, secrets, API keys, auth salts and capability/session meta are filtered out and can never leak.
- Master switch. A single toggle turns the whole MCP tool set on or off – enable or disable the MCP server for the entire site in one click.
- One-paste setup. The Connect screen generates a ready-made MCP connection prompt you paste into your AI – it adds the MCP server itself.
What your AI can do over MCP (free plugin)
Once your MCP client is connected, NIBWP exposes these WordPress capabilities as MCP tools:
- Read and write posts, pages and custom post types (create, update, delete, search).
- Manage categories, tags and custom taxonomy terms.
- Work with media, comments, navigation menus and users.
- Read and write post, term and user meta – including custom fields (ACF, Meta Box, Pods, JetEngine), since they are stored as standard meta.
- Read site info and statistics and allow-listed WordPress options.
- Use a per-site key/value memory store so the assistant can remember context across calls.
- Perform allow-listed, read-only filesystem and directory lookups scoped to your WordPress install.
Works with Claude, ChatGPT, Cursor & any MCP client
- Claude Desktop – add the MCP endpoint shown on the Connect screen and ask Claude to read, draft and update your posts, media, menus and memory store through conversation.
- Claude Code – wire NIBWP into your Claude Code session and let your AI read and write the live site as part of an agentic build workflow – ideal for agencies and developers working on real WordPress installs.
- ChatGPT & Google Gemini – connect the MCP endpoint as a custom connector and work with your site from the assistant you already pay for.
- Cursor, VS Code, Windsurf, Zed, JetBrains, Neovim – add the endpoint as an MCP tool server in your editor and query or update WordPress data without leaving your IDE.
- Any MCP client – GitHub Copilot, Cline, Warp, Raycast, Perplexity, Ollama and LM Studio all connect over the same authenticated HTTP MCP endpoint. 15+ clients are supported with copy-paste setup.
Built on the official WordPress Abilities API
WordPress 6.9 shipped the Abilities API – the official mechanism for plugins to register typed, AI-callable functions. NIBWP bundles the official wordpress/mcp-adapter and exposes your site through it, so your install is MCP-ready in a way that stays aligned with WordPress core’s AI roadmap – no proprietary, soon-to-diverge protocol layer.
How it compares
Some WordPress MCP plugins route every request through their own cloud servers – your content leaves your site. Others bolt on a custom API-key system and a large proprietary tool set. NIBWP takes the opposite approach: 100% self-hosted (no external relay), built on WordPress core (Abilities API + Application Passwords), with a focused, capability-checked ability set – free, no account, no external calls.
NIBWP Pro
The free plugin is fully functional on its own. NIBWP Pro – a paid upgrade at https://nibwp.com, not included in this free plugin – adds 190+ typed MCP tools across 66 integrations, plus agent tooling built for people who run real sites and real client portfolios.
- Integrations – 66 plugin and theme integrations turn WooCommerce, ACF, the page builders, forms, SEO and LMS plugins into schema-typed MCP tools, so the agent calls a plugin’s own API instead of guessing at meta keys.
- Pro Skills – builder-aware skill packs that turn a screenshot, URL, HTML or Figma frame into a validated, on-system build.
- Workflows – a structured playbook NIBWP injects as mandatory instructions: triggers, principles, ordered process steps, hard constraints, validation checks and a client-ready report. 18 default playbooks ship across nine categories (site building, SEO audits, content, WooCommerce setup, pre-launch checklists and more). Keep a workflow private to one site, share it across every site on your license, or publish it to the community Library. Define it once, run it on site one and site one hundred.
- AI Jobs – outcome-first maintenance from inside wp-admin. Pick a job from the library or describe the outcome in plain English; NIBWP plans the work, asks for approval before it changes anything, and hands back a plain-English report card you can send to a client. Jobs available today: find broken links (crawls posts and pages and reports HTTP status codes), security scan (debug exposure, file editor, default admin users, HTTPS, outdated software), check for updates, and clean up the database (revisions, spam, orphaned data). Run them manually or on a daily or weekly schedule via WP-Cron – read-only jobs run straight through, while “ask first” jobs pause in the Approvals tab with a preview of exactly what they want to do.
- Agent View – a browser tab showing the real, rendered pages of your site that a connected agent can open, read and drive, with a selector for every element. The agent clicks, fills fields, resizes the viewport to test responsive layouts, audits accessibility (contrast, alt text, labels, headings), reads console errors and manages blocks in the editor – while you watch. Anything that changes something stops for approval by default; read-only actions never do. The workspace is bound to the WordPress account that opened it and keeps the same permission scopes as every other ability, so the agent verifies visually instead of editing blind against database values.
- Figma – pull a file, page, frame or node into the agent’s working context, analyse its structure, detect which builder powers the site, and convert a frame or component into native WordPress output.
- NIBWP Design – brand-aligned page generation on your own design tokens.
- Audit Log, Status & User Access – a full log of every AI action for security review, debugging and client reporting; connection diagnostics; and per-user control over who can drive the agent.
- Safety controls – read-only safe mode, per-action permissions, force-draft, rate limits, sandboxed PHP and file operations, and granular permissions across 15+ AI clients.
- CLI – connect a site with one command, then repeat the same steps across every site in your portfolio.
Pro Skills – design in, validated build out
Skills teach an agent a specific builder or framework so the output is correct, on-system and production-ready – not a guess:
- Bricks Pro – screenshot, URL, image or Figma frame to validated Bricks templates.
- Elementor Pro – HTML, URL, image or mockup to an editable, validated Elementor widget tree with global classes and dynamic tags.
- EtchWP Pro – HTML, URL, image or Figma to validated EtchWP components with BEM + ACSS tokens.
- ACSS Pro – generate a working Automatic.css configuration from a screenshot, HTML/CSS or live URL.
- Kadence Pro – native, editable Kadence Blocks from a screenshot or HTML.
- Breakdance Pro – AI-assisted, validated Breakdance builds.
- Voxel Pro – Voxel directory and listing work driven by the agent.
- Figma Pro – build a Figma frame natively inside your page builder.
- Tutor LMS Builder – turn a brief, outline, transcript or URL into a complete, validated Tutor LMS course with topics, lessons and quizzes.
- Tutor Course Mini-site – generate a full mini-site around a Tutor LMS course.
MCP tools per plugin and theme (Pro)
Each integration registers its own set of typed MCP tools. Ability counts per plugin or theme:
- Page builders and themes – Builderius (21), Breakdance (14), Voxel (13), Bricks Builder (9), Divi (8), Elementor (7), Etch (7), Kadence (6), GeneratePress (6).
- Design systems – Figma (7), Automatic.css (4), plus the ACSS Pro (5), Bricks Pro (5), EtchWP Pro (5) and Elementor Pro skill packs.
- Custom fields – Advanced Custom Fields (8), ACPT (1), JetEngine (1), Meta Box (1), Pods (1).
- E-commerce and donations – WooCommerce (16), SureCart (9), FluentCart (5), Easy Digital Downloads (4), GiveWP (3).
- Forms – WS Form (14), Forminator (9), JetFormBuilder (9), Ninja Forms (9), Formidable Forms (8), HappyForms (7), Fluent Forms (5), Gravity Forms (5), WPForms (4), Contact Form 7 (3).
- SEO – SEO Pro Skill (14), SEOPress (9), Yoast SEO (6), Rank Math (6), SEO Advanced (6), Slim SEO (4).
- CRM, email, community and affiliates – FluentCRM (7), FluentCommunity (7), FluentSMTP (6), BuddyPress (5), FluentAffiliate (1).
- LMS and membership – Tutor LMS (7), LearnDash (6), LifterLMS (4), MemberPress (4).
- Translation – Weglot (12), TranslatePress (4), WPML (4).
- Directories, events and jobs – WP Job Manager (6), The Events Calendar (5), Directorist (1).
- Utilities – Security & Maintenance (12), Redirection (4), TablePress (3), Admin and Site Enhancements (1).
- Built-in toolkits – WordPress Core (12), Migration Toolkit (8), Notifications & SMS (8), Content Fetcher (6), Content Planner (6), Memory (4).
Browse every integration and its full tool list at https://nibwp.com/integrations – for example, the Figma integration exposes nibwp/figma-list, nibwp/figma-get, nibwp/figma-pull, nibwp/figma-pro-fetch, nibwp/figma-pro-analyze, nibwp/figma-pro-detect-builder and nibwp/figma-pro-convert.
Common Pro use cases
Content automation (briefs become drafted, interlinked, SEO-ready posts), SEO at scale (empty metas, accidental noindex and missing schema found and fixed in bulk), WooCommerce operations (supplier sheets become products with variations and pricing), Elementor-to-Bricks and Bricks-to-Etch migrations, 404 cleanup after a migration, multilingual backfill, Voxel directory builds, course creation from transcripts, and monthly care-plan reporting.
Pricing, Skills and the full integration directory: https://nibwp.com/pricing, https://nibwp.com/solutions and https://nibwp.com/integrations.
Screenshots
Installation
- Install through the WordPress.org plugin directory, or upload the
nibwpfolder to/wp-content/plugins/. - Activate the plugin.
- Open the NIBWP Connect screen.
- Turn on AI Abilities, generate an Application Password, and copy the ready-made connection prompt.
- Paste the prompt into Claude, Claude Code, ChatGPT, Gemini or Cursor – it connects itself.
FAQ
-
What is the Model Context Protocol (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.
-
How is NIBWP different from other WordPress MCP plugins?
-
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.
-
Do I need an API key or an account?
-
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.
-
Does NIBWP require Node.js, a proxy or a cloud service?
-
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.
-
How do I connect Claude Desktop or Claude Code?
-
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 addcommand. -
Does it work with ChatGPT, Gemini, Cursor, VS Code or Windsurf?
-
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.
-
What is the WordPress Abilities API?
-
Introduced in WordPress 6.9, the Abilities API is the official way for plugins to register typed, AI-callable functions. The
wordpress/mcp-adapterpackage 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. -
Is my site safe?
-
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.
-
Can AI read and write my custom fields (ACF, Meta Box, Pods, JetEngine)?
-
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.
-
Does NIBWP work with WooCommerce, Elementor, Bricks, Yoast or Rank Math?
-
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.
-
What are Pro Skills?
-
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.
-
What are Workflows?
-
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.
-
What are AI Jobs?
-
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.
-
What is Agent View?
-
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.
-
Will it slow down my site?
-
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.
-
Can I use local AI models (Ollama, LM Studio)?
-
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.
-
Does it work on multisite?
-
Yes, per site. Activate it on each subsite; every site gets its own endpoint, credentials and settings.
-
What happens when I turn AI Abilities off?
-
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.
Reviews
Contributors & Developers
“NIBWP – WordPress MCP Server – Connect Claude, ChatGPT, Cursor & Any AI Agent via MCP” is open source software. The following people have contributed to this plugin.
Contributors
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.0.2
- Documented the full NIBWP Pro feature set: Integrations, Pro Skills, Workflows, AI Jobs, Agent View, Figma, Audit Log and CLI.
- Added per-plugin and per-theme MCP tool counts across all 66 integrations.
- Expanded the supported MCP client list to 15+ clients, including ChatGPT, Gemini, Cursor, VS Code, GitHub Copilot, Windsurf, Zed and JetBrains.
- New FAQ entries covering Workflows, AI Jobs and Agent View.
1.0.1
- Added a dismissible NIBWP Pro promo in the admin (Founder Lifetime Deal, Pro Skills, Workflows, AI Jobs, Figma Studio).
- Admin UI polish: brighter styling and dark-mode refinements.
1.0.0
- First public release: self-hosted MCP server for WordPress, built on the 6.9 Abilities API and the official
wordpress/mcp-adapter. - Tested with Claude Desktop, Claude Code, Cursor, Windsurf and any MCP-compatible client.
- Read and write abilities for posts, terms, users, media, comments, menus, options, search and meta.
- Application Password authentication with in-dashboard generation and revocation.
- Per-object capability checks, option allowlist, and sensitive option/meta filtering.
- Master on/off switch, per-site key/value memory store, and allow-listed filesystem read.