Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Nhost

by nhostversion 0.4.0-beta2i★ –iRuns on your computer
Registry nameio.github.nhost/mcp

Install

Overview

Description from the maker (original English)

Let your users work with their own data through an AI assistant, limited to what they can see.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: Streamable HTTP
  • Category: Other
  • You need to fill in: MCP_GRAPHQL_ENDPOINT, MCP_AUTH_URL

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: MCP_GRAPHQL_ENDPOINT, MCP_AUTH_URL

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "nhost": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "MCP_GRAPHQL_ENDPOINT",
        "-e",
        "MCP_AUTH_URL",
        "docker.io/nhost/mcp:0.4.0-beta2"
      ],
      "env": {
        "MCP_GRAPHQL_ENDPOINT": "your-value",
        "MCP_AUTH_URL": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add nhost --env MCP_GRAPHQL_ENDPOINT=your-value --env MCP_AUTH_URL=your-value -- docker run -i --rm -e MCP_GRAPHQL_ENDPOINT -e MCP_AUTH_URL docker.io/nhost/mcp:0.4.0-beta2

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "nhost": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "MCP_GRAPHQL_ENDPOINT",
        "-e",
        "MCP_AUTH_URL",
        "docker.io/nhost/mcp:0.4.0-beta2"
      ],
      "env": {
        "MCP_GRAPHQL_ENDPOINT": "your-value",
        "MCP_AUTH_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "nhost": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "MCP_GRAPHQL_ENDPOINT",
        "-e",
        "MCP_AUTH_URL",
        "docker.io/nhost/mcp:0.4.0-beta2"
      ],
      "env": {
        "MCP_GRAPHQL_ENDPOINT": "your-value",
        "MCP_AUTH_URL": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • MCP_GRAPHQL_ENDPOINT required env
    GraphQL endpoint of the Nhost project the server exposes, e.g. http://hasura-service:8080/v1/graphql
  • MCP_AUTH_URL required env
    Nhost Auth URL used as the OAuth2 authorization server, e.g. https://SUBDOMAIN.auth.REGION.nhost.run/v1

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account nhost, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32461 servers in this category
  • Published to the registry more recently than 91% of the other 32461 servers in this category
  • Basic checks equal to or better than 100% of the other 32461 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Nhost safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: MCP_GRAPHQL_ENDPOINT, MCP_AUTH_URL

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.4.0-beta2) reached the registry 3 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, dotnet-mcp

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday
Install

dotnet-mcp

by Skymly

MCP server for .NET symbols, XAML, source generators, and restricted workspace edit

Runs on your computerUpdated today
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Nhost MCP Service

The Nhost MCP service adds an agentic interface to any Nhost project. It exposes your project's GraphQL API as an MCP (Model Context Protocol) server, allowing AI assistants like Claude, Cursor, or any MCP-compatible client to query and mutate your data.

If you're building on Nhost, this service lets your users interact with their project data through AI assistants — no custom integration code required. Deploy it alongside your project and any MCP-compatible client can connect, authenticate on behalf of your users via your existing Nhost Auth setup, and work with your data within the permissions defined.

How It Works

The MCP server sits between your AI assistant and your Nhost project's GraphQL API. It provides three tools that the assistant can call:

  • `get-schema` - Introspects the GraphQL schema so the assistant understands your data model. Returns either a summary of available operations or the full SDL for specific queries/mutations.
  • `graphql-query` - Executes read-only GraphQL queries against your project.
  • `graphql-mutation` - Executes GraphQL mutations to create, update, or delete data.

On startup, the server fetches a schema summary from your GraphQL endpoint and includes it in the MCP instructions, giving the AI assistant immediate context about your data model without any additional configuration.

Authentication with OAuth2

The MCP service integrates with Nhost Auth as an OAuth2 authorization server, following the MCP Authorization specification. This means any MCP client that supports OAuth2 can authenticate with your Nhost project automatically.

The flow works as follows:

  1. The MCP client discovers authentication requirements by fetching /.well-known/oauth-protected-resource from the MCP server.
  2. The client redirects the user to the Nhost Auth authorization endpoint for login (authorization code flow with PKCE).
  3. After authentication, the client exchanges the authorization code for a JWT access token.
  4. All subsequent MCP requests include the JWT as a Bearer token.
  5. The MCP server validates the JWT signature via JWKS, checks the issuer and expiration, then forwards the token on every GraphQL request.
  6. The GraphQL service enforces row-level and column-level permissions based on the JWT's claims, so the AI assistant can only access data the authenticated user is allowed to see.

IMPORTANT! CIMD needs to be enabled.

Enforcing a Specific Role

The --enforce-role flag restricts the MCP server to accept only tokens whose x-hasura-default-role claim matches the specified role. Requests with a different default role receive a 403 Forbidden response.

For example, setting --enforce-role=user_mcp means only tokens issued with user_mcp as the default role will be accepted. If you've configured permissions for that role with limited access (e.g., read-only on certain tables), the AI assistant will be restricted to those permissions.

This lets you:

  • Create a dedicated role (e.g., user_mcp) with restricted permissions for AI access.
  • Allow AI assistants to read data but not modify it.
  • Limit which tables or columns are visible to the assistant.
  • Run multiple MCP instances with different role configurations for different use cases.

