Skip to main content
Package and deploy an MCP server project to Alpic. The command collects source files, uploads them, and waits for the deployment to complete before printing the server URL.

​
Usage

alpic deploy
Deploys the current directory. Prompts for any missing configuration (project name, runtime) if not already set.

​
Extended Usage

Skip all prompts (useful in CI): 
alpic deploy --non-interactive --project-name my-app --runtime node24
Create and deploy a new project whose app root is a monorepo subdirectory (path is relative to the directory where you run the command): 
alpic deploy --project-name my-app --root-dir ./packages/my-mcp-server
--root-dir is passed through the same linking flow as alpic link: it only applies when this run creates a new Alpic project. For an already linked directory, the app root was set at link/create time. Import environment variables from a .env file when creating a new project: 
alpic deploy --project-name my-app --runtime node24 --env-file .env

​
Options

FlagDescription
--non-interactiveSkip all confirmation prompts
--runtimeRuntime to use: node24, node22, python3.14, python3.13
--root-dirRelative path to the app root for builds and deployments; only when creating a new project (omit for repository root)
--project-nameName for a new project
--team-idTeam ID
--project-idProject ID to deploy to directly
--environment-idEnvironment ID to deploy to directly
--env-filePath to a .env file to source environment variables from (new projects only)
Project names can be renamed. For CI/CD pipelines, prefer --project-id to avoid breakage.
Authentication is required. Run alpic login or set ALPIC_API_KEY before deploying.