Commands

The NSIN CLOUD command bar turns one typed line into one app or database action. There is no AI behind it: a small set of patterns matches what you type, and each one maps to exactly one REST call — the same call the MCP tools make.

How it works

⌘K or Ctrl K opens the bar anywhere in the panel.
Tab completes the command you started typing.
? opens this page in a new tab.

In the syntax below, <angle brackets> mark a required argument and [square brackets] an optional one. Tab fills in the required arguments and stops there — an optional argument only ever shows what you typed yourself.

Every command that starts with a name takes it first or last — shop logs and logs shop both work. The table below shows the name-first form.

In the table, <app> is an app’s name. Where a row says so, a database’s name works too. <db> is a database’s name only.

As you type a name, the bar offers only the commands that name has. scale, restart and redeploy are for apps only. Typed with a database’s name, they show an error and send nothing.

The first pattern that matches a line wins.

Deleting an app or a database is not a command. Destructive actions live on the resource’s own Settings page, behind a confirmation dialog.

Every command

Command	Example	What it does	API call
`deploy <image\|git-url> as <name> [port N]`	`deploy nginx:alpine as demo port 80`	Creates the app from a container image or a git repository and starts its first build. The port defaults to 80 for nginx images and 3000 otherwise.	`POST /v1/{project}/apps`
`<app> logs`	`shop logs`	Opens the live log of an app — or of a database, when the name is one.	nothing sent — opens a page
`<app> metrics`	`shop metrics`	Opens CPU, memory, network and restart charts for an app — or a database, when the name is one.	nothing sent — opens a page
`<app> terminal`	`shop terminal`	Opens a shell inside a running pod of the app or database. “shell” works too.	nothing sent — opens a page
`<app> disk`	`shop disk`	Opens the disks of an app or a database. “disks” works too.	nothing sent — opens a page
`<app> settings`	`shop settings`	Opens the settings of an app or a database.	nothing sent — opens a page
`<app> billing`	`shop billing`	Opens what an app or a database has cost so far. “cost” works too.	nothing sent — opens a page
`<db> backups`	`pg backups`	Opens the backups of a database. “backup” works too.	nothing sent — opens a page
`<db> events`	`pg events`	Opens the event history of a database.	nothing sent — opens a page
`<app> scale <replicas>`	`shop scale 2`	Sets how many replicas of the app run.	`POST /v1/{project}/apps/:app/scale`
`<app> restart`	`shop restart`	Rolls the app’s pods, keeping the image that is deployed.	`POST /v1/{project}/apps/:app/restart`
`<app> redeploy`	`shop redeploy`	Builds and deploys the app again from its current source. “deploy” alone works too.	`POST /v1/{project}/apps/:app/deploy`
`<app> open`	`shop open`	Opens the overview of an app or a database. “go” does the same, and the name alone searches.	nothing sent — opens a page
`db <name> <engine> [version]`	`db pg postgres 16`	Creates a managed database. Without a version you get the default one for that engine.	`POST /v1/{project}/databases`
`link <db> to <app>`	`link pg to shop`	Injects the database’s connection variables into the app’s environment.	`POST /v1/{project}/databases/:db/link`
`help`	`help`	Opens this page in a new tab. ”?” works too.	nothing sent — opens a page

<engine> is one of: postgres, pgvector, mysql, mariadb, redis, mongodb, clickhouse, elasticsearch, meilisearch.

Search

Anything you type that isn’t one of the commands above is a search. The bar matches it against the names of your apps and databases (and their status and source), lists what it finds under Recent, and Enter opens the highlighted one. It’s a local filter over the lists the panel already has — no request is made while you type.

Arrow keys move through the list, Enter opens, Escape closes.

MCP and the REST API

Every command here also has an MCP tool and a REST endpoint behind it — the same call, whichever way you trigger it. NSIN CLOUD runs its own MCP server at https://api.nsincloud.ir/mcp, the same way nsin’s MCP server does, and its REST API follows the same conventions: an API key as Authorization: Bearer or X-Api-Key.