Vibeflow

What Vibeflow MCP server does

The Vibeflow MCP server exposes Vibeflow’s task store and Kanban workflow as MCP tools. Tasks can represent bugs, features, enhancements, research, or general work, with statuses from backlog through done and priorities from Critical to Low.

The browser overlay adds UI context to tasks. A user can click an element and create a ticket containing its CSS selector, URL, and source location. The overlay also supports screenshots, task indicators, an open-task sidebar, and real-time synchronization over WebSocket. This makes the server suitable for small UI fixes, layout problems, and other work where the affected element is easiest to identify visually.

How it works

Start Vibeflow’s Kanban board with the CLI, then inject the overlay into the application using a bookmarklet, script tag, or DevTools console. The /inject page provides the integration snippets. After an element is annotated, an agent can use the Vibeflow MCP server to retrieve the task and its related files or comments.

Task listing returns root tasks by default. Child tasks can be requested explicitly, while direct lookup can resolve either a root or child task. The claim operation selects the highest-priority root task whose status is todo, changes it to in-progress, and includes information about its children without changing their statuses.

Agents can move tasks through the workflow, add comments, attach base64-encoded files, and export one or more tasks as a formatted LLM prompt. A verification tool runs visual verification for annotated tasks. The project tool reports the resolved project, including its root, branch, and mode.

Setup and configuration

Install the CLI globally with:

npm install -g @vibeflow-tools/cli

Start the board for the current directory with vibeflow kanban, or provide a project directory such as vibeflow kanban ./my-project. The start_kanban MCP tool starts the local Kanban board server and returns its URLs.

For HTML files or prototypes, vibeflow serve . starts a server with the annotation overlay. A single file can be supplied instead, and -p changes the port. Running vibeflow serve without a target uses API-only mode for an existing hosted application. The overlay can also be added to a page through the generated bookmarklet, script tag, or DevTools instructions.

The provided material does not specify MCP client configuration, required environment variables, or a license. Telemetry is managed separately through the CLI and can be disabled with vibeflow telemetry --disable; the README states that task content is not collected and that user identity is hashed.

Tools and capabilities

The Vibeflow MCP server provides tools for:

• Listing filtered root tasks or including children
• Retrieving a task with comments and files
• Reading the attached project’s root, branch, and mode
• Creating and editing tasks, including status, title, links, and verification verdict
• Claiming the next eligible root task
• Adding comments and attaching base64-encoded files
• Exporting tasks as an LLM prompt
• Running visual verification for annotated tasks
• Starting the Kanban board and retrieving integration instructions

The task store also supports file attachments through the board and CLI. A Markdown attachment satisfies the research-report gate described by the tool behavior. The overlay includes the Alt+A shortcut for toggling annotation mode and uses Shadow DOM for its panel.