MCP GraphQL implements the Model Context Protocol (MCP) to provide a standardized interface for interacting with GraphQL APIs. It automatically exposes every GraphQL query as a distinct MCP tool, with tool inputs that mirror the corresponding GraphQL query parameters. The JSON schema for tool inputs is generated dynamically from query parameters, and no separate schema definition is required—only the API URL and credentials. The server currently supports GraphQL queries (mutations are planned for future releases) and offers configurable authentication (Bearer, Basic, or custom headers) and automatic handling of complex GraphQL types. When a tool is invoked, the server translates the tool call parameters into a GraphQL query, executes it against the target API, and returns the results to the MCP client. If you don't provide predefined queries, the server can introspect the GraphQL schema and auto-generate queries up to a configurable max-depth, though this may produce voluminous responses. For production usage, supplying your own named operations via a queries file or string is recommended, with each operation automatically exposed as an MCP tool.