@vibezro/mcp

Model Context Protocol server that lets Claude (or any MCP-compatible LLM) manage your Vibezro account — projects, MCP servers, files, deploys, and logs — through 24 first-class tools.

Vibezro is a scale-to-zero hosting platform for MCP servers. This package is the management server — it lets your LLM create projects, deploy code, tail logs, and rotate keys without you ever leaving the chat.

Quick start

# 1. Mint a platform key
open https://app.vibezro.com/platform-keys

# 2. Wire it into your MCP client (see "Client setup" below)
# 3. Restart the client and ask: "list my Vibezro projects"

That's it. The server installs on demand via npx, so there's nothing to install globally.

Where do I get the API key?

The MCP server authenticates with a platform key (prefix vbz_pat_…). Mint one here:

app.vibezro.com/platform-keys

Platform keys are scoped to your account and never expire until you rotate them. Keep them out of version control — feed them to your client via the env var below.

Client setup

Claude Desktop

Edit claude_desktop_config.json:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "vibezro": {
      "command": "npx",
      "args": ["-y", "@vibezro/mcp"],
      "env": {
        "VIBEZRO_API_KEY": "vbz_pat_…"
      }
    }
  }
}

Restart Claude Desktop. You should see a 🔧 indicator with "vibezro" attached.

Claude Code

claude mcp add vibezro -- npx -y @vibezro/mcp
# then set the env var in your shell profile:
export VIBEZRO_API_KEY="vbz_pat_…"

Cursor

~/.cursor/mcp.json:

{
  "mcpServers": {
    "vibezro": {
      "command": "npx",
      "args": ["-y", "@vibezro/mcp"],
      "env": { "VIBEZRO_API_KEY": "vbz_pat_…" }
    }
  }
}

Cline (VS Code)

{
  "mcpServers": {
    "vibezro": {
      "command": "npx",
      "args": ["-y", "@vibezro/mcp"],
      "env": { "VIBEZRO_API_KEY": "vbz_pat_…" },
      "disabled": false,
      "autoApprove": []
    }
  }
}

Generic stdio client

The server is a vanilla MCP stdio server. Anything that speaks MCP can launch it:

VIBEZRO_API_KEY=vbz_pat_… npx -y @vibezro/mcp

Configuration

| Variable | Required | Default | Notes | | ----------------------- | -------- | ------------------------- | ----------------------------------------------------------------------------------------- | | VIBEZRO_API_KEY | ✅ | — | Platform key from app.vibezro.com/platform-keys. | | VIBEZRO_API_URL | ❌ | https://api.vibezro.com | Override for self-hosted or staging environments. | | VIBEZRO_MCP_TRANSPORT | ❌ | stdio | stdio (desktop clients) or http (remote/Smithery-style installs). | | PORT | ❌ | 3030 | Bind port when VIBEZRO_MCP_TRANSPORT=http. Ignored for stdio. |

What can my LLM do?

24 tools across 5 surfaces. All tools are prefixed vibezro_ so they're easy to spot in the agent's tool list.

Projects

• vibezro_list_projects — page through your projects.
• vibezro_get_project — fetch one by id, including MCP counts.
• vibezro_create_project — new project with a slugified name.
• vibezro_archive_project — soft-delete a project + every MCP under it.

MCPs

• vibezro_list_mcps — every MCP under a given project.
• vibezro_get_mcp — one MCP including its current deploy + runtime.
• vibezro_create_mcp — scaffold a new MCP under a project.
• vibezro_update_mcp — change name, runtime, or entrypoint.
• vibezro_archive_mcp — soft-delete.
• vibezro_rotate_api_key — invalidate the old per-MCP key, mint a new one.

Files

• vibezro_list_files — list every file in an MCP's workspace.
• vibezro_read_file — fetch a file's body.
• vibezro_write_file — create or overwrite a single file.
• vibezro_bulk_write_files — upload N files in one round-trip (zip-style bulk).
• vibezro_delete_file — remove a file.

Deploys

• vibezro_deploy — kick off a deploy; returns immediately with a deploy id.
• vibezro_list_deploys — recent deploy history for an MCP.
• vibezro_get_deploy — current state of a single deploy.
• vibezro_deploy_and_wait ⚡ — deploy + stream progress until live/failed (uses MCP progress notifications, cancellable).

Logs

• vibezro_get_logs — pull the last N log lines.
• vibezro_tail_logs ⚡ — live log stream (uses MCP progress notifications, cancellable).

Smart tools

• vibezro_lint_exposed — flags MCPs with private: true that shouldn't be.
• vibezro_suggest_runtime — recommends a runtime based on the file tree (Node vs Python detection).
• vibezro_redeploy_all_dirty — bulk-redeploys every MCP whose code is ahead of its last successful deploy.

⚡ = streaming tool. These emit MCP notifications/progress and honour the client's cancellation signal.

Example prompts

Once wired up, you can drive Vibezro entirely in chat:

"Create a new project called 'weather-bots' and scaffold a node-22 MCP under it."
"Deploy my 'pdf-extractor' MCP and tell me when it's live."
"Tail the logs on 'pdf-extractor' until you see a 200 response."
"List every MCP that's been dirty for more than 24h and redeploy them all."
"Rotate the API key for the 'github-bridge' MCP and update my .env."

Programmatic use (advanced)

Need to embed the server in your own process? The package also ships a public API:

import { createServer, type Logger } from "@vibezro/mcp";

const { server, api, logger } = createServer({
  apiKey: process.env.VIBEZRO_API_KEY!,
  // optional overrides
  apiUrl: "https://api.vibezro.com",
  logger: myCustomLogger satisfies Logger,
});

// Attach any MCP transport you like:
import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
await server.connect(new StdioServerTransport());

Exported names:

• createServer, createApiClient, createLogger, ApiError, TOOLS
• Types: CreateServerOptions, CreatedServer, ApiClient, ApiClientConfig, RequestOptions, Logger, LogLevel, Tool, ToolDeps, ToolResult, ToolStreaming

Troubleshooting

"VIBEZRO_API_KEY is required" — the env var isn't reaching the spawned process. In Claude Desktop / Cursor, env must be inside the server's JSON block, not your shell.

"401 unauthorized" — the key was rotated or revoked. Mint a fresh one at app.vibezro.com/platform-keys.

Tools don't appear — restart your client fully (Claude Desktop caches the tool list on launch). On macOS: cmd+Q, then reopen.

Stuck deploys — call vibezro_get_deploy for the deploy id. If it's been building for >10 minutes, open an issue.

Requirements

• Node.js ≥ 20 (the binary ships as ESM with a #!/usr/bin/env node shebang).
• Any MCP client speaking stdio transport. Tested against Claude Desktop, Claude Code, Cursor, and Cline.

License

UNLICENSED. © Ronniery B. Correa. See LICENSE for terms.

Links

• Vibezro platform: vibezro.com
• Mint a key: app.vibezro.com/platform-keys
• Source: github.com/ronniery/vibezro
• Issues: github.com/ronniery/vibezro/issues
• MCP spec: modelcontextprotocol.io