playground.wordpress.net

Last change

None yetUnchanged since first read.

Declared read-only

8 of 17

llms.txt

Present

1. playground_delete_directoryCan change things

   Delete a directory from the WordPress virtual filesystem. WARNING: Deletion is permanent and cannot be undone. By default (recursive=false), the directory must be empty or the call will fail. Set recursive=true to delete a directory and all its contents — use with care.

   First seen 11 Oct 2026. Unchanged since.

2. playground_delete_fileCan change things

   Delete a file from the WordPress virtual filesystem. WARNING: Deletion is permanent and cannot be undone. Returns an error if the file does not exist — use playground_file_exists first if deletion is conditional.

   First seen 11 Oct 2026. Unchanged since.

3. playground_execute_phpCan change things

   Run arbitrary PHP code in WordPress Playground and return the output. WordPress is NOT bootstrapped automatically. To use WordPress functions, start your code with: require("/wordpress/wp-load.php"); Always include the opening <?php tag. The response JSON contains three fields: - "text": stdout output - "errors": PHP warnings, notices, and fatal error messages from s

   First seen 11 Oct 2026. Unchanged since.

4. playground_file_existsReads only

   Check whether a file or directory exists in the WordPress virtual filesystem.

   First seen 11 Oct 2026. Unchanged since.

5. playground_get_current_urlReads only

   Get the current URL path of the WordPress site displayed in Playground. For additional metadata (WordPress version, PHP version, document root), use playground_get_site_info instead.

   First seen 11 Oct 2026. Unchanged since.

6. playground_get_site_infoReads only

   Get metadata about the running WordPress instance: current URL, document root, site URL, WordPress version, and PHP version. Use this when you need version information or the document root path. For just the current URL, prefer playground_get_current_url.

   First seen 11 Oct 2026. Unchanged since.

7. playground_get_website_urlReads only

   Return the URL the user must open in their browser to use WordPress Playground with this MCP server. Use this tool whenever you need to send the user to Playground or open it autonomously — always obtain the URL from this tool rather than constructing it manually.

   First seen 11 Oct 2026. Unchanged since.

8. playground_list_emailsReads only

   List every email the WordPress site has sent so far. Playground has no mail server. Each message WordPress attempts to send (password resets, comment notifications, wp_mail() calls…) is captured instead of being delivered. Use this tool to read those messages, e.g. to verify that a plugin sent an email or to retrieve a confirmation link. Returns the full inbox in send orde

   First seen 11 Oct 2026. Unchanged since.

9. playground_list_filesReads only

   List files and directories at a given path in the WordPress virtual filesystem. Returns a flat, non-recursive listing of the immediate contents. To explore subdirectories, call this tool again with the subdirectory path.

   First seen 11 Oct 2026. Unchanged since.

10. playground_list_sitesReads only

    List all WordPress Playground sites available. Call this before any other playground tool — it returns the siteId required by every other operation. If this returns no sites, the user may need to open Playground in their browser. Use playground_get_website_url to get the exact URL to send to the user. Returns site names and storage type. "temporary" sites are lost on p

    First seen 11 Oct 2026. Unchanged since.

11. playground_mkdirCan change things

    Create a directory (and all required parent directories) in the WordPress virtual filesystem. Call this before playground_write_file when writing to a path whose parent directories do not yet exist.

    First seen 11 Oct 2026. Unchanged since.

12. playground_navigateCan change things

    Navigate to a URL path in WordPress Playground and return the final URL after any redirects. Examples: "/wp-admin/", "/wp-login.php", "/". On 404 or error pages, navigation still succeeds from the tool's perspective — check the returned URL or use playground_request to verify the HTTP status code if needed.

    First seen 11 Oct 2026. Unchanged since.

13. playground_read_fileReads only

    Read a file from the WordPress virtual filesystem. Returns the file contents as text.

    First seen 11 Oct 2026. Unchanged since.

14. playground_rename_siteCan change things

    Rename a WordPress Playground site. Updates the display name shown in the browser UI.

    First seen 11 Oct 2026. Unchanged since.

15. playground_requestCan change things

    Make an HTTP request to the WordPress site running in Playground. REST API requests (/wp-json/* or ?rest_route=) are automatically authenticated with a valid nonce — no manual auth needed. Tool selection guide: 1. Use this tool (playground_request) with the REST API for standard content CRUD — posts, pages, users, terms, comments, settings, etc. The REST API ha

    First seen 11 Oct 2026. Unchanged since.

16. playground_save_in_browserCan change things

    Save a temporary WordPress Playground site to browser storage so it survives page reloads. Safe to call even if the site is already saved (no-op). Sites start as temporary by default and are lost when the browser tab is closed or the page is reloaded. Call this early in any multi-step workflow where losing progress would be costly.

    First seen 11 Oct 2026. Unchanged since.

17. playground_write_fileCan change things

    Write content to a file in the WordPress virtual filesystem. WARNING: Overwrites the entire file — existing content is permanently lost. Read the file first with playground_read_file if you need to preserve any content. Creates the file if it does not exist. Parent directories are NOT created automatically — call playground_mkdir first if needed, otherwise the write wi

    First seen 11 Oct 2026. Unchanged since.

Run this site? This page shows what your site told our crawler, ToolChronicleBot. To be left out, disallow it in robots.txt or write to hello@toolchronicle.com.