Before you connect an AI agent to your WordPress site, it is worth spending five minutes understanding what you are about to do — because what you are about to do is genuinely powerful. NIBWP turns your site into a server that AI agents can read from and write to. Used well, that is a superpower: agents that build, fix and maintain your site on command. Used carelessly, it is a foot-gun. This article is the “before knowledge” — the requirements, the mental model, and the safety basics — so that everything you do afterwards is deliberate.
NIBWP exposes WordPress to AI agents as typed tools over a secure endpoint. Before you start you need WordPress over HTTPS, admin access, and an MCP client. Understand three ideas — tools, scopes and the audit log — and adopt three habits — least-privilege tokens, force-draft, and backups — and you will use it safely and confidently.
What NIBWP actually is
NIBWP is a Model Context Protocol (MCP) server that lives inside WordPress. MCP is an open standard for connecting AI applications to tools and data. Instead of an agent scraping your site or you writing custom integration code, NIBWP advertises a set of tools — typed operations like “search posts” or “create product” — that an agent can call over one authenticated HTTPS endpoint. The agent decides what to do; NIBWP validates, authorizes, executes and logs every call.
What you need
Five things. Most you already have:
- A WordPress site — a recent version, self-hosted or managed.
- HTTPS — the endpoint must be served over TLS. Cloud-based AI clients (Claude, Cursor) reach your site from the internet, so it must be publicly reachable over HTTPS. Claude Code, running locally, can also reach a localhost or staging site.
- Admin access — to install NIBWP and generate tokens.
- An MCP client — Claude Code, Claude Desktop, Cursor, or any tool that speaks MCP. This is the “agent” side.
- A few minutes — from install to first call is about five.
The mental model: three ideas
Everything in NIBWP rests on three concepts. Understand these and the rest is obvious.
1. Tools (abilities)
A tool is a single typed operation — nibwp/wp-create-post, nibwp/wp-search. Each is self-describing: the agent knows its inputs and outputs without you wiring anything. NIBWP calls these abilities, and ships 30+ of them out of the box, plus more from each active plugin integration.
2. Scopes
A scope is what a token is allowed to do. Tokens carry scopes — read, write, publish, admin — and an agent can only call abilities its token permits. This is your primary safety lever: give an agent the least it needs.
3. The audit log
Every call is recorded — which tool, which token, the arguments, the result, the timing. Nothing an agent does is invisible. The audit log is your accountability and your debugging tool in one.
Three habits that keep you safe
You do not need to be paranoid — you need three habits:
| Habit | Why it matters |
|---|---|
| Least-privilege tokens | Give each agent the smallest scope that does the job. A research agent gets read; a content agent gets write, not publish. |
| Force-draft on | Make AI writes land as drafts a human approves. The agent proposes; you dispose. |
| Backups | A recent backup turns any mistake into an inconvenience. Standard practice, doubly wise with agents. |
Your first ten minutes
Install on staging
Put NIBWP on a development or staging site first. Activate it to publish the MCP endpoint.
Generate a read token
Create an application password scoped to read. Start by letting the agent look, not touch.
Connect a client
Use the config generator to connect Claude, Cursor or Claude Code. See the next guides for each.
Ask it to read
“List my recent posts.” Watch the call appear in the audit log. You are live — safely.
Graduate to write
When you are comfortable, issue a write token with force-draft on, and let the agent draft.
What can go wrong (and how it is prevented)
- An agent changes something unexpected — prevented by scopes and force-draft; everything is a reviewable draft.
- A runaway loop hammers the database — prevented by per-token rate limits.
- You cannot tell what happened — prevented by the audit log; every call is recorded.
- A leaked token — contained by per-client tokens you can revoke individually.
FAQ
Do I need to know how to code?
Is it safe to run on a live site?
Does it work on shared hosting?
What is the difference between read, write and publish?
Ready to begin?
Install NIBWP, generate your first token, and connect a client — the next guides walk you through each.
Get NIBWP