NIBWP – WordPress 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-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.