The 7 Best MCP Servers for Designers and Creatives in 2026 (Ranked for Moodboards, Briefs and Decks)

Key Takeaways

• Storyflow ranks first for planning creative work from an assistant: it is the one server here that writes moodboards, briefs, colour palettes, shot cards and slide decks onto one visual board, and reads back what changed and who changed it.
• Figma's remote MCP server (mcp.figma.com/mcp) ranks second and is the clear first choice for product and UI designers. It reads design context for code and can write native frames, components and variables to the canvas, free during its beta.
• Canva's connector (17 tools in Claude's directory) turns a chat into a finished, exportable design from a template. It does not plan the project around that design.
• Adobe for creativity bundles 50+ tools from Photoshop, Illustrator, Firefly, Express, Premiere, Lightroom, InDesign and Stock into Claude, with about 40 tools open to guests.
• Miro's MCP server works on every Miro plan, with daily tool-call limits from 100 (Free) to 10,000 (Enterprise).
• The rating weights are published below. Planning output and read-back count for 45 percent, because a designer's assistant is only as useful as the board it can see.
• Storyflow is paid-only during early access (Plus from $7.99 a month billed annually). Collaborators a paid member invites join free and get 25 MCP actions a week; Plus, Pro and Max have no MCP limit.
• Milanote is not ranked: its pricing page lists no AI features, and we found no Milanote MCP server or connector on 9 October 2026.

What an MCP Server Does for a Designer (and What It Does Not)

You already plan half your projects in a chat window. The client brief goes into Claude, the moodboard directions come back as a bulleted list, and then you spend forty minutes rebuilding that list as a board, a palette and a deck in three other tools. The assistant did the thinking. You did the typing.

An MCP server closes that gap. The Model Context Protocol is the open standard that lets an assistant such as Claude, ChatGPT, Gemini or Grok call another product's tools. You add the product's server address once, sign in, and from then on the assistant can read what is in that product and, if you allow it, change it.

It moves the output out of the chat

The practical change is where the work lands. Without a server, everything the assistant writes lives in a scrolling transcript you have to copy out. With one, the assistant writes directly into the product: a Figma frame, a Canva design, a Storyflow board, a Notion page. The transcript stops being the deliverable.

It gives the assistant something to read

The second change matters more on long projects. A server with good read tools lets the assistant start from what is already there: last week's moodboard, the palette you settled on, the notes the client added to the board. That is the difference between an assistant that asks you to paste the brief again and one that says "the client moved the warm direction to the top on Tuesday".

It does not replace the design tool

No server on this list makes the assistant a designer. Figma's server writes frames, but you still judge the layout. Canva's connector fills a template, but taste is still yours. Storyflow's server builds the planning board, but it does not draw a logo, retouch a photo or produce a vector file. Pick servers for the job they do, then keep doing the part only you can do.

Remote servers are the ones designers should use

Most servers here are remote: hosted by the vendor, reached over HTTPS, signed in with OAuth. You paste one address and never touch a terminal. Local servers that run on your machine exist (Figma has a desktop one for specific enterprise cases), but for chat clients such as claude.ai and ChatGPT, remote is what works.

How We Ranked These MCP Servers

Most "best MCP servers" lists rank by GitHub stars or tool count. Neither tells a designer anything useful. A server with 67 tools that cannot hold a project together is worse for planning than one with 30 that can. So we ranked on the jobs a designer or creative lead actually hands an assistant: plan the project, build the reference material, show it to a client, and pick up next week where it stopped.

We read each vendor's own documentation and pricing page on 9 October 2026 and scored each one against six weighted criteria.

Why planning output carries the most weight

A designer's week is not mostly pixels. It is briefs, references, directions, feedback and decks. Those are the artifacts an assistant can draft well, and the ones that cost the most time to rebuild by hand.

Why read-back is second

An assistant that can only write produces a pile. One that can read the board, and see who moved what, can maintain a project. That is the property that makes an MCP server worth connecting for a three-month brand project instead of a one-off.

Why we did not score image quality

Image generation quality depends on the model behind each tool and changes month to month. We scored what the server lets the assistant do with your project, not how pretty a generated picture is.

MCP Servers for Designers Compared

Storyflow leads on planning output and read-back. Figma leads on anything that ends as an interface or code. Canva and Adobe lead on finished assets. The right server is the one whose product already holds the thing you hand the client.

The 7 Best MCP Servers for Designers and Creatives, Reviewed

