| 开发者 | nibwp |
|---|---|
| 更新时间 | 2026年6月21日 20:24 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
wordpress/mcp-adapter, so it stays lightweight and future‑proof instead of shipping a proprietary protocol layer.
Authentication uses WordPress core Application Passwords (HTTP Basic) — the same standard the REST API already trusts. Every credential is created, listed, and revoked from your dashboard. There is no separate API key to manage, no account to create, and no subscription.
Why NIBWP
nibwp folder to /wp-content/plugins/.The Model Context Protocol 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, 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.
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.
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.
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.
No — it builds on it. WordPress 6.9 introduced the Abilities API for registering AI‑callable functions, and wordpress/mcp-adapter bridges those abilities to the MCP protocol. NIBWP adds a curated, capability‑checked ability set, Application‑Password authentication, a master on/off switch, an option allowlist, a memory store, and a one‑paste Connect flow on top of that foundation.
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.
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.
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.
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. 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.
wordpress/mcp-adapter.