Docs › Connect an agent or use the API

MCP tools

What an assistant can call, and what it cannot.

The MCP server answers at https://YOUR-SITE/wp-json/mcp/wpbr with the same login as the REST API (the connection’s Application Password). Remote MCP clients that support OAuth sign-in use https://YOUR-SITE/wp-json/mcp/wpbr-oauth instead; the connection’s password does not work there.

Read

wpbr-get-capabilities, wpbr-list-sites, wpbr-list-targets, wpbr-get-target, wpbr-get-target-history, wpbr-list-runs, wpbr-get-run, wpbr-get-run-report, wpbr-get-staged-file, wpbr-get-plan

Prepare (record state, replace nothing)

wpbr-stage-attachment, wpbr-prepare-plan (needs an idempotency_key), wpbr-cancel-plan, wpbr-request-approval

Run

wpbr-execute-plan, wpbr-advance-run, wpbr-cancel-run, wpbr-rollback-run

wpbr-execute-plan is listed only while automated writes are on. wpbr-advance-run, wpbr-cancel-run and wpbr-rollback-run are always listed, because they are how an existing run is finished, stopped or undone: with writes off, advancing a run that is still replacing is refused, and cancelling or rolling back still works. Your MCP client lists the tools it can call; that list is the source of truth.

There is no tool to approve. Uploading a new file is REST only (a tool cannot carry a binary); through MCP an assistant stages a file already in the Media Library.