Each review follows the same shape: the verdict, who it is for, what it costs, why it ranks where it does, strengths, limits. Facts about other vendors come from their own pages, linked inline, read on 9 October 2026.

1. Storyflow

Verdict: the MCP server that turns an assistant conversation into a planned creative project on a visual board.

Best for: art directors, brand designers, studio leads and freelancers who plan client work in Claude or ChatGPT and present it as a board.

Pricing: Plus $7.99 a month billed annually ($9.99 monthly), Pro $14 ($19 monthly), Max $39 ($49 monthly). Storyflow is paid-only during early access; its Free plan launches before the end of 2026, and anyone a paid member invites to a board joins free now. See pricing.

Storyflow is a visual project planning workspace: an infinite canvas board that holds notes, tables, documents, images, moodboards, storyboards, mind maps, kanban, charts and slide decks. Its MCP server puts that board inside any assistant that can add a remote MCP server. You paste one address, https://mcp.storyflow.so/mcp, sign in, and choose which projects the assistant may use and whether it may change anything.

Why it ranks first: it is the only server here built around the planning artifacts a designer hands a client. Ask Claude for three moodboard directions and you get them as grouped walls of pictures on the board, because the add_images tool downloads images from addresses the assistant found or you pasted and keeps Storyflow's own copy, so the board survives dead links. Ask for the brand palette and create_color_palette lays out swatches with names, hex and RGB values. Ask for the pitch and create_deck builds slides on the same board. Ask for a storyboard (the same job as the AI storyboard generator in the app) and create_shot_cards builds a row of shot cards, each with its frame, direction and equipment notes. Then, a week later, get_board_changes tells the assistant what changed on the board and who changed it.

The read side is what separates it from a generator. The assistant can list your projects and boards, read board elements, documents and files, search, and summarise a board before it adds anything. That makes the second session useful: "rework the moodboard around what the client moved on Tuesday" starts from the board, not from a pasted transcript.

It also reaches chat apps, not only coding tools. Storyflow documents setup for Claude, ChatGPT, the Gemini app, Grok, Claude Code, Cursor, VS Code with GitHub Copilot, Gemini CLI, Codex, Devin, Figma, Zed, Raycast, Lovable, Perplexity and Le Chat. Figma is on that list as a client: with a Full seat on a paid Figma plan, Figma can add Storyflow as an MCP connector and read your planning board.

Strengths

• Writes the full planning set in one place: notes, groups, tables, documents, colour palettes, shot cards, strip boards, mind maps, charts, diagrams, carousel pages and slide decks, plus board templates.
• Reads back boards, documents, files and the board's change history with the person who made each change.
• What the assistant adds appears live on an open board, and show_board displays the board inside clients that support MCP apps.
• Permissions are chosen at sign-in: all projects or picked ones, read-only or allowed to change, documents outside projects on or off.
• Runs on your assistant's model, so it spends no Storyflow AI credits. Plus, Pro and Max have no MCP limit.

Limits

• It is not a design tool. No vector editing, no UI design, no retouching, no code export.
• Browser only: no mobile or desktop apps and no offline mode.
• Paid-only during early access. Invited free accounts get 25 actions a week, and every read and change counts as one.
• A photo attached in the chat does not reach Storyflow. The assistant calls request_photo_upload and hands you an upload link instead.
• Connections expire after 30 days and ask you to sign in again.

Try it: the connection guide has the steps for each assistant.

2. Figma MCP Server

Verdict: the server every product and UI designer should connect first, and the strongest design-to-code bridge available.

Best for: product designers, design system teams and designers who hand off to developers using Cursor, Claude Code or VS Code.

Pricing: the remote server is available on all seats and plans. Figma's pricing page lists MCP tool-call limits of 20 calls a month on Starter, 200 a day (10 a minute) on Professional, 200 a day (15 a minute) on Organization and 600 a day (20 a minute) on Enterprise. A Professional Full seat is $16 a month.

Figma's guide to its MCP server describes a remote server at mcp.figma.com/mcp that gives agents design context (variables, components, layout), generates code from selected frames, retrieves FigJam and Make resources, links components to code through Code Connect, and turns live web UI into editable Figma layers. Through the remote server and supported clients, agents can also create and modify frames, components, variables and auto layout in Figma Design and FigJam. Figma says canvas writing is free during the beta and will later become a usage-based paid feature.

Why it ranks second: for interface work nothing else comes close, and it scores well on read-back because it reads real design context, not screenshots. It ranks below Storyflow on this list because its strength is the interface, not the project around it. A brand refresh brief, three moodboard directions and a client presentation deck are not what Figma's server is built to produce, and its listed clients lean toward coding tools rather than chat apps.