Configuration

All flags can be set via environment variables.

FlagEnv VarDescription
--listen-addrMCP_LISTEN_ADDRHTTP listen address (default: :3000)
--debugMCP_DEBUGEnable debug logging
--log-format-textMCP_LOG_FORMAT_TEXTFormat logs in plain text instead of JSON
--graphql-endpointMCP_GRAPHQL_ENDPOINTGraphQL endpoint URL (required)
--mcp-instructionsMCP_INSTRUCTIONSServer-level MCP instructions
--query-instructionsMCP_QUERY_INSTRUCTIONSInstructions for the graphql-query tool
--mutation-instructionsMCP_MUTATION_INSTRUCTIONSInstructions for the graphql-mutation tool
--schema-instructionsMCP_SCHEMA_INSTRUCTIONSInstructions for the get-schema tool
--auth-urlMCP_AUTH_URLOAuth2 authorization server URL (required)
--realmMCP_REALMRealm for WWW-Authenticate header
--enforce-roleMCP_ENFORCE_ROLEEnforce that the JWT's default Hasura role matches this value
--browser-htmlMCP_BROWSER_HTMLHTML content to serve when a browser visits the service URL

Deploying to Nhost

To deploy to Nhost Run you can use the one-click install link below:

https://app.nhost.io/run-one-click-install?config=eyJuYW1lIjoibWNwIiwiaW1hZ2UiOnsiaW1hZ2UiOiJuaG9zdC9tY3A6MC4xLjAiLCJwdWxsQ3JlZGVudGlhbHMiOm51bGx9LCJjb21tYW5kIjpbIm1jcCJdLCJyZXNvdXJjZXMiOnsiY29tcHV0ZSI6eyJjcHUiOjEyNSwibWVtb3J5IjoyNTZ9LCJzdG9yYWdlIjpbXSwicmVwbGljYXMiOjEsImF1dG9zY2FsZXIiOm51bGx9LCJlbnZpcm9ubWVudCI6W3sibmFtZSI6Ik1DUF9BVVRIX1VSTCIsInZhbHVlIjoiaHR0cHM6Ly9TVUJET01BSU4uYXV0aC5SRUdJT04ubmhvc3QucnVuL3YxIn0seyJuYW1lIjoiTUNQX1JFQUxNIiwidmFsdWUiOiJodHRwczovL21jcC5hY21lLmNvbSJ9LHsibmFtZSI6Ik1DUF9HUkFQSFFMX0VORFBPSU5UIiwidmFsdWUiOiJodHRwOi8vaGFzdXJhLXNlcnZpY2U6ODA4MC92MS9ncmFwaHFsIn0seyJuYW1lIjoiTUNQX0lOU1RSVUNUSU9OUyIsInZhbHVlIjoiVGhlc2UgYXJlIHNvbWUgaW5zdHJ1Y3Rpb25zIGZvciB5b3VyIE1DUCBzZXJ2ZXIuIn0seyJuYW1lIjoiTUNQX0VORk9SQ0VfUk9MRSIsInZhbHVlIjoidXNlcl9tY3AifV0sInBvcnRzIjpbeyJwb3J0IjozMDAwLCJ0eXBlIjoiaHR0cCIsInB1Ymxpc2giOnRydWV9XSwiaGVhbHRoQ2hlY2siOm51bGx9

And edit as needed. Make sure to set the correct subdomain and region in the MCP_AUTH_URL (or your custom domain if you using one), set the MCP_REALM to the URL you will use for your MCP service, change the MCP_INSTRUCTIONS as needed and change or remove MCP_ENFORCE_ROLE

NOTE: Check the releases page and make sure you are using the most recent version of the service.

Alternatively, add a run-mcp.toml to your project directory:

name = 'mcp'

command = ['mcp']

[image] image = 'nhost/mcp:0.1.0'

[[environment]] name = 'MCP_AUTH_URL' value = 'https://local.auth.local.nhost.run/v1'

[[environment]] name = 'MCP_REALM' value = 'https://myapp.example.com'

[[environment]] name = 'MCP_GRAPHQL_ENDPOINT' value = 'http://hasura-service:8080/v1/graphql'

[[environment]] name = 'MCP_INSTRUCTIONS' value = 'This MCP server interacts with my application'

[[environment]] name = 'MCP_ENFORCE_ROLE' value = 'user_mcp'

[[ports]] port = 3000 type = 'http' publish = true

[resources] replicas = 1

[resources.compute] cpu = 125 memory = 256

Then deploy your project as usual. The MCP server will be available at the published port and any MCP-compatible client can connect to it.

You can also try locally with:

nhost up --run-service run-mcp.toml

Connecting an MCP Client

Point your MCP client to the server URL. For example, in Claude Desktop's configuration:

  1. Go to customize -> Connectors
  2. Click on + and enter any name you want and the url where your MCP server resides, for instance https://mcp.acme.com
  3. Click "Add"
  4. Once connected you will be redirected to your Oauth2's consent page to authorize the Oauth2 client.
Ask PopNx