Vibe Kanban MCP Server

Vibe Kanban exposes a local MCP (Model Context Protocol) server, allowing you to manage organisations, projects, issues, workspaces, and repositories from external MCP clients like Claude Desktop, Raycast, or even coding agents running within Vibe Kanban itself.

<video controls className="w-full aspect-video rounded-xl" src="https://vkcdn.britannio.dev/vk-mcp-server.mp4"

</video>

Setting Up MCP Integration

Option 1: Using the Web Interface

This works if you're adding the Vibe Kanban MCP server to any supported coding agent within Vibe Kanban.

1. In Vibe Kanban Settings, navigate to the "MCP Servers" page
2. In the "Popular servers" section, click on the Vibe Kanban card
3. Click the Save Settings button

Option 2: Manual Configuration

You can manually add the MCP server to your coding agent's configuration. The exact syntax will depend on your coding agent or MCP client.

Add the following configuration to your agent's MCP servers configuration:

{
  "mcpServers": {
    "vibe_kanban": {
      "command": "npx",
      "args": ["-y", "vibe-kanban@latest", "--mcp"]
    }
  }
}

--mcp launches the local MCP stdio server. Any additional arguments after --mcp are passed through to the vibe-kanban-mcp binary.

Available MCP Tools

The Vibe Kanban MCP server provides tools for managing organisations, projects, issues, workspaces, and task execution.

Context

Organisation Operations

Project Operations

Issue Management

Issue Assignees

Issue Tags

Issue Relationships

Supported relationship types: blocking, related, has_duplicate.

Repository Management

Workspace Management

Workspace Sessions

The repositories parameter is an array of objects with:

• repo_id: The repository ID (UUID)
• branch: The branch for this repository

When issue_id is provided, the workspace is automatically linked to the remote issue. If prompt is omitted, the linked issue's title and description are used as the workspace prompt.

Supported Executors

When using start_workspace, the following executors are supported (case-insensitive, accepts hyphens or underscores):

• claude-code / CLAUDE_CODE
• amp / AMP
• gemini / GEMINI
• codex / CODEX
• opencode / OPENCODE
• cursor_agent / CURSOR_AGENT
• qwen-code / QWEN_CODE
• copilot / COPILOT
• droid / DROID

Using the MCP Server

Once you have the MCP server configured, you can leverage it to streamline your project planning and execution workflow:

1. Plan Your Work: Describe a large feature or project to your MCP client
2. Request Issue Creation: At the end of your description, simply add "then turn this plan into issues"
3. Automatic Issue Generation: Your MCP client will use the Vibe Kanban MCP server to automatically create structured issues in your project
4. Start Workspaces: Use start_workspace to programmatically begin work on issues with specific coding agents

Example Usage

Planning and Issue Creation

I need to build a user authentication system with the following features:
- User registration with email validation
- Login/logout functionality
- Password reset capability
- Session management
- Protected routes

Then turn this plan into issues.

Your MCP client will use the create_issue tool to break this down into individual issues and add them to your Vibe Kanban project automatically.

Starting a Workspace Session

After issues are created, you can start work on them programmatically:

Start working on the user registration issue using Claude Code on the main branch.

Your MCP client will use the start_workspace tool with parameters like:

{
  "name": "User registration with email validation",
  "executor": "claude-code",
  "repositories": [
    {
      "repo_id": "987fcdeb-51a2-3d4e-b678-426614174001",
      "branch": "main"
    }
  ],
  "issue_id": "123e4567-e89b-12d3-a456-426614174000"
}

This creates a new workspace, links it to the issue, generates a feature branch, and starts the coding agent in an isolated environment.

Complete Workflow Example

1. List organisations to find the organisation ID
2. List projects in the organisation to find the project ID
3. List issues in the project filtered by status
4. Create a new issue for "Add user profile page"
5. Assign a team member to the issue
6. Start a workspace session for the issue using Amp on the develop branch

Each step uses the appropriate MCP tool (list_organizations, list_projects, list_issues, create_issue, assign_issue, start_workspace) to manage the complete workflow from planning to execution.

Internal Coding Agents (Within Vibe Kanban)

A powerful workflow involves using coding agents within Vibe Kanban that are also connected to the Vibe Kanban MCP server:

1. Create a Planning Issue: Create an issue with a custom agent profile configured with a planning prompt. See Agent Configurations for details on creating custom profiles.
2. Explore and Plan: The coding agent explores the codebase and develops a comprehensive plan
3. Generate Issues: Ask the coding agent to "create a series of individual issues for this plan"
4. Automatic Population: The agent uses the MCP server to populate individual issues directly in the Vibe Kanban interface

This creates a seamless workflow where high-level planning automatically generates actionable issues in your project board.

Installation Instructions for MCP Clients

Raycast Example

Raycast is a popular MCP client that can connect to Vibe Kanban's MCP server. Here's how to configure it:

For complete Raycast MCP configuration details, see the official Raycast MCP documentation.

Configure the Vibe Kanban MCP server in Raycast by adding the server details. </Tab>

Once configured, you'll see the Vibe Kanban MCP server listed and ready to use in Raycast. </Tab> </Tabs>