Skip to main content

MCP Server

The MCP server (vibecontrols-mcp binary, from @vibecontrols/mcp) exposes Vibecontrols and Burdenoff Workspaces capabilities as Model Context Protocol tools for AI assistants like Claude Desktop, ChatGPT desktop, etc.

Install​

npm install -g @vibecontrols/mcp
# or
bun install -g @vibecontrols/mcp

Binary: vibecontrols-mcp

Run​

Stdio transport (typical for Claude Desktop):

vibecontrols-mcp --stdio

HTTP transport (for remote clients):

vibecontrols-mcp --http --port 5555

What it exposes​

The server publishes tools in two groups:

  • Vibecontrols tools — agents, vibes, sessions, vibedecks, webhooks, configurations and the rest of the surface you already know from the CLI.
  • Burdenoff Workspaces platform tools — the shared capabilities your workspace has enabled, such as identity, workspaces and groups, files, tags, conversations, notifications, scheduling, integrations, export, and billing.

Tool names are prefixed with the product they belong to, so tools from different products can be mounted side by side in the same assistant without colliding. Every tool call is made with your token and is permission-checked exactly like the equivalent CLI or API call — an assistant can never do more than you can.

Vibecontrols-specific tools​

They cover the same surface as the CLI — agents, vibes, sessions, vibedecks, webhooks, etc. Browse the live tool list via:

vibecontrols-mcp --list-tools

Claude Desktop integration​

Add to your Claude Desktop config:

{
  "mcpServers": {
    "vibecontrols": {
      "command": "vibecontrols-mcp",
      "args": ["--stdio"],
      "env": {
        "BURDENOFF_TOKEN": "...",
        "WORKSPACE_ID": "..."
      }
    }
  }
}

Source​

Published as @vibecontrols/mcp on npm; source at github.com/algoshred/vibecontrols-mcp.

Next steps​