
Nhost Backend MCP Server: Setup for Claude, Cursor and Other Apps
Lets people connect Claude, Cursor or another assistant to their own data in an Nhost app, limited to what their account is allowed to see.
This is Nhost's own MCP service for an Nhost project. You deploy it next to your project, and it turns the project's GraphQL API into three tools. Each person signs in through your Nhost Auth, and every request runs as that person, so your existing permissions apply. It is not a one-click app for end users, so the project owner sets it up first.
Good for
- Teams building on Nhost who want users to query app data from an AI assistant
- Developers who need row and column permissions to apply to AI access
- Admins who want a dedicated read-only role for AI use
Works in
12 should work
Tap an app to see how to set it up and any known problems.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Client does not support this transport.
Client does not support this transport.
Install Nhost MCP
Claude Code
- 1
Copy this prompt.
Add the Nhost MCP server to Claude Code. Run this command: claude mcp add --transport http nhost https://YOUR-MCP-SERVICE-URL Then check that it loaded and tell me if I need to sign in or restart.
- 2
Paste it into Claude Code. It shows the change and asks before running it.
Requires Your own deployed Backend MCP service.
Nhost has no shared server. Deploy the Backend MCP service first (Nhost Run, one-click or run-mcp.toml), then replace the placeholder address with your service URL. Your Nhost Auth needs the OAuth2 provider, CIMD and a consent page. You sign in through your app when you connect. Not documented by Nhost for this app; the connection uses the same address as the documented ones.
Built from the package data we hold. Not yet tested by us.
Tools
Shows the assistant what data your project has
Introspects the GraphQL schema and returns either a summary of operations or the full definition of the ones asked for, so the assistant understands your data model.
Try: “What tables can you see?”
Network ·
get-schemaReads data from the project
Runs a read-only GraphQL query as the signed-in user. Row and column permissions from your Nhost project still apply.
Try: “Show my orders from the last 30 days.”
Network ·
graphql-queryCreates, changes or deletes data
Runs a GraphQL mutation as the signed-in user. The tool is marked destructive in its source, and the project permissions decide what is allowed.
Try: “Mark order 42 as shipped.”
Delete ·
graphql-mutation
From the official docs
Permissions
high risk · 3 things to watch · 1 advisory
High risk
The assistant can read and, by default, change or delete any data the signed-in user is allowed to touch in your Nhost project. Create a role with only the access you want and enforce it, for example read-only.
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only modeHow to turn it on
Watch out for
The mutation tool can change or delete data
It runs any GraphQL mutation the signed-in user may run. Enforce a read-only role unless you want the assistant to write. github.com
It does not limit operations itself
The server accepts any query or mutation and relies on your GraphQL permissions. Review row and column rules before you deploy. github.com
Content in your data can steer the assistant
The docs warn about prompt injection from stored data. Give the AI role the least access you can. github.com
Security advisories
8 other advisories are about the wider nhost project, not this MCP server. See them on GitHub
Technical details
| Turning on read-only | Set the enforce-role option (MCP_ENFORCE_ROLE) to a role that only has read permissions in your GraphQL permissions. |
|---|---|
| Talks to | Your Nhost GraphQL endpoint and Nhost Auth |
| Sign-in and keys | Users sign in with OAuth2 through Nhost Auth. The server checks the JWT and forwards it on each GraphQL request. |
| Scopes |
|
Questions
Is the Nhost MCP server official?
Yes. It is the Backend MCP service in the nhost/nhost repository, published by Nhost.
What is the Nhost MCP server URL?
There is no shared URL. You deploy the service yourself, for example on Nhost Run, and use the address you give it, such as https://mcp.acme.com.
What do I need to set up first?
Your Nhost Auth must be an OAuth2 provider with CIMD clients and a consent page enabled. Then set the GraphQL endpoint and the Auth URL on the service.
Can I make it read-only?
Yes. Create a role that only has read permissions and set MCP_ENFORCE_ROLE to it. Tokens with any other default role get a 403.
Which AI apps can connect?
The docs cover Claude as a custom connector and Cursor with a URL config. Any client that supports remote MCP servers with OAuth2 should work the same way.
Can it see other users' data?
No more than your permissions allow. Every request runs with the signed-in user's token, so row and column rules in your GraphQL permissions apply.
Information
updated Nov 2, 2026
- Publisher
- Official
- Package
nhost/mcp- Registry
- Docker
- Transport
- Streamable HTTP
- Auth
- OAuth
- Version
- 0.3.0
- License
- MIT
- Last commit
- Oct 31, 2026
- Open issues
- 86
- Listed in
- Official MCP registry
Sources
Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.
Show all 4Hide
- github.com · github.com
- github.com · github.com
- github.com · github.com
- github.com · github.com