Skip to content

GraphQL Schema Viewer

Last updated:

This tool is provided as-is for convenience. Output should be verified before use in any production or critical context.

Agent Invocation

Best Path For Builders

Browser workflow

Runs instantly in the browser with private local processing and copy/export-ready output.

Browser Workflow

This tool is optimized for instant in-browser execution with local data handling. Run it here and copy/export the output directly.

/graphql-schema-viewer/

For automation planning, fetch the canonical contract at /api/tool/graphql-schema-viewer.json.

How to Use GraphQL Schema Viewer

  1. 1

    Paste your GraphQL schema

    Input a GraphQL schema (full schema, not introspection JSON). The viewer parses it and builds an interactive type explorer.

  2. 2

    Browse types and fields

    Click on any type to see its fields, arguments, and return types. Drill down into nested types to understand the full structure. Follow relationships between types.

  3. 3

    Find mutations and subscriptions

    Locate mutation definitions to understand available write operations. Look for subscription types to see real-time events your API supports.

  4. 4

    Generate queries from schema

    Some versions let you click fields to auto-generate query or mutation boilerplate. Use this to jumpstart GraphQL queries without manually typing type names.

Frequently Asked Questions

What GraphQL schema format is supported?
GraphQL Schema Definition Language (SDL) — the standard .graphql format used by Apollo, Hasura, Prisma, and most GraphQL servers. Paste your schema SDL directly.
Can I explore types without a running server?
Yes, paste your schema SDL. No server connection needed. The tool parses and displays all types, fields, arguments, and relationships entirely client-side.
Does it show relationships between types?
Yes, click any type to see which other types it references through its fields. The type browser lets you navigate the schema by clicking on field types.
Can I search for specific fields?
Yes. The search box matches type names and field names, so typing a field name filters the type browser to the types that declare it.
Does it validate the schema?
Yes. The parser flags undefined type references, meaning a field whose type is not a built-in scalar or a type declared in the schema, with a descriptive message.