Gadget MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GADGET_APP | Yes | App slug, e.g. my-app | |
| GADGET_API_KEY | Yes | Production API key | |
| GADGET_ENVIRONMENT | No | The environment to connect to (production or development) | production |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| introspect_modelA | List all fields and their types for a Gadget model. Run this first when you're unsure what fields exist on a model. |
| list_modelsA | List all models (types) available in this Gadget app via GraphQL introspection. |
| query_recordsA | Query records from any Gadget model. Supports filtering, sorting, pagination cursors, and field selection. Use introspect_model first to discover available fields, and introspect_filters to see valid filter shapes. |
| count_recordsA | Return the total number of records for a Gadget model, with optional filtering. |
| get_recordA | Get a single Gadget record by ID. Specify the model name, record ID, and fields to return. |
| introspect_filtersA | Show all available filter fields and their types for a Gadget model. Use this to construct valid filter arguments for query_records and count_records. |
| introspect_actionsA | List all actions (mutations) available in this Gadget app, including their arguments. Useful for understanding what write operations are available, even though this server is read-only. |
| get_schema_overviewA | Return all models with their fields and types in a single call. Use this for a broad understanding of the app schema before diving into specific models. |
| run_graphqlA | Run an arbitrary read-only GraphQL query against the Gadget app. Use this for complex queries with nested relations or custom filtering that query_records can't express. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Each tool has a unique and clear purpose: counting records, fetching single record, schema overview, action/filter/model introspection, listing models, querying records, and running arbitrary GraphQL. No overlap in functionality.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., count_records, introspect_model, run_graphql). Verbs are uniform and descriptive.
9 tools is well-scoped for a read-only Gadget server, covering schema discovery, record retrieval, counting, and custom queries without being excessive or insufficient.
For a read-only server, the tool surface is thorough: schema introspection, record CRUD (get, query, count), filter discovery, and arbitrary GraphQL queries. No obvious gaps for typical read operations.