Connecting Clients

The Backend MCP Server is a remote MCP server over HTTP. Any client that supports remote MCP servers with OAuth2 can connect using nothing but the service URL — the client handles the OAuth2 flow for you, so there are no tokens to copy or config files to hand-edit.

The client pages use https://mcp.acme.com as the example service URL. Replace it with the URL where you deployed Backend MCP (your MCP_REALM).

Claude

Add Backend MCP as a custom connector.

Cursor

Add it to your MCP configuration.

Other clients

Any OAuth2-capable remote MCP client.

Note

Clients that only support local (stdio) MCP servers, or that do not implement the OAuth2 discovery flow, cannot connect directly. Backend MCP is a remote HTTP server and requires OAuth2.

Not what you were looking for?

To connect an AI assistant to Nhost for local development and project management — rather than exposing a deployed project to end users — use the CLI MCP server instead.