Hasura MCP Server

If you already use Hasura MCP, the hasura mcp mcp server is the piece that lets your assistant work with it directly. This Model Context Protocol (MCP) server provides an advanced interface for AI agents (like those in Cursor or Claude Desktop) to interact with a Hasura GraphQL endpoint. It enables agents to discover the API structure, execute both.

What the server does

• Hasura GraphQL Schema (hasura:/schema) —
• Provides the full GraphQL schema definition obtained via standard introspection
• MIME Type: — application/json
• Agents can read this resource to understand the complete structure of the API, including types, fields, arguments, directives, etc
• run_graphql_query —
• Description: — Executes a read-only GraphQL query against the Hasura endpoint. Use this for fetching data when a specific tool isn't available. Ensure the query does not modify data. Example: query { users { id name } }

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Credentials and setup notes

Configuration is passed through the environment: ADMIN_SECRET, YOUR_ADMIN_SECRET. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Node.js (v18 or higher recommended, check .nvmrc or package.json engines if specified) * pnpm (or npm/yarn, adjust commands accordingly) * Access to a running Hasura GraphQL endpoint. * (Optional but recommended) Hasura Admin Secret for privileged access, or properly configured default role permissions.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by husamabusafa; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.