VibeFlow FlowEditor MCP Server

MCP server for managing workflow structure - nodes, connections, and layout.

Features

Tools

• Workflow Management: create, get, update, delete, list workflows
• Node Management: add, delete, move, rename, duplicate nodes
• Connection Management: add, delete, get connections
• Layout: auto-layout nodes, get node positions

Resources

• vibeflow://workflows - List all workflows
• vibeflow://workflow/{id} - Get specific workflow

Prompts

• create_http_workflow - Create a simple HTTP request workflow
• add_code_node_after - Add a Code node after a specific node
• connect_nodes - Connect two nodes in a workflow
• organize_workflow - Organize and layout workflow nodes

Installation

bun install
bun run build

Usage

As MCP Server (STDIO)

bun run src/index.ts

Or use the built version:

node build/index.js

Configuration

Set environment variable:

export CONFIG_API_URL=http://localhost:7575

Claude Desktop Configuration

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "vibeflow-flow-editor": {
      "command": "bun",
      "args": [
        "run",
        "/absolute/path/to/vibeflow/packages/mcp/flow-editor/src/index.ts"
      ],
      "env": {
        "CONFIG_API_URL": "http://localhost:7575"
      }
    }
  }
}

Development

# Run tests
bun test

# Run in development mode
bun run dev

Examples

Create a workflow with HTTP request

// Using the create_http_workflow prompt
{
  "workflowName": "Fetch User Data",
  "apiUrl": "https://api.github.com/users/octocat"
}

Add nodes and connect them

// 1. Create workflow
await callTool('create_workflow', { name: 'My Workflow' });

// 2. Add nodes
await callTool('add_node', {
  workflowId: 'workflow-1',
  type: 'n8n-nodes-base.webhook',
  position: [250, 300]
});

await callTool('add_node', {
  workflowId: 'workflow-1',
  type: 'n8n-nodes-base.code',
  position: [250, 450]
});

// 3. Connect them
await callTool('add_connection', {
  workflowId: 'workflow-1',
  source: 'Webhook',
  target: 'Code'
});

// 4. Auto-layout
await callTool('auto_layout', {
  workflowId: 'workflow-1'
});

Architecture

FlowManager (Business Logic)
  ↓
MCP Server (Tools, Resources, Prompts)
  ↓
Config API (HTTP)

• FlowManager: Pure business logic, fully tested
• MCP Server: Protocol layer, exposes FlowManager via MCP
• Config API: Backend storage (@repo/config)