=== NIBWP – WordPress MCP Server for Claude & AI Agents ===
Contributors: nibwp
Tags: mcp, mcp-server, claude, claude-code, ai
Requires at least: 6.9
Tested up to: 7.0
Requires PHP: 8.0
Stable tag: 1.0.0
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Self‑hosted WordPress MCP server for Claude, Claude Code, ChatGPT & AI agents. Built on the official Abilities API — no relay, no account.

== Description ==

**NIBWP is the self‑hosted WordPress MCP server.** It turns your 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 through one standard, authenticated endpoint — no copy‑pasting, no scraping, and **no external relay touching your data**.

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** and is built directly on the WordPress 6.9 **Abilities API** and the official `wordpress/mcp-adapter`, so it stays lightweight and aligned with WordPress core instead of shipping a proprietary protocol layer.

= 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 all AI abilities on or off for the whole site.
* **One‑paste setup.** The Connect screen generates a ready‑made prompt you paste into your AI — it connects itself.

= What your AI can do =

* 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, Claude Code & 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.
* **Cursor / Windsurf / VS Code** — add the endpoint as an MCP tool server in your editor and query or update WordPress data without leaving your IDE.
* **ChatGPT, Gemini & any MCP client** — any client that speaks the Model Context Protocol over an authenticated HTTP endpoint connects: Claude (Anthropic), OpenAI / ChatGPT, Google Gemini, Cursor, VS Code, Windsurf, Cline and Zed.

= 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**.

= Premium integrations (NIBWP Pro) =

The free plugin is fully functional on its own. **NIBWP Pro** turns **30+ popular WordPress plugins** into AI‑callable, schema‑typed MCP tools — no glue code. Activate an integration and your agents read and write it through clean, typed calls:

* **WooCommerce** — read and manage products, variations, orders and store data.
* **SEO** — Yoast SEO, Rank Math, SEOPress, Slim SEO.
* **Page builders** — Elementor, Bricks, Etch, Divi.
* **Custom fields** — Advanced Custom Fields (ACF), Meta Box, Pods, JetEngine.
* **Forms** — Contact Form 7, Fluent Forms, Gravity Forms.
* **CRM, email & community** — FluentCRM, FluentSMTP, FluentCommunity, BuddyPress.
* **LMS & membership** — LearnDash, LifterLMS, Tutor LMS, MemberPress.
* **Commerce & donations** — SureCart, FluentCart, Easy Digital Downloads, GiveWP.
* **Design systems & themes** — Automatic.css (ACSS), GeneratePress, Kadence.
* **More** — The Events Calendar, TablePress, TranslatePress, WPML, Redirection.

Browse the full directory at https://nibwp.com/integrations

= Pro Skills — design in, validated build out =

**NIBWP Pro Skills** teach agents a specific builder or framework so the output is correct, on‑system and production‑ready — not a guess. Turn a **screenshot, URL or Figma frame** into a validated build:

* **Bricks Pro** — screenshots, URLs, images or Figma → validated Bricks templates.
* **Elementor Pro** — HTML, URL or image → a validated Elementor widget tree with global classes and dynamic tags.
* **EtchWP Pro** — HTML, URL, image or Figma → validated EtchWP components with BEM + ACSS tokens.
* **ACSS Pro** — generate a working Automatic.css configuration from a screenshot, HTML/CSS or live URL.
* **Tutor LMS Builder** — turn a brief, outline or URL into a complete, validated Tutor LMS course.

Common use cases: **content automation** (draft, summarize and update posts), **SEO at scale** (audit and bulk‑optimize through typed tools) and **WooCommerce ops** (read and manage products and orders).

Explore Pro Skills at https://nibwp.com/solutions

Premium integrations and Pro Skills are part of **NIBWP Pro**, a paid upgrade available at https://nibwp.com — they are not included in this free plugin.

== Installation ==

1. Install through the WordPress.org plugin directory, or upload the `nibwp` folder to `/wp-content/plugins/`.
2. Activate the plugin.
3. Open the **NIBWP → Connect** screen.
4. Turn on **AI Abilities**, generate an **Application Password**, and copy the ready‑made connection prompt.
5. Paste the prompt into Claude, Claude Code, ChatGPT, Gemini or Cursor — it connects itself.

== Frequently Asked Questions ==

= What is the Model Context Protocol (MCP)? =

MCP is an open standard that lets AI assistants call structured "tools" on external systems. Without it, you copy‑paste 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 — through a secure, authenticated connection.

= How is NIBWP different from other WordPress MCP plugins? =

Two things. First, NIBWP is **100% self‑hosted** — 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** — the official Abilities API plus Application Passwords — instead of a custom API‑key system and a proprietary protocol layer. Access is capability‑checked per object, and a master switch turns everything 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 add` command.

= Does it work with Cursor, VS Code, Windsurf, ChatGPT or Gemini? =

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.

= 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-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.

= 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.

= 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 30+ plugins — 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.

= What are Pro Skills? =

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

= 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.

== Screenshots ==

1. The NIBWP Connect screen — enable AI Abilities, generate an Application Password, and copy the ready‑made connection prompt.
2. Dashboard — 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.

== Changelog ==

= 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.

== Upgrade Notice ==

= 1.0.0 =
First public release.
