VibeFlow MCP - VibeFlow Canvas

The VibeFlow MCP (Model Context Protocol) server turns any MCP-compatible AI client into your content operator: load your workspace’s business context and learned preferences, write LinkedIn and X posts, upload photos, brief the VibeFlow design agent for graphics, and schedule or publish — from your editor, your agent, or Claude itself. A typical workflow: open a repo in Claude Code, tell the assistant “draft a LinkedIn post about the feature we just shipped”, and it loads your workspace context, writes the copy in your voice, has the design agent produce a graphic, attaches it, and puts the post on your calendar once you say when. No browser context-switch. Setup instructions per client live on Connect your agent.

What you can do via MCP

Goal	Tools you’d chain
Learn the ropes (do this first)	`get_content_guide` → `get_canvas_guide`
Load the workspace	`list_organizations` → `get_workspace_context`
Draft a post	`create_post` → `get_post` → `flag_post_gaps`
Edit the copy	`get_post` → `update_post_variant`
Put real photos on a post	`request_upload_url` → PUT the file → `set_post_photos`
Have the design agent make a graphic	`create_canvas_frame` → poll `get_canvas_frame_creation` → `screenshot_canvas_frames`
Put that graphic on a post	`set_post_graphic` (grid or LinkedIn carousel)
Put it on the calendar	`schedule_post` / `publish_post` / `unschedule_post`
Ask what content works	`get_content_analytics` → `get_top_posts`
Compare against competitors	`list_competitors` → `get_competitor_analysis` / `get_competitor_evidence`
Teach it your voice	`remember` / `forget`
Export standalone graphics	`export_canvas` → poll → `get_canvas_export`

Full reference on VibeFlow MCP tools.

Transport

Field	Value
Transport	Streamable HTTP
MCP URL	`https://tool.vibeflow.ai/mcp`
Auth	OAuth 2.1 (default) or `Authorization: Bearer` API key

Any MCP client that supports Streamable HTTP can connect. Streaming is preserved end-to-end.

OAuth (recommended)

There is nothing to create, copy, or rotate. Point your client at the MCP URL with no auth headers:

Add the server

Give your client the URL https://tool.vibeflow.ai/mcp. Per-client steps: Connect your agent.

Approve access

On first use your browser opens VibeFlow’s consent page. Sign in and click Allow access.

Done

Your client stores the OAuth tokens and refreshes them automatically. Revoke anytime by removing the connector in your client.

The server implements OAuth 2.1 with dynamic client registration and PKCE — the flow Claude’s connector directory and ChatGPT both require — so it works out of the box in clients that support remote MCP OAuth.

API key auth

For scripts, CI, or clients without OAuth support, a personal key works everywhere a header does.

Open Settings

Create an API key

Switch to the API key tab and click Create API key. The key starts with vf_mcp_….

Send it as a bearer header

Authorization: Bearer vf_mcp_…

Both auth modes resolve to the same account and the same tools — OAuth tokens expire and refresh on their own; API keys live until you regenerate them under Settings → MCP. If a key leaks or lands in a public repo, regenerate immediately — the old key dies instantly.

A prompt to try

Once your client is connected, try this in chat to see the loop end-to-end:

Load the VibeFlow content guide and my workspace context. Draft a
LinkedIn post about the release we shipped this week — pull the
details from this repo's changelog. Have the design agent make one
graphic for it, attach it, and show me the post. If I like it, I'll
tell you when to schedule it.

A good MCP client will chain get_content_guide → get_workspace_context → create_post → create_canvas_frame → get_canvas_frame_creation → set_post_graphic → get_post, then wait for your explicit yes before schedule_post.

Pricing

MCP tool calls bill the same as in-app usage. Post drafting, editing, scheduling, and uploads carry no agent charges; the create_canvas_frame design-agent tool charges per-turn (token-based, 1-credit minimum), and exports 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.

Connect your agent

Claude, Claude Code, Cursor, Codex, OpenClaw, Hermes — step by step.

Tool reference

Every tool, signature, and behavior.

​What you can do via MCP

​Transport

​OAuth (recommended)

​API key auth

​A prompt to try

​Pricing

​Next