NEO AppAcme Inc
Portal, CLI, and MCP share the same project state and approval policy.

Developer Tools

Drive NEO from terminal, CI, and AI agents while approval policy stays enforced.

How it works

From source to live

Deployment guide
1
Submit sourceGit integration or neo-app deploy sends source to NEO App.
2
BuildAn isolated builder detects Buildpacks, Nixpacks, or Dockerfile.
3
Ship safelyHealth checks gate rollout and failed releases auto-rollback.
4
LiveServe on *.neoapp.biznetgio.dev or custom domains with automatic TLS.

Preview in staging first. Production deploys, public endpoints, scaling, and paid resources still route through Approvals.

CLI

Common commands

CLI reference
$ npx -y @biznetgio/neo-app@latest agent setupInstall the skill, register MCP, authenticate, and link a project.
$ neo-app statusCheck the connected account, organization, environment, and linked project.
$ neo-app whoami --url https://portal.neoapp.biznetgio.devVerify identity against the current NEO App control plane.
$ neo-app project listList accessible projects and their stable IDs.
$ neo-app link <project-id>Link the current repository to an existing project.
$ neo-app deploy . --project <project-id> --name <app-name> --type webInspect, confirm cost, and deploy the current directory as a web service.
$ neo-app agent doctorDiagnose CLI authentication, API access, MCP registration, and local skill setup.
MCP server

AI agent access

MCP guide

NEO MCP lets approved agents deploy, read logs, scale, and edit variables without bypassing organization policy.

{
  "mcpServers": {
    "neo-app": {
      "command": "npx",
      "args": ["-y", "@biznetgio/neo-app@latest", "mcp"],
      "env": { "NEO_APP_URL": "https://portal.neoapp.biznetgio.dev" }
    }
  }
}
“Deploy api to staging and show the result.”“Show the last 50 error logs for frontend.”“Scale web service to 3 replicas.”“What changed in the latest deployment?”