Claude & MCP

Hype Flow speaks MCP (Model Context Protocol), so Claude can operate it directly: create projects, build and wire canvases, run nodes and templates, and fetch the results — everything scoped to your account and organization.

Connect claude.ai

In claude.ai, open Settings → Connectors and add a custom connector.
Use the server URL:
```
https://hypeflow.m1au.com/mcp
```
Claude sends you through Hype Flow’s sign-in (OAuth) — approve, and the connector is live.

From then on, any chat with the connector enabled can work your projects:

“Create a project called Autumn Drop, build a prompt → LLM → image-gen chain with Nano Banana Pro, run it, and show me the result.”

Connect Claude Code / other MCP clients

For clients that authenticate with a token instead of a browser flow, create a personal access token in your Hype Flow account settings and configure the client against the same /mcp endpoint with the token as a bearer credential. Treat the token like a password: it acts as you, and it can be revoked from the same settings page.

What Claude can do over MCP

Projects & orgs — list and create projects, inspect membership.
Canvas — list node types, add/update/connect/delete nodes, tidy the layout.
Runs — run nodes and templates, watch generations, regenerate selected collection images.
Assets & library — list, view, and upload assets; manage styles and negatives.
Shots — the storyboard flow: create shots, attach references, set start/end frames, assemble.

Claude sees the same graph you do — changes appear live on the canvas, and everything it does respects your organization’s permissions.

Good patterns

Batch work: “Run the product-shot template once for each of these five photos.”
Scaffold, then refine by hand: let Claude build the graph shape; do the prompt craft yourself on the canvas.
Report back: “List yesterday’s generations in Autumn Drop and give me the three best hero candidates.”