Skip to main content

​
Overview

The Alpic CLI lets you deploy MCP servers to Alpic from the terminal. Use it to deploy with a single command, create or link projects on first run, and integrate deployments into scripts or CI/CD. Authentication is API key only. Install the CLI globally; npx is also usable if you prefer not to install.

​
Getting started

​
Run the CLI

Install the CLI globally, then run alpic from anywhere: 
npm install -g alpic
# or
pnpm add -g alpic

alpic <command>
You can also run it without installing via npx: npx alpic <command>.

​
Authentication

The CLI requires an API key. Set the ALPIC_API_KEY environment variable before running any command.
1

Get your API key

In the Alpic dashboard, open your team and go to API Keys in the sidebar. Click New API key, name it, and copy the key.
2

Set the environment variable

Export the key in your shell or add it to your CI/CD secrets:
export ALPIC_API_KEY=your_api_key_here
Keep your API key secure and never commit it to version control. If exposed, revoke it in the dashboard and create a new one.

​
Deploy

Deploy your project to Alpic from the current directory or a given path.

​
Usage

alpic deploy
Deploys the current directory. 
alpic deploy ./my-app
Deploys the specified directory (default is current directory).

​
First-time deploy

If the directory is not yet linked to an Alpic project, the CLI will prompt you to:
  • Create a new project — Choose a name, runtime (Node.js 24/22, Python 3.14/3.13), and optional root directory. The project and its Production environment are created and linked.
  • Link to an existing project — Select a project and environment from your team.
The link is saved in .alpic/project.json. Future deploys from that directory reuse this config.

​
What gets deployed

The CLI uses git to determine which files to pack: tracked and untracked files, excluding ignored ones. If the directory is not a git repo, it temporarily runs git init to collect files. Git must be installed. After packing, the CLI uploads a tarball, triggers the deployment, and waits for it to complete (up to 15 minutes). On success, it prints the MCP server URL(s) and elapsed time.

​
Example output

🔗 https://your-env.alpic.live

Completed in 23s

​
Telemetry

The CLI collects anonymous, opt-out telemetry to improve the product. No personal or project data is sent. Telemetry is on by default.
CommandDescription
alpic telemetry enableEnable telemetry (default).
alpic telemetry disableDisable telemetry.
alpic telemetry statusShow whether telemetry is enabled or disabled.

​
Next steps

Alpic API

Use the REST API for programmatic access to projects, environments, and deployments.