GraphQL Inspector
MIT
Validates a GraphQL schema, compares two versions of one and reports what changed, and flags which changes are breaking. It also validates stored operations against a schema, which is how you find out that a deploy will break a client before it does.
GraphQL
Specifications it implements
What this tool does to each specification, in the role vocabulary. Follow a standard through to standards.apievangelist.com for what it actually specifies.
| Standard | Role | What that means |
|---|---|---|
| GraphQL | validatesalso tests |
Using this from an agent
- Interfaces
clilibraryci-action- Install
-
npm
@graphql-inspector/cli - Consumes
- graphql
- Emits
- json, text, markdown
- Runtime
- Runs offline Deterministic Read-only No credentials
Where it applies
Jobs this tool actually does, and the surface each one is exercised on.
Determine whether a schema change is breaking before it ships.
ci-pipelinecoding-agent
Breaking-change detection needs BOTH versions of the schema. An agent holding only the new one can validate it, but cannot answer this question.
Validate a set of client operations against the schema they will run against.
ci-pipeline
- Website
- https://the-guild.dev/graphql/inspector
- Repository
- https://github.com/graphql-hive/graphql-inspector
- License
- MIT — reported by the GitHub API, verified 2026-10-06
- Stars
- 1768 · last commit 2026-10-06
Reading this as an agent? Don't scrape the page — this entry is published as
structured data at
arrow_back
All tools by adoption
/tools.json,
against the tool.schema.json
schema, using the roles.json
vocabulary. Start at /llms.txt.