Skip to main content
Create a submission package for one of your environments. Alpic reads the environment’s deployed MCP server, lists its tools, and prefills every field it can infer, so the package comes back already populated. The environment must have a successful deployment, and its MCP server must not require authentication, because Alpic cannot read the tools of a server it cannot connect to.

​
Usage

Without an environment flag, you are prompted to pick a project and an environment; --platform is prompted for too.

​
Extended Usage

Target an environment explicitly:
Resolve the environment by name:
Print the created package as JSON, ready to pipe into alpic submission update:
Creating a package also starts a Beacon audit of the environment, so the readiness checks are ready by the time you review the package.

​
Options