Dashboard, CLI or MCP?
The dashboard, the CLI, and the MCP server produce the same outcomes; choose the surface that fits your workflow.
Appo operates your app's publication. You drive that lifecycle from whichever surface fits how you work; the outcomes are the same on all three, and you can switch surfaces at any time.
| Dashboard | CLI | MCP | |
|---|---|---|---|
| What it is | The web interface | appo in your terminal | Your AI assistant, via the Appo connector |
| Fits when | You prefer a GUI | You work in the terminal or CI | You work with an agent |
| Start | apps.goappo.io | npm install -g @appolabs/appo | npx @appolabs/appo mcp |
They share the same account, the same apps and the same operated path: you can create an app from the CLI, publish it from the dashboard, and send a push from your assistant.
The SDK is a separate component: the JavaScript bridge that gives your web code native APIs inside the app. It is not one of these surfaces; it is added when you need native features.