Setting the file. One moment.
Subchapter 13.5
references/webmcp.mdMarkdown2 KBView on GitHub
Use this reference when interacting with the open Playground page through callable WebMCP tools. For setup or connection-method selection, use website workflows.
WebMCP exposes tools through the open webpage. It does not require the local Playground MCP server, its WebSocket bridge, or mcp=yes.
Examples to look for during discovery include:
| Purpose | Example WebMCP tools |
|---|---|
| Site information and persistence | playground_get_site_info, playground_list_sites, playground_rename_site, playground_save_in_browser |
| PHP and WordPress requests | playground_execute_php, playground_request |
| Navigation | playground_navigate, playground_get_current_url |
| Filesystem operations | playground_read_file, playground_write_file, playground_list_files, playground_mkdir |
Use the discovered tool set as the source of truth. Playground can also proxy tools registered by plugins inside the WordPress iframe onto the outer page; rediscover tools after navigation or a site switch when needed. A WordPress ability registration alone does not make it a WebMCP tool.
Background: WordPress Playground and WebMCP: bringing AI agents into your browser workflow (opens in a new tab).
If WebMCP is unavailable or lacks an operation, return to the interaction router and read the selected fallback reference. Preserve the intended site when changing methods; do not create a replacement or reload away current work.
Check tool results and verify the requested state in the same site before claiming success. After navigation or a site switch, confirm the active site and rediscover tools when needed.