Skip to main content
The VibeFlow MCP (Model Context Protocol) server lets any MCP-compatible AI client talk directly to VibeFlow. You can scaffold full-stack projects, manage design systems, and open projects for editing — all without leaving your editor.

​
Available tools

​
Project tools

ToolDescription
initiate_projectBuilds a web app from a plain-text prompt. Handles frontend, backend, database, and auth when needed. Only prompt is required — VibeFlow handles the build.
get_projectPolls the build status of a project using its projectId. Returns one of: queued · provisioning · sandbox_setup · generating · saving · ready · failed
open_project_for_editingReturns a direct editor URL to open an existing project in VibeFlow for review or editing.

​
Design System tools

ToolDescription
get_all_design_systemsLists all design systems in your VibeFlow account. Use this before creating a new one or referencing one in a project.
create_design_systemAnalyzes a workspace and creates a design system from existing patterns, styles, and components. Extracts colors, typography, spacing, and reusable components.
update_design_systemRe-analyzes a workspace and updates an existing design system with the latest patterns and components.
add_component_to_design_systemAdds a reusable component (button, card, form, nav, etc.) to an existing design system.

​
Typical workflow

1. initiate_project  →  kick off a build from a prompt
2. get_project       →  poll until status is "ready"
3. open_project_for_editing  →  get the editor URL to review or modify
For design-system-first projects: 
1. get_all_design_systems          →  pick or confirm a design system
2. create_design_system (if none)  →  generate one from your codebase
3. initiate_project                →  build using the design system

​
Getting your API key

  1. Go to Settings → MCP in VibeFlow.
  2. Click Create API Key to generate your key.
  3. Copy the MCP URL and API Key — you’ll need both when connecting.

​
Transport

FieldValue
TransportStreamable HTTP
MCP URLhttps://tool.vibeflow.ai/mcp
Authentication is passed as a bearer token in the Authorization header: 
Authorization: Bearer YOUR_API_KEY
Any MCP client that supports HTTP transport with custom headers can connect to VibeFlow.

​
Connecting your client

​
Claude Code

Run the following command in your terminal: 
claude mcp add --transport http \
  vibeflow https://tool.vibeflow.ai/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"
Replace YOUR_API_KEY with the key from your Settings page.

​
Cursor

Cursor uses mcp-remote as a bridge for HTTP-based MCP servers. Add the following to your Cursor MCP config (~/.cursor/mcp.json or the MCP settings panel): 
{
  "vibeflow": {
    "command": "npx",
    "args": [
      "-y",
      "mcp-remote",
      "https://tool.vibeflow.ai/mcp"
    ],
    "env": {
      "HTTP_AUTHORIZATION": "Bearer YOUR_API_KEY"
    }
  }
}
Replace YOUR_API_KEY with the key from your Settings page.

​
Other MCP clients

For any other client that supports Streamable HTTP transport, configure it with:
  • MCP URL: https://tool.vibeflow.ai/mcp
  • Auth header: Authorization: Bearer YOUR_API_KEY
Refer to your client’s documentation for how to set custom HTTP headers on MCP connections.

​
Regenerating your API key

Go to Settings → MCP and click the regenerate icon next to your API Key. Your old key is immediately invalidated — update it in your client config after regenerating.