mcp-graphql-bridge
Related Servers
Alternatives to mcp-graphql-bridge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to interact with GraphQL APIs through schema introspection and query execution.1,191 npm1MIT
- AlicenseAqualityDmaintenanceEnables AI agents to connect to any GraphQL endpoint, introspect schemas, and execute queries or mutations through auto-generated tools.2210 npmMIT
- AlicenseNot gradedqualityAmaintenanceConverts a GraphQL schema into MCP tools, allowing AI to discover and call GraphQL queries and mutations via natural language.207 npmMIT
- AlicenseBqualityDmaintenanceEnables AI assistants to execute GraphQL queries and retrieve schema information from any GraphQL endpoint.2223 npm8MIT
- AlicenseAqualityDmaintenanceProvides comprehensive GraphQL introspection, filtering, and query/mutation execution with safety controls. Enables AI agents to explore and interact with GraphQL APIs through natural language.74 npm1MIT
- AlicenseAqualityAmaintenanceA generic MCP (Model Context Protocol) server that bridges any GraphQL API to Claude Code. It introspects your GraphQL schema and exposes each query and mutation as an individual tool, letting Claude interact with your API directly.221 npm1MIT
TDQS
Scored across 8 tools
The query__* tools are clearly separated by resource and singular/plural variant, and get_type_details serves a distinct introspection role. execute_graphql overlaps with the specific query tools by design, but its fallback purpose is clearly stated, so misselection is unlikely.
The six query tools follow a consistent query__<resource> pattern, and the singular/plural distinction is predictable. The generic tools get_type_details and execute_graphql use a different verb_noun style, which is a minor deviation but not confusing.
Eight tools is a lean, focused set for a GraphQL bridge: six common resource queries plus two generic utilities for schema inspection and arbitrary operations. Each tool has a clear purpose and the count feels appropriate.
The generic execute_graphql tool ensures any query or mutation can be run, covering coverage gaps beyond the named resources. get_type_details supports the workflow of discovering types and fields, so the surface has no obvious dead ends.