Agent and terminal workflows
MCP and CLI
MCP and CLI workflows should follow the same public product contracts as Studio, import, publish, and Pulse docs.
MCP and CLI capability guide for Vibecodr agent and terminal workflows.
Implementation focus
Use this when connecting agents, uploading from a terminal, diagnosing CLI import failures, or deciding which actions are safe to automate.
Expected outcomes
- Choose MCP or CLI based on who is acting: an agent or a terminal user.
- Keep upload and publish behavior aligned with Studio contracts.
- Understand why some actions require sign-in, confirmation, or are unavailable.
- Avoid exposing secrets or private storage through automation.
MCP and CLI share product boundaries
MCP is the agent-facing product surface. The CLI is the terminal-facing product surface. Both should help with supported Vibecodr workflows without becoming raw platform administration, secret inspection, storage browsing, or deployment-token access.
Use MCP when an agent needs public context, launch prep, metadata help, or supported signed-in actions. Use the CLI when a terminal workflow needs upload, inspect, import, publish, or status commands that follow the same public contracts as Studio.
- MCP connects through the documented remote endpoint.
- CLI upload and import should surface the same staged upload and build guidance as Studio.
- Neither surface should expose secrets, private storage internals, or privileged platform controls.
- Agents and scripts should prefer product-shaped actions over raw implementation access.
Troubleshoot command workflows
When a CLI upload or publish fails, classify it the same way you would in Studio: auth, file shape, staged upload verification, recipe detection, build output, metadata, or publish permission. This keeps terminal workflows aligned with the web product.
When an MCP action fails, check whether the tool is public-read, signed-in, confirmation-required, or unavailable. Do not assume every product action is safe to automate silently.
- Report command name, route or project id, status, and `errorKey` when available.
- Do not paste tokens or private source bundles into agent prompts.
- Retry only when the error says the action is retryable or when the failed step is idempotent.
Example and read next
Example: a terminal upload fails through the CLI. Classify it like Studio: auth, staged upload verification, recipe detection, build output, metadata, or publish permission before retrying.
Use these related pages when you need the next layer of guidance. They point to the most likely follow-up tasks, not every page that happens to touch the same system.
- Read next: MCP for Agents
- Read next: Import a Project
- Read next: Support Diagnostics
- Read next: Troubleshooting