Layovelle

Creating Designs with Claude

Documentation

Legacy. This section documents the original Layovelle MCP server at mcp.moda.app/mcp, built around start_design_task and get_moda_canvas. It is superseded by Layovelle for Agents — the moda CLI wherever your agent has a shell, and the Layovelle connector for claude.ai and other chat hosts. The connector replaces this server, so the tools below retire with it. These pages stay published for existing integrations; start new ones on Layovelle for Agents.
The most popular way to use Layovelle’s MCP server is to create designs by chatting with Claude. Instead of opening a design tool and building layouts by hand, you describe what you want and Claude creates it for you in Layovelle. This works from any Claude environment — the desktop app, the browser at claude.ai, Claude Code in your terminal, or even Claude on mobile. Claude is the primary workflow covered here because it’s the most common for Layovelle design creation. The same MCP tools can also be used from Cursor and other MCP-capable clients, but the exact UX depends on the host app.

How it works

  1. You ask Claude to create a design (a slide deck, social post, ad, report, etc.)
  2. Claude calls the start_design_task tool on the Layovelle MCP server
  3. The tool returns immediately with a task handle and a canvas URL — your design starts building right away
  4. On claude.ai web and Claude Desktop, an embedded progress view shows live updates and rendered pages as the agent works. On other clients, Claude (or any MCP host) polls get_task_status(task_id) to track progress.
  5. Once the design is ready, you can open it, edit it, export it, or ask Claude to revise it
Every design Claude creates is fully editable in Layovelle — you’re never locked into what the AI produces.

Quick setup

If you haven’t connected Layovelle yet, it takes about 30 seconds. Follow the setup guide for your environment (Claude Desktop, claude.ai, Claude Code, Claude mobile, Cursor, or VS Code). Before your first prompt:
  1. In Claude, click the + button in the chat box.
  2. Open Connectors.
  3. Enable Layovelle for the current conversation.
If you belong to multiple Layovelle organizations or teams, ask Claude to switch to the right workspace first:

Example prompts

Here are real prompts you can copy and paste into Claude right now. Be explicit about the output type in every prompt, especially for non-slide work. Phrases like PDF report, Instagram post, diagram, flowchart, or presentation slides help Layovelle choose the right format.

Slide decks and presentations

Social media posts

Marketing and ads

Reports and documents

Diagrams and visuals

Using your brand

Before each new design, Claude asks which brand kit to use: one of your kits, a new one it creates from your website, or none. It asks even when you have only one kit, and it waits for your answer before creating anything. Name a kit in your request (“using the Acme brand kit”) to skip the question. Your brand colors, fonts, logos, and style guidelines are then used without you having to mention them. To use the same kit every time in a Claude Project, add a line like Always use the Layovelle brand kit "Acme" to the project’s instructions. To set up a brand kit from Claude:
Layovelle will scrape your site and extract colors, fonts, logos, and brand guidelines. The first brand kit created for a team becomes the default automatically. If your team already has a default brand kit, you can ask Claude to use the new one explicitly:
You can also ask Claude to check what brand assets are available:

Iterating on designs

Claude remembers the context of your conversation, so you can refine designs with follow-up messages:
Each follow-up modifies the same canvas — Claude tracks the conversation automatically. You don’t need to start over.

Attaching references

You can give Claude reference images, PDFs, or existing Layovelle designs to work from:

Specifying format and dimensions

For best results, tell Claude what kind of design you want: You can also specify exact dimensions:

Exporting your designs

Once Claude creates a design, you can export it directly from the conversation. Under the hood, the MCP flow is:
  1. start_design_task(...) — returns immediately with {task_id, canvas_id, canvas_url, status: 'queued'}
  2. get_task_status(task_id) until can_export == true or the task reaches a terminal failure state
  3. export_canvas(canvas_id=..., format=...)
On claude.ai web and Claude Desktop, the live-progress iframe handles step 2 visually so neither you nor Claude has to wait for the tool to finish before seeing pages render. On hosts without iframe support, Claude polls get_task_status itself. If export is attempted too early, Layovelle MCP returns a structured not_ready response with a retry interval instead of a tool error. Then Claude can export from the conversation:
Supported formats: PNG, JPEG, PDF, PPTX, MP4, and GIF (MP4 and GIF render one page’s animation timeline).

Tips for great results

Usage limits

Your organization has a cap on how many design tasks can run at once. start_design_task and remix_design calls from the MCP server share this cap with your REST API usage. When you hit the cap, the tool returns an error like "Rate limit exceeded: 10/10 concurrent tasks active." Wait for an existing task to finish (poll via get_task_status) and retry. See Usage Limits for the full picture, including how to contact support if you need a higher cap.

What’s next