Tools reference
The MCP server registers 84 tools, all named wp_*. Here they are grouped by job, with the scope each group needs. For every tool’s parameters and an example call, open the full catalogue.
On this page
How tools reach your site
Your assistant never sees WordPress directly. It calls a tool such as wp_set_seo on the MCP server; the server turns that into one HTTPS request to the plugin’s REST API under /wp-json/wpcb/v1, signed with your token. The plugin checks the token’s scopes and the WordPress capability of the user it belongs to, runs the change, and writes an audit log entry.
In Claude Code a tool shows up as mcp__<server name>__wp_set_seo, where the server name is whatever you called the site when you added it. The assistant picks the right one when you name the site in your prompt.
A tool only works when the token has its scope. Read tools need …:read; anything that changes the site needs the matching write scope. See Token scopes.
Posts and pages
Read, write and publish content. Writes save a WordPress revision first; a post created with status “publish” stays a draft unless the token has content:publish.
Categories and tags
List terms of any taxonomy and create new ones.
Media
List the library, upload from a URL or base64, set alt text, captions and descriptions, optimise images, find files nothing uses, delete with confirmation.
SEO
Read and write SEO meta in the fields your SEO plugin already uses, analyse a post, audit many at once, check the sitemap, find broken links.
Analytics
Read traffic from the site’s analytics plugin: overview, top posts, keywords, referrers, a single post, period comparison, trends by category, pages without traffic.
Multilingual
Languages, post and media translations, string translation audits. Works with WPML; on sites without a supported multilingual plugin these tools report no languages.
Theme and appearance
The active theme and its files, custom CSS, theme switching, menus, widgets and the Customizer. Theme file writes keep the previous version.
Plugins
List plugins with their available updates, install from the WordPress.org directory, a zip URL or a local zip of up to 20 MB (with confirmation), activate, deactivate, read and write plugin files, scaffold a new plugin.
Files
List, read, search and download files; write, upload, create folders, rename and delete. Since plugin 1.7.0, site:write changes files only inside the uploads folder (inert types only); anywhere else needs fs:admin as well, and every overwrite, rename or delete there asks for confirmation. Secrets such as wp-config.php and .env are never read or changed. All file tools need an administrator account.
Site and system
Settings (changing the site address or admin email asks for confirmation), health and performance checks, full backups and restore.
Advanced
SQL through a guard that allows only SELECT by default and confirms every write, and WP-CLI limited to an allowlist and disabled until the site owner turns it on.
What is not a tool
Some of the plugin’s REST routes have no MCP tool, because Xaflo Desktop uses them directly: maintenance mode (/maintenance), the debug.log console (/debug/log), the audit log and token management. The one-time wp-admin sign-in link (/admin/login-link) is left out on purpose: it is a credential for a person, not for a model. All routes are in the REST API reference.