Gadget MCP Server
Related Servers
Alternatives to Gadget MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA generic MCP server that converts .graphql query files into tools for Claude, enabling interaction with any GraphQL API without coding.MIT
- AlicenseBqualityDmaintenanceRead-only MCP server that lets Claude, ChatGPT, or Cursor answer pest-business questions from your GorillaDesk account in plain English—looks up customers, invoices, schedules, and technicians without creating or changing data.19MIT
- AlicenseAqualityDmaintenanceGraphQL MCP Server that acts as a bridge allowing MCP clients (like Cursor or Claude Desktop) to interact with target GraphQL APIs through standard tools for schema introspection and operation execution.26 npm3MIT
- 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.29 npm1MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that exposes GraphQL operations as typed tools for AI models, with schema exploration, validation, execution, hot reload, OAuth, prompts, MCP Apps widgets, and OpenTelemetry support.8 npmMIT
- AlicenseAqualityDmaintenanceA read-only MCP server that provides AI coding tools with database schema structure (tables, columns, keys, relationships) without exposing row data.326 PyPIApache 2.0
TDQS
Scored across 13 tools
Most tools target distinct operations (query_records vs run_graphql vs export_records vs group_count are clearly differentiated), but there is a cluster of five overlapping introspection tools (list_models, get_schema_overview, introspect_model, introspect_filters, introspect_actions) where get_schema_overview largely subsumes list_models and introspect_model. Descriptions do clarify the layering, so misselection is possible but avoidable.
Every tool follows a clean snake_case verb_noun pattern (count_records, introspect_model, list_models, get_record, run_graphql, query_records, export_records, group_count, read_logs, report_bug). No camelCase or style mixing; conventions are fully predictable.
13 tools is well-scoped for a data-access/introspection server, and each tool covers a distinct capability (query, count, group, export, schema introspection, logs, bug reporting). Nothing feels redundant or padded.
The surface covers read, count, group, export, and introspection well, but the introspect_actions description explicitly points users toward run_action, create_record, and update_record — none of which exist in the tool set — creating a dead end for mutations. There is also no delete operation, so the lifecycle is notably incomplete for the referenced domain.