Strengths

• Reads variables, components and layout so generated code matches the design system.
• Writes native, editable content to the canvas in Design and FigJam (beta).
• Long list of supported clients, including Claude Code, Claude Desktop, Codex, Cursor, VS Code, Gemini CLI, Android Studio and Xcode (beta).

Limits

• Starter's 20 tool calls a month is a trial, not a working allowance.
• Canvas writing support varies by client and will become usage-based after the beta.
• Built for interfaces; moodboards, briefs and pitch decks are not its job.

3. Canva AI Connector

Verdict: the fastest route from a chat to a finished, exportable social or marketing design.

Best for: social designers, content teams and marketers who produce templated assets at volume.

Pricing: we could not load Canva's pricing or help pages on 9 October 2026, so we do not quote a plan requirement here; check your plan in Canva before connecting.

Claude's directory listing for Canva describes a connector built by Canva and verified by Anthropic, added in November 2025, that can "search, create, autofill, and export Canva designs." It lists 17 tools, including search-designs, get-design, export-design, generate-design, create-folder and add-comment-thread-to-design. The server address is mcp.canva.com/mcp, and sign-in is required.

Why it ranks third: when the deliverable is a post, a poster or a carousel built from a template, Canva's connector gets you there in fewer steps than anything else here. It ranks below Storyflow and Figma because it works one design at a time. It does not plan the campaign those designs belong to, and its read side is limited to finding and reading your designs.

Strengths

• Generates and autofills real Canva designs you can keep editing by hand.
• Exports designs straight from the chat.
• Can leave comment threads on a design, useful for review rounds.

Limits

• One design at a time; no project board, brief or moodboard around it.
• Plan requirements were not verifiable on Canva's site during our check.
• Template-led output, which is the point for social work and a constraint for brand exploration.

4. Adobe for Creativity

Verdict: the broadest creative toolset inside Claude, best for edits you would otherwise open Photoshop or Express to make.

Best for: photographers, social designers and video editors who want quick retouches, resizes and reformats without leaving the chat.

Pricing: Adobe's getting started guide says any Claude plan works (Free, Pro, Max, Team, Enterprise), with some features on paid Claude plans only. Guests get about 40 standard tools; signing in with an Adobe account adds more tools, Creative Cloud storage, higher limits and work that persists across sessions.

Adobe announced the connector on 28 April 2026, with 50+ tools from Photoshop, Illustrator, Firefly, Express, Premiere, Lightroom, InDesign and Stock. Adobe's examples are retouching portraits (lighting, background blur, straightening, cropping), designing social assets from Express templates, and reformatting horizontal video for Shorts and Reels. Claude's directory listing adds Acrobat, shows 67 tools and lists PDF editing, background removal and resizing for social formats.

Why it ranks fourth: it is the strongest execution layer here for photo and video work, and it needs no Adobe subscription to try. It ranks below Canva for designers because its output is edited files rather than designs you keep building on, and its documented clients are Claude web, Claude Desktop and Cowork, so ChatGPT and Gemini users are not covered by Adobe's setup guide.

Strengths

• Widest app coverage: eight Creative Cloud apps plus Acrobat in Claude's listing.
• Usable as a guest with about 40 tools.
• Batch photo edits and social reformatting from one prompt.

Limits

• Adobe's guide documents Claude only.
• Edits files; it does not plan or hold the project.
• Some capabilities need a paid Claude plan, and plugins need one too.

5. Miro MCP Server

Verdict: the right server when your team's whiteboards already live in Miro.

Best for: design teams that run workshops, journey maps and diagrams in Miro.

Pricing: Miro's MCP documentation says the server works on all plans, including free teams. Daily limits are 100 calls on Free, 500 on Starter, 2,000 on Business and 10,000 on Enterprise, resetting at 00:00 UTC. Miro's pricing page lists Starter at $8 per member a month and Business at $20, billed yearly, with Free limited to 3 editable boards.

Miro describes the server as a bridge between AI agents and boards: summarising and searching boards, building boards, generating diagrams and acting on comments. Its tools page shows the current approach: the assistant reads board items as SVG and writes them back as SVG (canvas_create_from_svg, canvas_update_from_svg), with table tools marked as deprecating soon. Install paths are documented for Claude, ChatGPT and Codex, Claude Code, Cursor, Gemini CLI and VS Code.

