Vibe MCP Server

NPX wrapper around vibe-kanban and vibe-kanban-mcp

Local serverstdio

What is the Vibe MCP server?

Vibe MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. NPX wrapper around vibe-kanban and vibe-kanban-mcp.

What you get

In a world where software engineers spend most of their time planning and reviewing coding agents, the most impactful way to ship more is to get faster at planning and review.

What the assistant can call

Once Vibe is connected, these are the calls the assistant has available:

  • Variable — Type
  • POSTHOG_API_KEY — Build-time
  • POSTHOG_API_ENDPOINT — Build-time
  • PORT — Runtime
  • BACKEND_PORT — Runtime
  • FRONTEND_PORT — Runtime
  • HOST — Runtime
  • MCP_HOST — Runtime
  • MCP_PORT — Runtime
  • DISABLE_WORKTREE_CLEANUP — Runtime
  • VK_ALLOWED_ORIGINS — Runtime
  • VK_SHARED_API_BASE — Runtime

Configuration and credentials

You will need one environment variable: POSTHOG_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

  • Rust (latest stable) - Node.js (>=20) - pnpm (>=8) Additional development tools: Install dependencies:

Setting it up

vibe-kanban on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Vibe's toolset — Variable, POSTHOG_API_KEY, POSTHOG_API_ENDPOINT and 11 more — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Vibe.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the vibe mcp server does with a few real requests.

Available tools

ToolWhat it does
VariableType
POSTHOG_API_KEYBuild-time
POSTHOG_API_ENDPOINTBuild-time
PORTRuntime
BACKEND_PORTRuntime
FRONTEND_PORTRuntime
HOSTRuntime
MCP_HOSTRuntime
MCP_PORTRuntime
DISABLE_WORKTREE_CLEANUPRuntime
VK_ALLOWED_ORIGINSRuntime
VK_SHARED_API_BASERuntime
VK_SHARED_RELAY_API_BASERuntime
VK_TUNNELRuntime

How to install the Vibe MCP server

{
  "mcpServers": {
    "kanban-1": {
      "command": "npx",
      "args": ["-y", "vibe-kanban"],
      "env": {
        "POSTHOG_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • Rust (latest stable) - Node.js (>=20) - pnpm (>=8) Additional development tools: Install dependencies:
VariableDescriptionRequired
POSTHOG_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Vibe to Variable.
  • Use Vibe to POSTHOG API KEY.
  • Use Vibe to POSTHOG API ENDPOINT.

Frequently asked questions

It connects Vibe to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (Variable, POSTHOG_API_KEY, POSTHOG_API_ENDPOINT, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Vibe directly.