// MCP TOOL REFERENCE

WORDPRESS DEVELOPER MCP SERVER TOOLS

25 tools from the WordPress Developer MCP Server MCP Server, categorised by risk level.

View the WordPress Developer MCP Server policy →

// ALL 25 WORDPRESS DEVELOPER MCP SERVER TOOLS

READ 8 tools

Read wpdev_auth_status Check Studio authentication status. Read wpdev_check_for_mcp_updates Check if a newer version of the WordPress Developer MCP Server is available. Read wpdev_fs_list_dir List files/folders inside a Studio site directory. Safe: only allows paths within the given sitePath. Read wpdev_fs_read_file Read a text file inside a Studio site directory. Safe: only allows files within the given sitePath. Has a s... Read wpdev_preview_list List Studio preview sites for a given path of the original Studio site. Read wpdev_site_list List all local WordPress Studio sites. Read wpdev_site_status Get detailed status of a Studio site including wp-admin username as adminUsername, wp-admin password as adm... Read wpdev_wpcom_site_list Fetch the authenticated user

WRITE 8 tools

Write wpdev_site_pull Pull a WordPress.com site into a local WordPress site. Requires WordPress.com authentication. Use wpdev_wpc... Write wpdev_fs_write_file Write content to a file inside a Studio site directory. Safe: only allows paths within the given sitePath. Write wpdev_preview_create Create a Studio preview site for a given path of the original Studio site. Write wpdev_preview_update Update a Studio preview site for a given original site path. Write wpdev_site_create Create a new Studio site. If the user wants an empty/test site, create only the site and stop after sharing... Write wpdev_site_design_brief Create a structured design brief before building or redesigning a WordPress site. If the request is undersp... Write wpdev_site_push Push a local WordPress site to a WordPress.com site. Requires WordPress.com authentication. Use wpdev_wpcom... Write wpdev_site_set Configure site settings.

DESTRUCTIVE 4 tools

Destructive wpdev_auth_logout Log out and clear WordPress.com authentication for Studio. Destructive wpdev_fs_delete Delete a file or folder inside a Studio site directory. Safe: only allows paths within the given sitePath. Destructive wpdev_preview_delete Delete a Studio preview site by its hostname (e.g. Destructive wpdev_site_delete Delete a Studio site. Destructive: requires confirm=true. Optionally move site files to trash.

EXECUTE 5 tools

Execute wpdev_site_start Start a Studio site. Returns site URL and admin username. Execute wpdev_site_stop Stop a Studio site or all sites. Execute wpdev_wp Run WP-CLI commands on a Studio site. Use deliberately because WP-CLI can be slower than file reads/writes.... Execute wpdev_site_inspect Inspect a local WordPress site route with a real browser. Use this after creating or changing a site to ver... Execute wpdev_update_mcp Update the WordPress Developer MCP Server to the latest version.

// FAQ

How many tools does the WordPress Developer MCP Server MCP server have? +

The WordPress Developer MCP Server MCP server exposes 25 tools across 4 categories: Read, Write, Destructive, Execute.

How do I enforce policies on WordPress Developer MCP Server tools? +

Route the WordPress Developer MCP Server server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do WordPress Developer MCP Server tools fall into? +

WordPress Developer MCP Server tools are categorised as Read (8), Write (8), Destructive (4), Execute (5). Each category has a recommended default policy.

Enforce policy on every WordPress Developer MCP Server tool call.

Deterministic rules across all 25 WordPress Developer MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN WORDPRESS DEVELOPER →

Free to start. No card required.

42,500+ MCP servers and 110,000+ tools scanned and risk-classified.