The VibeFlow MCP (Model Context Protocol) server lets any MCP-compatible AI client run the canvas agent end-to-end: list and create canvases, write frames, attach skills, export to PPTX, and more. From your editor. A typical workflow: open a repo in Cursor or Claude Code, point the assistant at your codebase, and have it spin up a canvas branded with your real components, generate a launch deck, and stream theDocumentation Index
Fetch the complete documentation index at: https://canvas-docs.vibeflow.ai/llms.txt
Use this file to discover all available pages before exploring further.
.pptx back to your machine. No browser context-switch.
What you can do via MCP
| Goal | Tools you’d chain |
|---|---|
| Spin up a brand-new canvas and brief it | list_canvases → (none yet) → ask user → run_canvas_agent against a new canvas (created via UI or the broader VibeFlow MCP) |
| Add a frame to an existing canvas | list_canvases → list_canvas_frames → create_canvas_frame |
| Touch up a single frame | list_canvas_frames → get_canvas_frame_code → update_canvas_frame |
| Re-roll a whole frame | get_canvas_frame_code → write_canvas_frame |
| Run the full canvas agent on a brief | run_canvas_agent |
| Export a deck | export_canvas → poll → get_canvas_export |
Getting your API key
The same key works for both canvas tools and the broader VibeFlow MCP (UI projects, design systems, deploys).
Transport
| Field | Value |
|---|---|
| Transport | Streamable HTTP |
| MCP URL | https://tool.vibeflow.ai/mcp |
| Auth | Authorization: Bearer YOUR_API_KEY |
Connecting your client
Claude Code
YOUR_API_KEY with your key.
Cursor
Add to~/.cursor/mcp.json (or via the Cursor MCP settings panel):
Claude Desktop
Add to your Claude Desktop config:Anything else
For any client that supports Streamable HTTP transport:- MCP URL:
https://tool.vibeflow.ai/mcp - Auth header:
Authorization: Bearer YOUR_API_KEY
A prompt to try
Once your client is connected, try this in chat to see the loop end-to-end:list_canvases → run_canvas_agent → export_canvas → get_canvas_export and hand you back a working URL.
Pricing
MCP tool calls bill the same as in-app usage. Therun_canvas_agent tool charges per-turn (token-based, 1-credit minimum). Exports and clone calls have small flat fees. See Credits for the per-tool table.
The MCP doesn’t bypass credit gates. If your account is empty, the tool returns an “insufficient credits” error rather than running.
Regenerating your key
Settings → MCP → regenerate. The old key is invalidated immediately. Update your client config to the new key. If a key is leaked or pushed to a public repo, regenerate immediately.Next
Tool reference
Every canvas tool, signature, and behavior.
Credits
What each tool costs.