Vibe-coded apps built with Claude Code, Cursor, or Windsurf deploy to production in under 5 minutes using the OSC MCP server. Connect your AI agent once, then deploy databases, app hosting, and 200+ open source services through natural language — no Kubernetes, no cloud config. The agent that wrote your app can also ship it. You just need to give it the right infrastructure tools.
This is the gap vibe coding exposed: the build is instant, the deploy is not. Claude can scaffold a full-stack app with a Postgres-backed API and authentication in under 10 minutes. Then you spend the next hour provisioning the database, setting environment variables, wiring the connection strings, and debugging TLS. The creative work automated, the mechanical work manual. Open Source Cloud (OSC) closes that gap by giving your AI agent direct access to infrastructure tools through MCP.
What is vibe deployment?
Vibe deployment is the natural extension of vibe coding: you let the same AI agent that built your app also ship it. Instead of stopping at "here's your code," the agent provisions the database, deploys the application, sets the environment variables, and hands you a live URL — all in the same conversation. The infrastructure decisions happen through tool calls, not through config files you write and run yourself.
The term is new, but the idea is straightforward: if an agent can write the code, it should be able to run it too.
Prerequisites
One command. That's it.
For Claude Code, run:
claude mcp add --transport http osc https://mcp.osaas.io/mcp
The first time you use an OSC tool, Claude Code will open a browser window for OAuth authentication. If you don't have an OSC account yet, you can create one there — no separate signup step required.
For Claude Desktop, Cursor, Windsurf, and other MCP-compatible tools, the OSC MCP page has one-step connection instructions for each.
Step-by-step: deploy a vibe-coded app via Claude Code
Say you've built a Node.js app with a PostgreSQL backend during a vibe coding session. Your agent wrote the code. Now you want it live. Here's how the conversation goes.
Step 1: Ask the agent to provision a database
You: I need a PostgreSQL database for this app. Can you provision one on OSC?
The agent calls the OSC MCP create-service-instance tool with serviceId: "eyevinn-postgres". Within about 30 seconds, it gets back a connection string using the instance's port-mapped host and port:
Agent: Done. Your PostgreSQL instance is running.
Connection string: postgres://user:password@<host>:<port>/myapp
I've stored it in the OSC parameter store under "DATABASE_URL".
Step 2: Deploy the app
You: Now deploy the app. Source is github.com/yourname/your-app
The agent calls create-myapp with your GitHub repo URL and attaches the parameter store containing DATABASE_URL:
Agent: Deploying from github.com/yourname/your-app...
Build complete. Your app is live at:
https://yourapp-abc123.apps.osaas.io
Step 3: Wire a custom domain (optional)
You: Map it to api.myproject.com
The agent calls the domain-mapping tool, creates the DNS record, and Let's Encrypt TLS is provisioned automatically.
Step 4: Verify it's running
You: Check the app status and show me the last 20 lines of logs
The agent queries the instance health and fetches logs — no terminal, no cloud console, no context switch.
Step 5: Done
From "I need a database" to a live, TLS-terminated, custom-domain app: four exchanges. The agent handled every infrastructure decision. You stayed in the conversation.
What you can deploy
OSC exposes 200+ open source services through MCP. The categories your agent can provision in a single session:
Databases
PostgreSQL, MariaDB, CouchDB, ClickHouse, MongoDB, MySQL — all fully managed, all open source.
Caching and queues
Valkey (Redis-compatible), SmoothMQ (SQS-compatible). One tool call, connection string back.
Storage
S3-compatible object storage (MinIO). Your agent can create a bucket, get credentials, and wire them to your app without leaving the conversation.
App hosting
Deploy any GitHub repo running Node.js, Python, or WASM. Environment variables wired via the OSC parameter store. Custom domains with automatic TLS.
Intelligence
The OSC Architect tool — an AI that helps your agent design multi-service architectures before it starts provisioning. Ask it to plan before you build.
The full catalog: osaas.io/mcp.
No lock-in — take your code anywhere
Other platforms deploy to their infrastructure. You write your app against their APIs, their managed runtimes, their proprietary services. When agents make infrastructure decisions at speed, you can end up locked into vendors you didn't consciously choose.
OSC deploys to open source. Every service your agent provisions is an open source project:
- PostgreSQL is actual PostgreSQL
- Storage is MinIO-compatible S3
- Caching is Valkey — the Redis fork maintained by the Linux Foundation
- App hosting runs on open source container runtimes
That means you can take any component — or the entire stack — and run it yourself on AWS, GCP, bare metal, or your own Kubernetes cluster. The connection strings work the same. The data is yours.
When your AI agent is making infrastructure choices for you, open source is your insurance policy.
What this looks like at scale
The production benchmark: Streaming Tech TV+, a streaming platform built in 36 hours by one developer directing 6 AI agents. 15,000+ lines of code, 99 commits, 13 OSC services in the final stack — PostgreSQL, two Valkey caches, MinIO, video transcoding, HLS packaging, Whisper subtitles, ClickHouse analytics. The agents didn't just write code. They provisioned every service and wired every connection.
That's the endpoint. Your next vibe coding session is the starting point.
Try it
- Run
claude mcp add --transport http osc https://mcp.osaas.io/mcp(or connect your tool of choice) - Authenticate via OAuth — account creation is part of the flow if you're new
- Start a new session, ask your agent to build and deploy something
The next time you vibe code an app, you don't have to stop when the code is done.
Open Source Cloud provides 200+ open source projects as managed services with native MCP integration. Every component is open source — zero vendor lock-in. Revenue is shared with the creators of the open source projects that power the platform.
Top comments (0)