yuuno-mcp

# yuuno-mcp MCP server for [yuuno.tech](https://app.yuuno.tech) **adflow** — drive the node-based AI media canvas from an MCP client (Claude Code, Claude Desktop, Cursor, …). You become an agent on the board: create sessions, wire up image/video/audio/text generation nodes, run flows, and read results — the same canvas the in-app chat edits, so your changes appear live in the browser. ## Get an API key Mint a workspace key at **app.yuuno.tech → Settings → Organization → API** (`https://app.yuuno.tech/settings/organization/api`). It's a 40-character hex string scoped to your workspace. Rotating it (Reset) invalidates the previous key for every connected client in that workspace. ## Connect ### Claude Code Local (stdio, recommended — works everywhere): ```bash claude mcp add yuuno -e YUUNO_API_KEY=<your-40-hex-key> -- uvx yuuno-mcp ``` Hosted (Streamable HTTP — no local install): ```bash claude mcp add --transport http yuuno https://mcp.yuuno.tech/mcp \ --header "Authorization: Bearer <your-40-hex-key>" ``` ### Claude Desktop Add to `claude_desktop_config.json` (stdio; Desktop connectors don't pass custom headers, so use stdio): ```json { "mcpServers": { "yuuno": { "command": "uvx", "args": ["yuuno-mcp"], "env": { "YUUNO_API_KEY": "<your-40-hex-key>" } } } } ``` ### Cursor Add to `~/.cursor/mcp.json` (or a project `.cursor/mcp.json`): ```json { "mcpServers": { "yuuno": { "url": "https://mcp.yuuno.tech/mcp", "headers": { "Authorization": "Bearer ${env:YUUNO_API_KEY}" } } } } ``` Cursor also supports stdio (`"command": "uvx", "args": ["yuuno-mcp"]`). > **Client support note:** remote (hosted HTTP + `Authorization` header) works > today in Claude Code and Cursor. Claude Desktop and claude.ai custom > connectors don't pass static headers — use stdio (`uvx`) for Desktop; OAuth > for claude.ai is a later release. ## First moves for the agent Call **`get_cheatsheet`** once at the start of a session —…