Why it ranks fifth: it is a strong team whiteboard server with honest, published limits, and reading comments is useful for review. It ranks below Storyflow for creative planning because it builds generic board items and diagrams rather than moodboards, palettes, shot cards and decks, and below Canva and Adobe on finished output.

Strengths

• Free plan access with a published 100 calls a day.
• Reads and lists comments, so the assistant can act on feedback.
• Broad, documented client support including ChatGPT.

Limits

• Free plan keeps only 3 boards editable.
• SVG-based writing suits diagrams more than visual reference boards.
• Table tools are marked as deprecating.

6. Notion MCP

Verdict: the server for studios whose briefs, wikis and project databases already live in Notion.

Best for: studio operations, writers and designers who keep briefs in pages and databases.

Pricing: Notion's pricing page lists Plus at $10 per member a month billed annually ($12 monthly) and Business at $20 ($24 monthly), with a free plan. Its MCP documentation states no plan requirement.

Notion's MCP setup guide gives the address mcp.notion.com/mcp over Streamable HTTP, with an SSE fallback. After OAuth, a client can search Notion and connected sources, read, create and update content you can access, and create pages and databases. File uploads through the server are capped at 20 MiB. Documented clients include Codex, Claude Code, Cursor, VS Code with GitHub Copilot and Devin.

Why it ranks sixth: for text-shaped planning (a brief, a project database, a wiki) it is excellent. It ranks below the visual tools because a designer's plan is mostly pictures, palettes and sequences, and a Notion page holds those as a document rather than as a board you arrange.

Strengths

• Mature read and write across pages and databases.
• Workspace owners manage and revoke MCP access in Settings.
• Documented for most major coding clients.

Limits

• Document-shaped output, not a visual board.
• 20 MiB cap on file uploads through the server.
• No palette, storyboard or deck tooling.

7. Webflow MCP Server

Verdict: the server for web designers who build and run live sites in Webflow.

Best for: web designers and studios that ship client sites on Webflow.

Pricing: requires a Webflow site; some features need add-ons or Enterprise, per Webflow's MCP documentation.

Webflow's documentation describes a server that lets agents create and edit elements, styles, components, interactions, custom code, fonts and design system variables, and manage CMS collections and items, pages, assets, forms, SEO metadata and comments. Visual snapshots and anything tied to the current selection, page or breakpoint need the Webflow Designer open with the Bridge App connected. Each authorization covers one workspace, analytics need the Analyze add-on on paid site plans, and page branches need Enterprise. Documented clients are Claude Code, Claude Desktop, ChatGPT, Codex and Cursor.

Why it ranks seventh: it is excellent at its job, which is the site, and narrow for everything before it. Planning a site's direction, references and client presentation is upstream work this server does not do.

Strengths

• Deep site control: elements, styles, CMS, SEO.
• Respects existing Webflow roles and cannot change access settings.
• Works in ChatGPT as well as Claude.

Limits

• Designer-dependent features need the Bridge App running.
• One workspace per authorization.
• No planning or reference tooling.

Worked Example: A Brand Refresh From a Claude Chat to a Client Board

Rankings are abstract. Here is an illustrative project, a brand refresh for a 12-person coffee roaster, run through Claude with the Storyflow server connected and laid out step by step so you can see which tools an assistant calls and what they count against. The numbers are an example, not a measurement.

The setup

The designer is a freelance brand designer on Storyflow Plus. The client sent a two-page brief as a PDF. The designer uploads that PDF to the Storyflow project once (files on the board are readable by the assistant), then opens Claude and writes one message: "Read the brief in the Roastery project. Build a refresh board: a one-page summary of the brief, three moodboard directions of 9 pictures each, a 6-colour palette per direction, and an 8-slide presentation for Thursday."

What the assistant did

On Plus there is no MCP limit, so the 14 actions cost nothing beyond the subscription. If the client's in-house designer, invited free, ran the same request from their own Claude, it would use 14 of their 25 weekly actions.

The second session is where it pays off

On Tuesday the client's in-house designer, invited to the board, drags direction two to the top and moves two pictures aside, while the marketing lead opens the view link with no account and signs in to comment. On Wednesday the designer asks Claude: "What changed on the refresh board this week, and who changed it?" One get_board_changes call answers with the moves and the name of the person who made them. A second message, "Move the two pictures set aside into a Parked group and rebuild slides 3 to 5 around direction two", becomes a handful of move_element, group_into_walls, remove_deck_slides and add_deck_slides calls. No brief re-pasted, no screenshots.

The same job without a planning server

