mcp-graphql

npx mcp-graphql

{
  "mcpServers": {
    "graphql-mcp": {
      "command": "npx",
      "args": [
        "mcp-graphql"
      ]
    }
  }
}

Point it at an endpoint and it introspects the schema on startup, exposing it both as an MCP resource and through an introspect-schema tool; query-graphql then executes operations against that endpoint. The schema does not have to come from introspection — a local .graphql file or a hosted schema URL works too, which is the practical path when introspection is disabled in production, as it often is. The safety decision worth copying is that mutations are refused unless ALLOW_MUTATIONS is set: a model holding both the full schema and write access can reach any resolver the service exposes, and that is not a default anyone should inherit accidentally.