you › Deploy my app to staging.
hypervibe › Here’s the plan for your review.
+ web service and worker
+ Postgres database
+ staging domain and HTTPS
No changes made. Ready to apply?
you › Apply this staging plan.
✓ approved changes applied
✓ live site responds over HTTPS
hypervibe › Staging is deployed and verified.
Production is unchanged.
you › Is my latest deploy ready to share?
hypervibe › I’ll check the release and the live app.
→ checking serious-app / staging
✓ build and checks passed
✓ web and worker are running
✓ live site responds over HTTPS
hypervibe › The latest release is verified.
Backups haven’t been checked yet.
release 7c92e4a · staging
state ready to share
you › What needs my attention?
hypervibe › I’ll look at the current problems.
→ checking serious-app / staging
✓ latest release is running
! notification delivery failed
sender domain is not authenticated
hypervibe › The app is up. Email needs attention.
Check the sender’s domain setup.
evidence email provider response
changes none made
Illustrative session /Deploy with MCP
01 / two parts, one Hypervibe
Create how you want. Deploy on your terms.
Deploy with the open-source MCP. Monitor with the hosted app.
Open source / MCP + CLI
Bring your own agent. Bring your own cloud.
Plan, deploy, and verify with your coding agent or terminal.
Your infrastructure and provider bills stay in your accounts.
Restart OpenCode, then run opencode mcp list to check that Hypervibe is connected.
Other MCP clients
In your client’s MCP settings, add a local server named hypervibe using the stdio transport and this launch command:
npx -y @hypervibe/hypervibe@latest mcp
If it asks for separate fields, set command to npx and arguments to -y, @hypervibe/hypervibe@latest, and mcp. Restart your client and check its MCP connection status.