For comparison, the same Monday in a chat-only workflow: Claude writes the summary and three directions as text, the designer searches and drags 27 pictures into a board by hand, types 18 hex values into swatches, and builds 8 slides in a separate presentation tool. Every Tuesday change has to be described back to the assistant in words. The assistant's work is the same; the rebuilding is the time sink the server removes.

Prompts You Can Copy for Each Server

Good MCP prompts name the place, the artifact and the size. Vague prompts ("make me a moodboard") make the assistant guess where to write and how much. These are written to be pasted as they are, with your own project names swapped in.

Chain servers in one conversation

Assistants can call more than one connected server in a single conversation. A practical chain for a campaign: plan the campaign on the Storyflow board and agree it with the client there, then ask Canva to autofill the social templates from the board's captions, then ask Adobe to reformat the hero video for Reels. Each server does the step it is best at, and the plan stays on the board.

What It Costs: Pricing and Limits for Each MCP Server

No vendor here charges separately for its MCP server today (Figma says canvas writing will become usage-based after its beta). What you pay for is the product account behind it and, in some cases, a metered allowance of tool calls. You also need an assistant that can add the server.

The assistant side

Claude's pricing page lists connectors on the Free plan, and Pro at $20 a month (or $17 a month billed annually). On Claude Free you can add one custom connector, which is enough to try Storyflow. ChatGPT needs Plus or above for custom servers, added through developer mode.

Three realistic stacks

• Freelance brand designer: Claude Pro plus Storyflow Plus. Planning, references, palettes and decks on one board; client views by link.
• Product designer: Claude or Cursor plus Figma Professional. Add Storyflow if you also run discovery boards and stakeholder decks.
• Social content team: ChatGPT or Claude plus Canva, with Storyflow Max ($39 a month annual) when the team needs a shared workspace with roles for the plan.

Which Stack Fits Your Design Work

The question is not which server is best in the abstract. It is which product already holds the thing you hand over at the end of the job. Use these rules in order and stop at the first one that fits.

If you present plans, directions and decks to clients

Connect Storyflow. Your deliverable is a board and a presentation, and that is what its server builds and reads back. The AI mood board maker and creative direction deck pages show those two artifacts inside Storyflow. Add Canva or Adobe for the finished assets once a direction is approved.

If your deliverable is an interface or a design system

Connect Figma first. No other server reads design context and writes native frames. Use Storyflow for research, moodboards and stakeholder decks upstream if you run that work outside Figma.

If you produce social assets from templates at volume

Connect Canva. Autofill and export are the steps that eat your day, and its connector does both.

If most of your time goes on photo and video edits

Connect Adobe for creativity in Claude. Guest access lets you test it before deciding whether to sign in.

If your team already lives in Miro or Notion

Connect the server for the tool you already pay for. The best server is often the one whose data is already there. Add Storyflow when you need moodboards, palettes, storyboards and decks rather than sticky notes or pages.

If you build and maintain client sites

Connect Webflow for the site itself, and plan the site direction on a board before the build starts.

How to Connect Storyflow in Under Five Minutes

Every assistant uses the same address: https://mcp.storyflow.so/mcp. Storyflow speaks Streamable HTTP, not SSE. The full steps live in the help article; these are the four you will use most.

Claude

Open Customize, then Connectors. Click Add, then Add custom connector. Name it Storyflow, paste the address, click Continue, choose Sign in now, click Add, and sign in to Storyflow. Claude's Free plan allows one custom connector.

ChatGPT

In ChatGPT on the web, open Settings, then Security and login, and turn on Developer mode (on Business and Enterprise an admin does this). Go to chatgpt.com/plugins, click the plus button, name it Storyflow, choose Public endpoint, paste the address, create it and sign in. You need ChatGPT Plus or above.

Gemini and Grok

In the Gemini app, open Settings, then Connected Apps, then Custom apps, and Add a custom app; it needs a personal Google account with Keep Activity on, in the US, 18 or over, in English. In Grok, open grok.com/connectors, click New Connector, then Custom, paste the address and sign in; on Grok Business and Enterprise an admin adds it in the xAI console first.

Claude Code and Cursor

In Claude Code, run claude mcp add --transport http storyflow https://mcp.storyflow.so/mcp in your terminal, then run /mcp inside Claude Code to sign in. In Cursor, add Storyflow as a remote server with the same address in your MCP settings, then sign in when asked.

Choose the permissions on purpose

