Docs · getting-started

Quickstart — connect your first AI client

Install NIBWP, generate an Application Password, paste both into Claude / Cursor / Claude Code, run /mcp.

Connect your first AI client to WordPress in about three minutes. By the end of this guide an agent like Claude Code, Cursor, or Claude Desktop can read, search, and act on your site through one secure endpoint — running entirely on your own server.

In short

Install NIBWP, create a WordPress Application Password, paste your site URL and credentials into your AI client’s MCP config, and run /mcp. Your agent is now connected to your site.

Before you begin

  • WordPress 6.0 or newer, with an administrator account.
  • The NIBWP plugin installed and activated (step 1 below).
  • An MCP-capable client: Claude Code, Cursor, Claude Desktop, or any tool that speaks the Model Context Protocol.
  • Node.js 18+ available locally — the connector runs through npx.

1. Install NIBWP

Install it like any other WordPress plugin:

  • Download the plugin .zip from your NIBWP account.
  • In WordPress, go to Plugins → Add New → Upload Plugin, choose the file, and click Install Now.
  • Click Activate. NIBWP now exposes a Model Context Protocol endpoint at https://your-site.com/wp-json/mcp/nibwp.
Self-hosted, always. NIBWP runs entirely on your own server. Nothing is proxied through a third party — your data and your credentials stay on your site.

2. Create an Application Password

Agents authenticate with a standard WordPress Application Password — never your real login password, and revocable at any time.

  • Go to Users → Profile for your own account.
  • Scroll to Application Passwords, enter a name such as NIBWP, and click Add New Application Password.
  • Copy the generated password (24 characters, with spaces).
Copy it now. WordPress shows an Application Password only once. If you lose it, just revoke it and generate a new one — no harm done.

3. Connect your AI client

Point your client at your site with the @automattic/mcp-wordpress-remote connector. Add this to your client’s MCP configuration, replacing the URL, username, and Application Password with your own:

mcp configjson
{
  "mcpServers": {
    "my-wordpress": {
      "command": "npx",
      "args": ["-y", "@automattic/mcp-wordpress-remote@latest"],
      "env": {
        "WP_API_URL": "https://your-site.com/wp-json/mcp/nibwp",
        "WP_API_USERNAME": "your-username",
        "WP_API_PASSWORD": "xxxx xxxx xxxx xxxx xxxx xxxx"
      }
    }
  }
}

Where each client keeps that config:

  • Claude Code — a .mcp.json file in your project root (or run claude mcp add).
  • CursorSettings → MCP → Add Server, or edit ~/.cursor/mcp.json.
  • Claude DesktopSettings → Developer → Edit Config (claude_desktop_config.json).

4. Run your first command

Restart your client so it loads the new server, then confirm the connection and try a read:

agent
> /mcp
my-wordpress — connected · 130+ tools available

> List my 5 most recent posts and their status.
… calling nibwp/wp-list-posts …

If the agent lists your posts, you’re connected. Now try real prompts: “Draft a post about X,” “Find SEO issues on my homepage,” or “Show my last 10 WooCommerce orders.”

Verify it works

  • /mcp lists my-wordpress as connected.
  • The agent can list posts (a read action).
  • Creating a draft post succeeds (a write action).
Stay in control. Every ability is typed and permissioned. Decide exactly what agents may do under NIBWP → Permissions, and review every call in the audit log.

Troubleshooting

I get a 401 / authentication error
Check that WP_API_USERNAME is your WordPress username (not your email), and that the Application Password was pasted with its spaces. Regenerate it under Users → Profile if you’re unsure.
The endpoint returns 404
Confirm NIBWP is active and that WP_API_URL ends with /wp-json/mcp/nibwp. If permalinks are set to “Plain,” switch to “Post name” under Settings → Permalinks and save.
My client doesn’t see the server
Fully restart the client after editing the config, and make sure Node.js 18+ is installed so npx can fetch the connector.
The agent can read but not write
That’s the permission system doing its job. Open NIBWP → Permissions and enable the write or destructive abilities you want to allow.

You’re connected. Now go build.

See everything your agent can do, or follow a real-world walkthrough end to end.

Browse AI abilities →   All documentation

Connect your first agent.

Follow the quickstart, or book a demo and we'll walk you through it.