NIBWP

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

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, 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)

Read the full description on the official page →