Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.melius.com/llms.txt

Use this file to discover all available pages before exploring further.

The Melius MCP integration lets Claude (and other agentic AI tools) build canvases for you. Instead of opening Melius and clicking around, you brief Claude in natural language — referencing your project files, brand docs, and product details — and Claude assembles the canvas, writes the prompts, chooses the models, and kicks off generations. For marketers doing creative ops at scale, this is the single biggest productivity unlock on the platform. It also runs asynchronously: brief Claude from your phone during a meeting, get a Melius link back when the canvas is built.

​
What you can do with Melius + Claude

A few patterns we see across customers:
  • Daily/weekly briefs. Drop a brief into Claude every Monday morning — Claude builds the canvas, generates the variants, pings you when it’s done.
  • End-to-end campaign builds. Brief Claude with the campaign concept; Claude reads your brand docs, builds the canvas with character sheets + clip nodes + voiceover + stitch, and hands you a finished video draft.
  • Brand-consistent automation. Claude reads your brand anchor on every run, so the outputs stay on-brand without you re-pasting context.
  • Cross-canvas reuse. Claude can find existing projects and canvases by name, reuse references, and link work across canvases.

​
Setup

You’ll need: a Melius team account and Claude (or another MCP-capable client).
1

Open Claude and add a custom connector

In Claude.ai: Settings → Connectors → Add custom connector. In Claude Desktop: Customize → Connectors → Add (+) → Custom. Name it Melius.
2

Paste the Melius connector URL

https://mcp.melius.com/mcp
Hit Add.
3

Sign in with Melius

Claude opens a Melius login page. Sign in (or use your existing session), pick the team you want Claude to work in, and click Authorize. Melius creates a connector key for Claude on your behalf — no API key to create or paste. Claude is connected immediately.
4

Open a new Claude chat and confirm the connection

You should see Melius listed in Claude’s available tools. Try a quick brief: “Show me the projects in my Melius account.” If Claude returns your project list, you’re connected.
The connection is scoped to the team you picked during sign-in. If you want Claude to work in a different team, add a second Melius connector and pick that team during authorize. To disconnect at any time, go to Team settings → Integrations & MCP in Melius — find the claude-…-mcp key Melius created during authorize and delete it.
Already connected via api.melius.com/mcp with an API key? That still works — see the MCP server docs for both paths.

​
How to brief Claude

The general pattern: tell Claude what you’re working on, point it at your reference material, and tell it where to build. Claude handles model selection, prompt writing, and canvas assembly. A working brief looks like: 
I'm working on a new performance video for [brand].

Use the [Creative Brief PDF] and the [brand.md] from this project to
understand the brand voice, persona, and visual style.

In Melius, on the [Brand] project, create a new canvas called "Live
Demo". On that canvas:
1. Create a character sheet for the persona using GPT Image 2 (Medium),
   based on the attached reference image.
2. Generate 3 UGC video clips (9x16, 720p, Seedance 2.0) — opening, body,
   close — using the character sheet as the reference image for each.
3. Reference the brand brief and creative brief in every clip's prompt.
Claude reads the briefs, pulls the brand voice, finds the existing Melius project, creates the canvas, builds out the nodes with prompts written from the brief, and kicks off the generations. You can watch it work in Claude’s terminal-style output, or come back when it’s done.

​
How to structure your Claude projects

This part matters for team workflows. Claude has two surfaces — Claude Chat projects and Claude Cowork — and they have different sharing properties:
  • Claude Chat projects. Shareable across team members. Project files (your brand anchor, your creative briefs) are visible to everyone on the project. Use this when multiple people brief Claude on the same brand or campaign.
  • Claude Cowork. Solo, not shareable. Good for individual workflows, deep research, longer-running tasks. Not the right home for shared brand docs.
The pattern most agencies use: one Claude Chat project per client, with the brand anchor (brand.md) and creative guidelines as project files. The whole team briefs Claude on that project, and Claude has the brand context every time without you re-pasting it. Inside Melius: one Melius project per client matches the Claude project. The team folder structure aligns: Claude project “[Brand]” → Melius project “[Brand]” → all canvases live there.

​
Skills (advanced)

Claude Skills (the Markdown-based skill files in Claude Chat) can encode repeatable workflows — “build a UGC ad in Melius,” “produce static variants for a launch,” etc. We don’t currently bundle Melius-specific skills, but customers have built their own that work well. If you build a useful skill — for an agency-internal workflow, a specific campaign type, a brand template — we’d love to see it. Send it in the Slack channel and we’ll feature good ones.

​
What asynchronous looks like in practice

The MCP path is built for async work. Some patterns we see:
  • Phone-to-laptop handoff. Brief Claude from your phone in an Uber. Claude builds the canvas in the background while you’re in your next meeting. Come back to your desk, open the Melius link, review and ship.
  • Slack-as-brief. Some teams brief Claude through a Slack workflow — /brief triggers a Claude run that drops a Melius link in the channel when it’s done.
  • Scheduled runs (cron). Set Claude up to run a creative production task on a schedule — e.g. every Monday morning, build the weekly variant batch and ping the design lead with the canvas link.
The common thread: the work moves to where the work happens — your phone, your Slack, your inbox — instead of requiring you to open Melius first.

​
Common pitfalls

  • Re-pasting brand context every time. If you’re doing this, you haven’t set up a Claude project with your brand docs as project files. Set it up once; every future brief inherits it.
  • One Claude project for everything. Hard to manage, brand context bleeds across clients. One project per client.
  • API key from the wrong team. If Claude can’t find your projects, you probably generated the API key while a different team was active in Melius. Re-generate from the right team.
  • Asking Claude to do the whole thing in one prompt with no context. Even with the MCP, Claude works best when you point it at specific reference material. Drop your brief and reference images in the chat the same way you would on the Melius canvas.
Once your MCP setup is solid, you’ll find yourself opening the Melius web app less — most briefing happens in Claude, and you only open Melius to review and tweak. That’s the intended end state.
Last modified on May 29, 2026