At sign-in Storyflow asks which projects the assistant may use (all or picked), whether it may make changes (otherwise it only reads), and whether it may use documents outside projects. For client work, pick only that client's project. Disconnect any time in Settings, then Connected apps; access ends within a minute.

Common Mistakes When Designers Add MCP Servers

Most disappointment with MCP servers comes from setup, not from the servers. These are the patterns that waste the first week.

Connecting every server at once

Each connected server adds tools the assistant has to choose between. With seven connected, a request like "make a board" is ambiguous. Connect the two or three you use weekly, and name the product in the prompt when more than one could do the job.

Giving write access to every project

Storyflow lets you connect read-only. For a client's live project, start read-only until you trust the prompts, then reconnect with changes allowed for that one project.

Attaching a photo and expecting it on the board

On Storyflow, a picture you drop into the chat stays in the chat. The assistant gives you an upload link through request_photo_upload. Pictures the assistant finds online or that you link by address go on the board directly through add_images.

Asking for a moodboard without a size

"Make a moodboard" produces whatever the assistant guesses. "Three directions, 9 pictures each, one-line rationale per direction" produces something you can present. The numbers do the art direction.

Treating the first output as final

The server makes iteration cheap. Ask for three directions, kill one, push another. The second and third passes, informed by what is already on the board, are where the quality comes from.

Forgetting the 30-day expiry

Storyflow connections end after 30 days and ask you to sign in again. If the assistant suddenly cannot see a project, that is the first thing to check, followed by whether you picked that project at sign-in.

When Storyflow Is Not the Right Choice

Storyflow ranks first on this list because the criteria are about planning creative work. On other jobs it is the wrong server, and you should know which before you connect it.

You design interfaces or systems

Use Figma's server. Storyflow does not edit vectors, build components, manage variables or export code. Its board can hold your UX research and stakeholder deck, but the design itself belongs in Figma.

You need finished, export-ready assets

Use Canva or Adobe for creativity. Storyflow plans the social carousel or the campaign; it does not produce print-ready files, retouch photos or reformat video.

You need formal approvals, publishing or scheduling

Storyflow does not publish or schedule social posts, and it has no approve button or versioned proofing. Clients view the board by link and sign in to comment, which works for feedback, not for a signed-off approval trail.

You work offline or on a phone

Storyflow is browser only, with no mobile or desktop apps and no offline mode.

You want a free tool today

Storyflow is paid-only during early access; its Free plan launches before the end of 2026. Miro's free plan with 100 MCP calls a day, Notion's free plan and Figma's Starter are free today.

You weigh vendor tenure above everything

Storyflow is a newer product with a shorter track record and a smaller template ecosystem than Figma, Adobe, Canva, Miro or Notion.

Servers We Checked and Left Out

A list is only as credible as what it excludes. These were checked and did not make the ranking.

Milanote

Milanote is a well-loved moodboard tool, but its plans page lists no AI features, and we found no Milanote MCP server or connector on 9 October 2026. Its free plan covers 100 notes, images or links and 10 file uploads; paid is $9.99 per person a month billed annually ($12.50 monthly). If Milanote ships a server, it would compete directly with Storyflow for moodboards.

Framer

We found several community-built Framer MCP servers but no official one published by Framer. Community servers can work, but they run outside the vendor's support and permissions model, so we did not rank them.

Local community servers for desktop apps

There are open-source servers that drive desktop design apps through a local plugin. They suit developers comfortable with a terminal. For chat apps like claude.ai and ChatGPT, which reach only remote servers, they are the wrong starting point.

A Template: The Design Project Board Your Assistant Builds

Use this layout as the instruction you give the assistant on the first day of a project. It is the board structure that makes later sessions useful, because every piece has a predictable place to read from.

Paste this as your first prompt: "Set up a project board for [client] with these sections: Brief, References, Palette, Structure, Sequence, Plan, Presentation. Fill Brief from the attached document and leave the others as labelled empty groups." Then fill each section in its own message. The assistant reads what is there before it adds to it, so each step builds on the last.

For a designer-specific starting point, the moodboard for designers page and the design brief page show the same board structure inside Storyflow.

The Bottom Line

Pick the MCP server whose product holds what you hand over at the end. For designers and creative leads who plan in ChatGPT or Claude and hand clients a board, a set of directions and a deck, that is Storyflow: one address, the brief, references, palettes, storyboards and slides on one board, and an assistant that reads the board's history before it builds. For interfaces, connect Figma. For templated assets, Canva. For photo and video edits, Adobe. Connect Storyflow to your assistant and ask it to build your next client board.