NIBWP – Self-Hosted MCP Server – Connect Claude, ChatGPT, Cursor & Any AI Agent via MCP
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-pas
About this tool.
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.