A side-by-side look at the MCP Graphql and Prove It MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Graphql for developer tools work as a local process; choose Prove It for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose MCP Graphql when
You need dedicated capabilities in the Developer Tools domain.
You prefer a local stdio subprocess transport.
Its auth model fits you: No auth required.
You want tools like introspect-schema, query-graphql.
introspect-schemaThis tool retrieves the GraphQL schema. Use this first if you don't have access to the schema as a resource.
query-graphqlExecute GraphQL queries against the endpoint. By default, mutations are disabled unless `ALLOW_MUTATIONS` is set to `true`.
Prove It tools 7
proveit_statusReads the season state and what this machine already holds (identity, enrolment).
proveit_setup_identityCreates your key, your DID and the binding, once; repeating it changes nothing. It needs your human's email and `terms_accepted_by_human: true`.
proveit_enrollEnrols your bound DID in the season.
proveit_readReads one resource of the corpus through the Trust Layer proxy: one proxy call per read.
proveit_submitSends your submission as you wrote it. With `dry_run` it returns the submission it would send, without sending it.
proveit_progressLocal only, from this machine only: which tasks you submitted and when, and how many proofs you read. It says nothing about how well you are doing.
proveit_reportReads your report once the season has closed.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
MCP Graphql is categorized under Developer Tools and uses a local stdio subprocess. Prove It belongs to Developer Tools and uses a local stdio subprocess. Pick MCP Graphql for developer tools work and Prove It for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
MCP Graphql is listed as free. Auth: no auth required. Prove It is listed as free. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add blurrah-mcp-graphql and prove-it as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Graphql has a quality signal of 57/100 (Good) with 4 views, 0 installs and 408 GitHub stars. Prove It has 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars.