Operations integration
WPGraphQL MCP
WPGraphQL gives a site a GraphQL API, often for a headless front end. WP MCP adds two free, read-only ops on the plugin-data pair, so no new top-level tool appears. wpgraphql-query runs a query through WPGraphQL's own graphql() as the current user, so WPGraphQL's resolvers and their permission checks decide what comes back, exactly as they do for the front end; it takes the query, optional variables and an optional operation_name. Mutations and subscriptions are refused with mutation_refused before WPGraphQL runs: the document is scanned with comments and strings skipped, and parsed as well when WPGraphQL's bundled parser is loaded, and any operation that is not a query refuses the whole call. Results return data and errors (message, locations and path only), WPGraphQL's debug extensions are dropped, and emails, phone numbers and IP addresses are masked wherever they appear, with masked:true in the response. A result over 100 KB is refused with a hint to ask for fewer items or fields. wpgraphql-get-schema summarises the schema through introspection: the root query fields with their types and arguments and the type names by kind, or one named type's fields, input fields, enum values and interfaces. The mutation and subscription roots are left out. Both ops need edit_posts and write nothing.
What your AI can do
Real WPGraphQL operations, every write reversible.
- Run a GraphQL query as the signed-in user, with variables
- See only what WPGraphQL's own permission checks allow
- List the root query fields and every type by kind
- Describe one type's fields, arguments, enum values and interfaces
- Get results with emails, phones and IPs masked
- Test the queries a headless front end depends on, without changing anything
Example prompts
Example WPGraphQL prompts.
What can I query through WPGraphQL on this site? Summarise the schema.
Run the query our Next.js front end uses for the blog index and show me what it returns.
Which fields does the Post type expose, and does it include our ACF fields?
Under the hood
The WPGraphQL calls, under the hood.
plugin-data-read({ operation: "wpgraphql-get-schema", args: { type: "Post" } }), fields, args, interfaces; no mutation root
plugin-data-read({ operation: "wpgraphql-query", args: { query: "{ posts(first: 5) { nodes { title uri } } }" } }), read only; personal values masked
In the free plugin
The WPGraphQL integration is in the free plugin.
The core WPGraphQL tools ship in the free, GPL plugin with the full snapshot and undo engine, and no trial clock. Pro adds 133 more tools, including Elementor deep editing, the other page builders, the forms adapter pack and, for some integrations, extra operations. The pricing page lists what each tier includes.
Frequently asked
WPGraphQL MCP: questions, answered.
With WPGraphQL, can the agent run a mutation?
No. Any document holding a mutation or subscription is refused with mutation_refused before WPGraphQL sees it. Changes go through WP MCP's own write tools, which are snapshotted and undoable.
Whose permissions does a query run with?
The signed-in user's. The query goes through WPGraphQL's graphql() as that user, so private or draft content appears only if WPGraphQL would show it to them. Both ops also need edit_posts.
Why are emails masked in the results?
A single GraphQL result can hold many people's data, so WP MCP applies its list masking rule: emails, phone numbers and IP addresses are masked wherever they appear, and the response says masked:true.
Is the WPGraphQL integration part of the free plugin?
Yes. Both WPGraphQL ops are free and appear on the plugin-data pair while WPGraphQL is active.
Related integrations
More integrations for the same agent.
MCP for ACF & ACF Pro
FreeCustom fields, 5 tools.
MCP for JetEngine
FreeCustom fields, 2 tools.
MCP for Pods
FreeCustom fields, 2 tools.
MCP for Meta Box
FreeCustom fields, 5 tools.
MCP for Code Snippets
FreeOperations, 2 tools.
MCP for UpdraftPlus
FreeOperations, 2 tools.
Browse the full Integrations hub, or read more on the WordPress MCP plugin.