Skip to main content
Deploy and manage projects from your terminal. Requires Node.js 22 or newer.

​
Install and log in

Open the sign-in link printed by login. Use the organization ID returned by whoami. If signup asks for an invitation, use the link you received.

​
Prepare your app

Run these commands in your GitHub repository:
Choose a unique request key for project creation. Link your repository, review the plan for the exact pushed commit, then deploy. Reuse the same request key if a response is interrupted. Your agent can handle this workflow with the GitHub deployment Skill. Isolated data gives Dev and Prod separate databases; each uses credits. Shared data uses one database for both. Keep your application’s existing authentication choice.

​
Check progress

Use the operation ID returned by deploy to follow progress. Dev links are private; ask your agent to open a Dev access link before testing.

​
Save a token for your agent

From your interactive login:
Tokens default to 90 days. The command saves the newly issued value to the private file; it cannot be retrieved again later. Ignore the file in Git. Existing credentials are not overwritten. Load it into your agent process using Node’s —env-file option. Use token revoke —help to revoke a selected key from your interactive login. Release manifest and checksums · MCP setup · API reference