Introducing NIBWP

For years, connecting AI to a WordPress site meant brittle scrapers, one-off scripts, and custom REST endpoints that broke on the next update. We wanted something durable instead: a stable contract between your content and any agent. That is what NIBWP is.

A protocol, not a plugin trick

NIBWP turns any WordPress install into a Model Context Protocol (MCP) server. Your posts, pages, custom fields, taxonomies, and store data become typed tools that any MCP client can discover and call. There is no middleware, no scraping, and nothing to proxy through our servers. The endpoint lives on your own REST API, under your own permissions.

Because every capability ships a JSON schema, agents call it predictably. They know the arguments, the types, and the shape of the response before they ever run a request. That is the difference between an agent that guesses and an agent that knows.

Read, write, destructive

Every tool declares one of three classes, so you always know what it can do:

• Read — safe, side-effect-free lookups like listing posts or fetching orders.
• Write — create and update content, fields, and templates, with optional force-draft.
• Destructive — deletes and raw operations, gated behind explicit scopes and confirmations.

One endpoint. Typed tools. Every major AI client.

Built for control and trust

Least-privilege application passwords scope each agent to exactly the tools it needs. Post-type rules, rate limits, and IP allow-lists keep it inside its lane. And a full audit log records every call with status, latency, user, and IP, so you always know what happened.

Where it goes next

This is the foundation the rest of the platform builds on: typed AI Abilities, granular permissions, persistent site memory, and Pro Skills that turn a design into a real build. Read the docs to connect your first agent, or request a demo and we will walk you through it on a live site.