MCP server for WordPress
An assistant answering a WordPress question can look up the real signature from parsed core source, build an example against a populated site, and hand you a link you can run. This page is how you connect one.
Connect
Add the server to your client. There is no key, and the reference tools are read-only.
Run this in a terminal. Add --scope user to connect it in every project instead of just this one. Identical on macOS, Windows and Linux.
claude mcp add --transport http wppaste https://wppaste.com/api/mcpTools
search_wordpress_symbols- Search WordPress functions, hooks, classes and methods by name. Use this first when you know part of a name but not the exact one. Returns names, kinds and reference URLs.
get_wordpress_symbol- Get the full signature, parameters, return value, availability and source location of one WordPress symbol. Use this before writing code that calls it, so the signature is correct for the version in question.
get_wordpress_source- Read the actual WordPress source of a function or method, as parsed from the release tag.
compare_wordpress_versions- Show what changed between two WordPress releases, or check which releases a symbol exists in. Use this for 'when was X added' and 'why does this work on one site but not another'.
list_sandbox_scenarios- List the pre-built WordPress environments a paste can run in. Call this before create_wordpress_paste so the example runs against real data (a stocked store, a large content set) instead of an empty site.
get_playground_blueprint_schema- The WordPress Playground blueprint format this site builds and accepts: the skeleton, the step names that are permitted, the version and URL parameters, and what a paste already provides for you. Call this before hand-writing a blueprint or passing custom steps to create_playground_link.
create_playground_link- Build a WordPress Playground URL that boots a real WordPress in the browser and runs a PHP snippet. Returns a link the user can open immediately. Use create_wordpress_paste instead when the code should also be saved and shareable; use this for a throwaway demonstration.
create_wordpress_paste- Save a runnable PHP snippet and get a shareable URL. The reader can press Run and execute it in a real WordPress in their browser. Use this to hand someone a working, reproducible example rather than code in chat.
Sandbox environments
An example is only reproducible if the data it needs exists. These are the environments a paste can boot into, and what each one already contains.
blog: Blog with posts- Posts 1-5 (post 2 has a `price` meta of 19.99), page 6, categories `news` and `updates`, tag `featured`.
store: WooCommerce store- WooCommerce active. Product categories `clothing`, `accessories`, `sale`. Five products by SKU (TSHIRT-01 £19.99, JACKET-01 £89 on sale at £69, BELT-01 out of stock, TOTE-01 free, SCARF-01 on sale). A `shopper` customer and one completed order of 2x TSHIRT-01.
acf-fields: Custom fields (ACF)- ACF active, plus registered post meta `subtitle` (string) and `rating` (number) on posts 1-3, so `get_field()` and `get_post_meta()` can be compared directly.
seo: SEO plugin installed- Yoast SEO active over the standard blog fixtures.
forms: Contact form- Contact Form 7 active. `wp_mail` is intercepted and printed rather than sent, so submissions are inspectable.
many-posts: Large content set- 60 published posts spread over 60 days, round-robin across three authors and the `news`/`updates` categories.
debug: Debugging toolkit- Query Monitor and Health Check active over the standard blog fixtures.
Scope
The corpus is WordPress core, parsed from its own release tags across the five most recent release lines. A tool call returns what a page like get_post() shows. Plugin and theme functions are not in it: a WooCommerce function will not resolve, even though the store environment can run one.