Skip to main content

First Deployment

Deploy your first artifact using vibeD's MCP tools.

Using Claude Desktop​

Option A: HTTP Transport (Remote / In-Cluster)​

If vibeD runs as a service (e.g. deployed to your Kind cluster), use mcp-remote to bridge Claude Desktop's stdio to vibeD's HTTP endpoint.

Add this to your Claude Desktop configuration (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{
  "mcpServers": {
    "vibed": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "http://vibed.127.0.0.1.sslip.io:9090/mcp/",
        "--allow-http"
      ]
    }
  }
}
Prerequisites
  • Node.js 20+ must be installed (for npx)
  • The vibeD MCP endpoint must be reachable from your machine — see Port-Forward Access if running on a local Kind cluster

Option B: Stdio Transport (Direct)​

Run vibeD as a local process that Claude Desktop launches directly:

{
  "mcpServers": {
    "vibed": {
      "command": "/path/to/vibed",
      "args": ["--config", "/path/to/vibed.yaml"]
    }
  }
}

This starts vibeD in stdio mode. The binary needs access to a Kubernetes cluster via your local kubeconfig.

Deploy Your First Artifact​

Ask Claude to deploy a simple website:

"Create a simple portfolio website with my name and deploy it using vibeD"

Claude will use the deploy_artifact tool automatically. Static HTML/CSS/JS files deploy instantly via ConfigMap (no container build needed). More complex apps (Node.js, Python, Go) are built via Buildah.

Using MCP Inspector​

For testing, use the MCP Inspector:

npx @modelcontextprotocol/inspector ./bin/vibed --config vibed.yaml

Then call the deploy_artifact tool with:

{
  "name": "hello-world",
  "files": {
    "index.html": "<!DOCTYPE html><html><body><h1>Hello from vibeD!</h1></body></html>"
  }
}

Using the HTTP API​

If vibeD is running in HTTP mode, you can call the MCP endpoint directly via Streamable HTTP:

# 1. Initialize session
curl -X POST http://localhost:8080/mcp/ \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{
    "protocolVersion":"2025-03-26","capabilities":{},
    "clientInfo":{"name":"curl","version":"1.0"}}}'

# 2. Use the Mcp-Session-Id header from the response for subsequent calls

Check the Dashboard​

After deploying, open http://localhost:8080 to see your artifact in the dashboard with its status and access URL.