Advanced Hasura GraphQL MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_graphql_queryA | Executes a read-only GraphQL query against the Hasura endpoint... |
| run_graphql_mutationC | Executes a GraphQL mutation to insert, update, or delete data... |
| list_tablesA | Lists available data tables (or collections) managed by Hasura, organized by schema with descriptions |
| list_root_fieldsC | Lists the available top-level query, mutation, or subscription fields... |
| describe_graphql_typeC | Provides details about a specific GraphQL type (Object, Input, Scalar, Enum, Interface, Union)... |
| preview_table_dataB | Fetch esa limited sample of rows (default 5) from a specified table... |
| aggregate_dataC | Performs a simple aggregation (count, sum, avg, min, max)... |
| health_checkC | Checks if the configured Hasura GraphQL endpoint is reachable... |
| describe_tableB | Shows the structure of a table including all columns with their types and descriptions |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Hasura GraphQL Schema (via Introspection) |
TDQS
Scored across 9 tools
Each tool has a clearly distinct purpose with no ambiguity. Tools like 'list_tables', 'describe_table', and 'preview_table_data' form a logical progression for table exploration, while 'run_graphql_query' and 'run_graphql_mutation' handle different operation types. The 'aggregate_data' tool provides specific functionality separate from general queries.
All tools follow a consistent verb_noun naming pattern throughout. Examples include 'list_tables', 'describe_table', 'run_graphql_query', and 'preview_table_data'. This consistency makes the tool set predictable and easy for agents to understand and navigate.
With 9 tools, this server is well-scoped for its purpose of interacting with Hasura GraphQL. Each tool earns its place by covering distinct aspects like schema exploration, data operations, and system health. The count is neither too sparse nor overwhelming for the domain.
The tool surface provides complete coverage for Hasura GraphQL interaction. It includes schema discovery ('list_root_fields', 'describe_graphql_type'), data exploration ('list_tables', 'describe_table', 'preview_table_data'), CRUD operations ('run_graphql_query', 'run_graphql_mutation', 'aggregate_data'), and system monitoring ('health_check'). No obvious gaps exist for core workflows.