Get up and running with the Nhost CLI
Start developing locally with Nhost. Install the CLI, initialize your project, and spin up a local PostgreSQL database, GraphQL engine, Auth, and Storage.
CLI quickstart local development Nhost CLI setup installThe Nhost CLI is the recommended way to start building your application. It sets up a full local development environment including PostgreSQL, GraphQL, Authentication, and Storage, tracking all migrations and metadata.
Docker is required to run the local environment.
1. Install the CLI
Section titled β1. Install the CLIβSupported platforms
- macOS
- Linux
- Windows (via WSL2)1
Choose your preferred installation method:
npm install -g @nhost/clipnpm add -g @nhost/clibun add -g @nhost/cliyarn global add @nhost/cli # Yarn Classicbrew install nhost/tap/nhostcurl -sSL https://raw.githubusercontent.com/nhost/nhost/main/cli/get.sh | bashnix profile install github:nhost/nhost#cliOr run the CLI without installation:
npx @nhost/cli@latest --versionpnpm dlx @nhost/cli@latest --versionbunx @nhost/cli@latest --versionyarn dlx @nhost/cli@latest --version2. Authenticate
Section titled β2. AuthenticateβLogin to your Nhost account. This is required if you want to pull configuration from an existing Nhost Cloud project (step 3) or deploy later. You can skip it if you only want to develop locally.
nhost login3. Initialize a Project
Section titled β3. Initialize a ProjectβInitialize a new Nhost project in your current directory.
nhost initThis scaffolds your project β a nhost/ directory holding your backend configuration (all version-controlled in Git) plus a functions/ directory for serverless functions:
.ββ π functions # Serverless functions (Node.js / TypeScript)ββ π nhost # Project & backend configuration ββ π emails # Email templates (verification, password reset, β¦) ββ π metadata # Hasura metadata β tables, permissions, relationships ββ π migrations # Database schema migrations ββ π seeds # Seed data for local developmentIf you already have a project on Nhost Cloud and want to pull down its configuration:
nhost init --remote4. Start Local Environment
Section titled β4. Start Local EnvironmentβStart the full Nhost stack locally. This uses Docker to spin up all the necessary services.
nhost upOnce running, the CLI prints the URLs for your local services:
| Service | URLs |
|---|---|
| Postgres: | postgres://postgres:postgres@localhost:5432/local |
| Hasura: | https://local.hasura.local.nhost.run |
| GraphQL: | https://local.graphql.local.nhost.run |
| Auth: | https://local.auth.local.nhost.run |
| Storage: | https://local.storage.local.nhost.run |
| Functions: | https://local.functions.local.nhost.run |
| Dashboard: | https://local.dashboard.local.nhost.run |
| Mailhog: | https://local.mailhog.local.nhost.run |
The local.nhost.run domain resolves to your machine, so these URLs work over HTTPS out of the box.
To stop the environment run nhost down, and to follow the logs run nhost logs.
5. Open the Dashboard
Section titled β5. Open the DashboardβOpen the local dashboard by going to https://local.dashboard.local.nhost.run to manage your database, auth settings, storage, and more.

6. Connect an AI Assistant (optional)
Section titled β6. Connect an AI Assistant (optional)βThe CLI ships an MCP server that lets an AI assistant read your GraphQL schema, run queries and mutations, and manage metadata and migrations against your local project. The fastest way to set it up is to hand the onboarding file to your assistant:
curl -fsSL https://docs.nhost.io/install-mcp | claudecurl -fsSL https://docs.nhost.io/install-mcp | codex exec -curl -fsSL https://docs.nhost.io/install-mcp | geminicurl -fsSL https://docs.nhost.io/install-mcp | <your-assistant-cli>See MCP Development Setup for the manual steps and client configuration.
Next Steps
Section titled βNext StepsβNow that your local backend is running, you can connect your frontend application to it or dive deeper into the CLI.