How to Connect Claude to Your Project Board (2026): Claude, Claude Desktop and Claude Code, Step by Step

Key Takeaways

• Of the five boards compared here, Storyflow is the one Claude can build the most on: notes, groups, tables, charts, diagrams, mind maps, documents, slide decks, shot cards and strip boards, placed where they belong on one canvas, and it reads who changed what on the board.
• Connecting takes one address and one sign-in. In Claude on the web or desktop: Customize, Connectors, Add, Add custom connector, name it Storyflow, paste the address, Continue, Sign in now, Add.
• In Claude Code it is one terminal command plus /mcp, and connectors you already added on claude.ai show up in Claude Code automatically when you log in with a Claude subscription.
• Permissions are set at Storyflow's sign-in, not in Claude: which projects, whether Claude may change anything, and whether it may use documents outside projects. Claude then asks you to approve tool calls on top of that.
• Claude's Free plan allows one custom connector. Claude Code needs Pro or above.
• Storyflow's paid plans (from $7.99 a month billed annually) have no MCP limit; a free account invited by a paid member gets 25 actions a week. Asana, Notion, Linear and Miro all ship their own MCP servers, and Miro publishes daily call limits by plan.
• The connector runs on Claude's model, so it does not spend Storyflow AI credits.
• Storyflow is not the right board for engineering issue tracking (Linear), company-wide task assignment (Asana) or a $0 setup today: it is paid-only during early access.

What Connecting Claude to a Project Board Actually Does

You have a plan in your head, a brief in a Google Doc, and a long Claude conversation where the two finally made sense. Then you copy the result into your board by hand, one card at a time, and by Thursday the board and the chat disagree. Connecting Claude to the board removes the copying step. Claude reads the board you point it at, writes to it directly, and the next conversation starts from what the board says rather than from what you remember.

The connection runs on MCP, the Model Context Protocol, the open standard Claude uses to talk to other apps. A board tool that runs an MCP server publishes a list of tools (read this board, add a table, build a deck), and Claude decides which to call while it works on your request. You do not write code. You add one web address, sign in to the board tool, and approve what Claude may do.

It is not a sync. It is a set of actions Claude takes on your behalf, one tool call at a time, with your permission. That distinction matters for three reasons:

• Claude only sees what it reads in that conversation. It does not keep a mirror of your workspace.
• Every write is a call you can see and approve, so a bad instruction shows up before it lands.
• The quality of the result depends on which tools the board exposes. A server that can only create tasks gives you tasks, however good the plan in the chat was.

That last point is why the choice of board matters more than the setup. Claude is the same model whichever server you connect. What changes is what it is allowed to build.

What Claude can do on a Storyflow board once connected

Storyflow is a visual project planning workspace for creative work: an infinite canvas board that holds notes, tables, documents, images, moodboards, storyboards, mind maps, kanban, charts and slide decks. Through its MCP server, Claude can:

• Read your boards, notes, documents and files, and see what changed on a board and who changed it.
• Build notes, groups, tables, charts, diagrams, mind maps, documents, slide decks, shot cards, strip boards, colour palettes and carousel pages, and apply board templates.
• Edit and move elements, remove deck slides and clear table cells.
• Create a new project when you allow all your projects.

What Claude adds appears live on the board if you have it open in another tab, so you can watch the plan arrive and correct it in the same minute. The full list of what the server does is on the Storyflow MCP page. If you want the same result without Claude, Storyflow's built-in AI does the brief to project board and document to project board jobs inside the app.

Before You Start: What Each Claude Surface Needs

Claude reaches your board from three places, and each one has its own requirement. Check this table before you start so a plan limit does not stop you halfway through.

On the Storyflow side you need a Storyflow account, because you sign in with it when you connect. 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. An invited free account can use the connector with a 25-action weekly allowance, which is covered in the cost section below.

One custom connector on Claude Free: spend it deliberately

Claude's Free plan allows exactly one custom connector. If you are on Free and want to test Storyflow alongside another custom server, you will have to remove one to add the other. Connectors you pick from Claude's own directory (Notion, Asana, Linear, Miro and monday.com are all listed in the Claude connectors directory) are added differently; Storyflow is added as a custom connector by its address.

How to Connect Claude to a Storyflow Board, Step by Step

The address every Claude surface uses is the same: https://mcp.storyflow.so/mcp. Storyflow speaks Streamable HTTP, the current standard transport, and does not serve the older SSE transport. You can also copy the address from Settings, then Storyflow MCP, inside Storyflow, next to the exact steps for each tool. The help article on connecting AI assistants carries the same steps with screenshots of the Storyflow side.

Step 1: Add Storyflow in Claude on the web or desktop

1. In Claude, open Customize, then Connectors.
2. Click Add, then Add custom connector.
3. Name it Storyflow, paste https://mcp.storyflow.so/mcp and click Continue.
4. Choose Sign in now, then click Add.
5. A Storyflow sign-in window opens. Sign in with your Storyflow account.

Claude's own form offers more options than you need here. Its help article lists authentication choices (Sign in now, Sign in when needed, No sign in), an OAuth client option and request headers for fixed credentials. For Storyflow, Sign in now is the right choice: the server uses a normal sign-in, so you do not paste keys or client secrets anywhere.

Step 2: Choose what Claude may touch, on Storyflow's sign-in screen

This is the step that decides how safe the connection is, and it happens in Storyflow, not in Claude. Storyflow asks three questions:

1. Which projects Claude may use: all of your projects, or only the ones you pick.
2. Whether Claude may make changes. If you say no, Claude can only read.
3. Whether Claude may also use your documents outside projects: your private documents and the ones shared with you. This starts on when you allow all projects and off when you pick projects, and you can change it either way.

If Storyflow does not recognise the app asking to connect, it shows a warning and you tick I trust this app before you can continue. For claude.ai and Claude Desktop you should see Claude named. If you see a name you did not expect, stop and check what you are connecting.

Step 3: Turn the connector on in the chat

Connectors can be switched on and off per conversation. In a chat, click the plus button at the lower left, choose Connectors and make sure Storyflow is toggled on. Claude's help article also describes a Search and tools menu where you can disable individual tools you do not want Claude to use. If you only ever want Claude to read in a given chat, you can switch off the write tools there as a second line of defence, on top of the read-only choice you made at sign-in.

Step 4: Approve the first tool calls

The first time Claude calls a Storyflow tool, it asks you to approve it. Claude's help center advises using Allow always only for servers and tools you trust to run unsupervised. A sensible pattern is to allow the read tools (list projects, list boards, read board elements, board summary, board changes) always, and approve write tools one at a time until you have watched a few land on the board the way you expected.

Storyflow labels each tool as read-only or as a change, and marks the ones that overwrite or replace existing content (tools whose names start with update, replace, write, set, clear, remove or convert) as destructive. Read the tool name in the approval prompt: a create call adds something new; a write or update call can change what was already there.

Step 5: Connect Claude Code

If you plan in the terminal, or you want Claude Code to update the launch board while it ships the feature, add Storyflow there with one command:

claude mcp add --transport http storyflow https://mcp.storyflow.so/mcp

Then run /mcp inside Claude Code, pick storyflow and follow the browser sign-in. The same three permission questions appear. Claude Code's MCP documentation explains the scope flag that decides who else gets the server:

For a personal planning board, the default local scope or user scope is right. Use project scope only if everyone who clones the repository should be offered the board connection; each person still signs in to Storyflow with their own account, so nobody inherits your access.

There is a shortcut. If you log in to Claude Code with a claude.ai subscription, connectors you already added at claude.ai show up in Claude Code automatically and appear in /mcp marked as coming from claude.ai. You may not need the command at all. Claude Code's documentation lists claude mcp list to see every configured server, claude mcp get storyflow for one server's details, and claude mcp remove storyflow to remove it, which also deletes the stored sign-in.

Step 6: Connect for a whole organisation on Claude Team or Enterprise

On Claude's Team and Enterprise plans, members cannot add a custom connector alone. An Owner or Primary Owner opens Organization settings, then Connectors, clicks Add, chooses Custom, then Web, and enters the Storyflow address. On Enterprise, people with a custom role that includes Manage access to Libraries can also add connectors. Members then find Storyflow in Customize, Connectors (usually labelled Custom) and click Connect.

Each member signs in to Storyflow with their own account and makes their own permission choices. That is the right default for a studio or agency: Claude can only reach the projects each person can already reach in Storyflow, and a freelancer you invited to one client board does not see the others.

Step 7: Send a first prompt that proves it works

Start with a read, not a write. Try: "List my Storyflow projects, then summarise the board in the one called Spring Launch." Claude should call the tool that lists projects, then the one that lists boards in that project, then read the board. If that works, you have a working connection, correct permissions and the right project in scope. Then try a small write on a test board before you let Claude near a client board. A launch roadmap or a product launch plan is a good first real job, because it has dates, owners and a budget Claude can lay out.

How We Ranked Project Board Connectors for Claude

Most connector round-ups rank by brand recognition. That does not help you, because Claude is the same model whichever server you connect. What changes is what Claude can read, what it can build, and what you can stop it doing. We ranked five board tools that publish an official MCP server Claude can use, scored only on what each vendor documents on its own pages as of October 9, 2026. If a capability is not documented, it scores low, even if it might exist.

The job we ranked for: a founder, producer or creative lead who plans visual, deadline-driven work (a launch, a campaign, a shoot) and wants Claude to turn a brief into a working board and keep it current.

We scored each criterion from 1 to 5 and multiplied by the weight. The weighting is published so you can reweight it: if setup effort matters most to you, Storyflow drops, because it is a custom connector rather than a directory pick.

Two notes on fairness. Linear scores 5 on permissions because it publishes a dedicated read-only server address, which is the cleanest read-only switch of any tool here. Storyflow scores 3 on setup because it takes a custom connector form rather than a one-click directory install, and on Claude Free that form uses your only custom slot.

Claude Project Board Connectors Compared (2026)

Read the table by the column that matches your job. If Claude's output should be a board you can present (a plan with a budget chart, a deck and the open questions side by side), the build column decides it. If Claude's output is a list of tickets for engineers, Linear's narrower tool set is exactly right.

The 5 Project Boards You Can Connect to Claude, Ranked

1. Storyflow

Verdict: the board Claude can build the most on, for visual creative and launch planning.

Best for: founders, producers, agencies and creative leads who want Claude to turn a brief into a presentable board.

Pricing: Plus $7.99 a month billed annually ($9.99 monthly), Pro $14 annual ($19 monthly) with AI image generation, Max $39 annual ($49 monthly) with a team workspace, roles and permissions. See pricing. No MCP limit on any paid plan.

Storyflow ranks first because its MCP server exposes the widest set of building tools of any board here, and they all land on one canvas. When you ask Claude to "turn this launch brief into a board", it can create the project, lay out the plan as grouped notes, put the task list in a table with dates in date cells, add a budget chart, draw a dependency diagram and build a slide deck next to the plan, placing each where it belongs. It can also read what changed on a board and who changed it over the last day, week or month, which turns "what moved this week?" into one question instead of a tour of every card.

The permission model is the other reason. You decide at sign-in which projects Claude may see, whether it may change anything, and whether it may touch documents outside projects. The connector has no tool for deleting board elements outright, though it can edit and move elements, remove deck slides and clear table cells, so approve those calls with care.

Strengths:

• The widest build range here: tables, charts, diagrams, mind maps, documents, decks, shot cards, strip boards, colour palettes and carousel pages.
• Reads board change history, including who made each change.
• Per-project access and a read-only choice at sign-in.
• Runs on Claude's model, so it does not spend Storyflow AI credits, and paid plans have no MCP limit.
• Works with the other assistants you may use too: ChatGPT, Gemini, Grok, Cursor and more, on the same address.

Limitations:

• Added as a custom connector, so on Claude Free it uses your one custom slot.
• Paid-only during early access; the Free plan launches before the end of 2026.
• Browser only: no desktop or phone app of its own and no offline mode.
• A photo you attach in the Claude chat does not reach Storyflow; Claude gives you an upload link for the board instead.

2. Miro

Verdict: the closest alternative for whiteboard-style boards, strongest for engineering diagrams.

Best for: teams already on Miro, product and engineering teams that diagram systems.

Pricing: Free with 3 editable boards; Starter $8 per member a month billed annually; Business $20 per member a month billed annually (Miro pricing).

Miro's MCP server lets Claude read and summarise boards, create and update content, generate diagrams from code or text and read and resolve comments, according to Miro's MCP FAQ. Supported items include frames, sticky notes, shapes, text, cards, docs, tables, images from public URLs and generated architecture, sequence and entity diagrams. You authorise one Miro team at a time, and a board in another team returns an error. On Enterprise, an admin must enable MCP first; it is off by default.

Strengths:

• Broad item support and diagram generation from code.
• Published daily limits: 100 tool calls on Free, 500 on Starter, 2,000 on Business, 10,000 on Enterprise.
• In Claude's directory, so setup is a one-click pick.

Limitations:

• One team per authorisation; switching teams means reconnecting.
• Change history reading is not documented on the MCP pages we checked.
• Its documented examples lean toward code (visualising pull requests, explaining code on a board).

3. Linear

Verdict: the right connector for engineering issue tracking, with the cleanest read-only option.

Best for: software teams whose project board is an issue tracker.

Pricing: Free with 250 issues and 2 teams; Basic $10 and Business $16 per user a month billed yearly (Linear pricing).

Linear's MCP documentation describes tools for finding, creating and updating issues, projects and comments. It publishes a separate read-only address (https://mcp.linear.app/mcp/readonly), and you can also request only the read scope at sign-in. In Claude Code the command is claude mcp add --transport http linear-server https://mcp.linear.app/mcp. Enterprise teams can route sign-in through Okta.

Strengths:

• A dedicated read-only server.
• In Claude's directory.
• Fits the way engineering teams already work.

Limitations:

• Issues and projects, not a visual board: Claude cannot lay out a plan, a chart or a deck in Linear.
• Usage limits are not documented on the MCP page.

4. Notion

Verdict: good when your plan lives in pages and databases rather than on a canvas.

Best for: teams whose project board is a Notion database.

Pricing: Free plan; Plus $10 per member a month billed annually ($12 monthly) and Business $20 ($24 monthly); full Notion AI is on Business and Enterprise (Notion pricing).

Notion's MCP guide says a connected client can read and update content in the selected workspace, with access matching what you can access there. In Claude Code the command is claude mcp add --transport http notion https://mcp.notion.com/mcp. A file upload tool handles files up to 20 MiB. Sign-in must be interactive; automated setups cannot skip it.

Strengths:

• In Claude's directory.
• Strong for documents and databases.

Limitations:

• No documented read-only switch; Claude gets what you can access in the workspace.
• A database board is a list in columns, not a spatial plan with charts and decks.

5. Asana

Verdict: the connector for company-wide task assignment and portfolio status.

Best for: teams that already manage work in Asana and want Claude to create and assign tasks.

Pricing: Personal free for up to 2 users; Starter $10.99 and Advanced $24.99 per user a month billed annually (Asana pricing).

Asana's MCP documentation lists the V2 server at https://mcp.asana.com/v2/mcp and says the older beta address (https://mcp.asana.com/sse) was scheduled to shut down on May 11, 2026. Claude can search and read tasks and projects, create and assign tasks, and produce reports. In Claude it ships as the Asana app in Claude. With a team Claude account, Asana requires organisation-wide app approval, which needs App Management capabilities that Starter does not include (Asana help).

Strengths:

• Built for assigning work to people.
• Enterprise+ admins can allow or block individual MCP clients.

Limitations:

• Tasks and projects only; no visual board Claude can lay out.
• Team Claude accounts need Asana app approval that Starter lacks.

Not ranked: Milanote

Milanote is a popular visual board for creative work, but we could not find an MCP server or a Claude connector on its site, and its plans page lists no AI features. Its free tier holds 100 notes, images or links and 10 file uploads; paid is $9.99 per person a month billed annually. If you want Claude to build on a creative board today, Milanote is not an option until it ships a connector.

Setting Permissions Without Regret

Two systems decide what Claude can do on your board, and they stack. Storyflow's sign-in sets the outer limit (which projects, read or write, documents outside projects). Claude's tool approvals and per-chat toggles decide what happens inside that limit, call by call. Get the outer limit right and the inner one becomes a convenience rather than your only safeguard.

The last row comes from Claude's own guidance: its help center notes that Research can invoke connector tools automatically without approval and advises disabling write-capable tools before using it. With a read-only Storyflow connection, that warning stops mattering.

How to change permissions later

You cannot edit the choices in place. Open Storyflow, go to Settings, then Connected apps, and remove Claude. Access ends within a minute. Then reconnect from Claude and make new choices at sign-in. The same page is where you cut off a connection you no longer trust.

How long a connection lasts

Every Storyflow connection ends on its own after 30 days, and Claude asks you to sign in again. That is deliberate: a connection you forgot about does not stay open forever. Personal keys, for tools that cannot run a sign-in, also last 30 days. Claude on the web, Claude Desktop and Claude Code all run the normal sign-in, so you do not need a key for any of them.

Worked Example: A Six-Week Product Launch Board Built From Claude

Here is an illustrative launch, start to finish: the product, budget, people and timings are invented for the example, and the action counts follow how the tools are built. The product is a $49 online course. The launch runs six weeks, has a $4,000 budget and three people: the founder, a freelance designer and a part-time marketer. The brief is a 900-word Google Doc. The founder uses Claude Pro and Storyflow Plus.

Session 1: brief to board (about 15 minutes)

The founder pastes the brief into Claude with Storyflow switched on and writes: "Create a Storyflow project called Course Launch. Build a board with the six-week plan grouped by week, a task table with owner and due date columns, a budget chart, and a list of open questions. Then show me the board."

Claude's calls, counted one action each:

The founder then asked for a pitch for an affiliate partner: "Make a six-slide deck from this board for affiliates." That was create_deck plus add_deck_slides, two more actions. Session total: 12 actions.

Session 2: the week-two check-in (about 3 minutes)

"What changed on the Course Launch board in the last week, and who changed it?" Claude called get_board_changes and get_board_summary: 2 actions. The answer named the designer's four new thumbnail cards and the marketer's edited email dates, without the founder opening a single card.

Session 3: re-plan after a slip (about 8 minutes)

The designer's assets slipped five days. "Move every task that depends on the thumbnails back five days, and add a note in week four explaining the slip." Claude read the table (1), updated the dates (1 update call on the table) and added the note (1): 3 actions.

What it cost

Across three sessions the founder used 17 actions. On a paid Storyflow plan that count does not matter, because there is no MCP limit. If the marketer, on a free invited account, ran the same three sessions from their own Claude, 17 actions would fit inside the 25-action weekly allowance even if all three fell in the same week, leaving 8 actions, enough for two more check-ins. Your counts will differ by how much you ask Claude to build per message.

Prompts That Work on a Connected Board

These prompts are written to give Claude a clear target (which project, which board, what to build) so it does not guess. Paste them as they are, swapping in your names.

Why these prompts work

They name the project and the board, because Storyflow identifies a board by its project and board ids, and Claude finds those by listing projects and boards first. A prompt that says "my launch board" when you have three makes Claude ask or guess. They also say what to build (a table, a chart, a deck) rather than "organise this", which leaves Claude to decide the shape.

A prompt to avoid

"Clean up my workspace." It is vague about scope, so Claude reads widely, spends actions and makes changes you did not picture. Ask for one board and one kind of change at a time.

What It Costs to Connect Claude to a Project Board

Costs here are for one person who plans. Claude prices are from Claude's pricing page; board prices are from each vendor's pricing page linked in the comparison table.

Claude Code is included in Pro, so the Pro rows cover the terminal too.

How to try the Storyflow connection without your own plan

If someone on your team already pays for Storyflow, ask them to invite you to a board. You join free, and your own Claude can connect with the 25-action weekly allowance, which resets every Monday (UTC). When the week's actions are used up, Claude tells you, and nothing on the board changes.

Decision Rules: Which Board Should Claude Connect To

1. If Claude's output should be something you present (a plan, a chart, a deck), connect Storyflow.
2. If the work is engineering issues and Claude should only report, connect Linear's read-only address. If your team has outgrown Linear for non-engineering work, see the Linear alternative page.
3. If your company already assigns all work in Asana, connect Asana; do not move a whole company to get a better canvas. If only your creative team is leaving Asana, the Asana alternative page shows what changes.
4. If your team already lives in Miro and diagrams code, connect Miro and check its daily call limit for your plan. For planning rather than diagramming, compare it on the Miro alternative page.
5. If your plan is a Notion database, connect Notion, and accept that Claude will edit pages, not lay out a board. The Notion alternative page covers moving a plan from pages to a canvas.
6. If you are on Claude Free and need two custom connectors, you cannot; pick the one you will use daily, or move to Pro.
7. If you need $0 today on the board side, Storyflow is not it until its Free plan launches; use Miro Free or Linear Free.

Troubleshooting a Claude Board Connection

Claude says it cannot see a project

You did not pick that project when you signed in. Disconnect in Storyflow (Settings, then Connected apps), connect again from Claude and pick it.

Claude says it cannot change anything

You connected without changes allowed. Reconnect and allow changes for the projects you want, or check that the write tools are not switched off in Claude's Search and tools menu.

Claude keeps asking you to sign in

The connection reached its 30 days or was removed in Connected apps. Sign in again and choose your projects.

Claude Code shows storyflow as failed in /mcp

Run /mcp, select storyflow and complete the browser sign-in. If you added the server with the SSE transport by mistake, remove it with claude mcp remove storyflow and add it again with --transport http, because Storyflow does not serve SSE.

Claude Code warns that a tool's output is large

Claude Code warns when an MCP tool returns more than 10,000 tokens and caps output at 25,000 by default, per its documentation. A big board read can hit that. Ask for a board summary first, or raise the cap with the MAX_MCP_OUTPUT_TOKENS environment variable before starting Claude Code.

The photo you attached in Claude never appeared on the board

Pictures attached in a Claude chat do not reach Storyflow. Ask Claude to add the photo, and it calls request_photo_upload, which gives you an upload link for that board. Open it and add the image there.

Storyflow shows an "I trust this app" warning

Storyflow did not recognise the app asking to connect. If you started the connection from Claude yourself, tick the box and continue. If you did not start it, cancel.

Common Mistakes When Connecting Claude to a Board

• Allowing every project on the first try. Start with one test project. You learn how Claude places things without risking a client board.
• Clicking Allow always on write tools in week one. Approve writes one at a time until you trust the pattern; allow reads always.
• Using Research mode with a write-enabled connection. Claude's Research can call connector tools without approval. Keep that connection read-only.
• Vague prompts. "Organise my board" spends actions and produces a shape you did not picture. Name the board and the element.
• Expecting Claude to remember the board between chats. It reads the board fresh each conversation. That is a feature: the board, not the chat, is the record.
• Forgetting to disconnect after a project ends. Remove a client connection in Connected apps when the job ships; it would expire in 30 days anyway, but sooner is cleaner.
• Treating the connector as a scheduler. Storyflow does not publish or schedule social posts, send call sheets or send invoices. Claude can plan them on the board; another tool sends them.

When Storyflow Is Not the Right Choice

Storyflow is the board we recommend for visual, deadline-driven planning with Claude. It is the wrong choice in these cases, and we would rather you know now.

• You need $0 today. Storyflow is paid-only during early access. Its Free plan launches before the end of 2026. Miro Free (3 editable boards, 100 MCP calls a day) or Linear Free (250 issues) cost nothing now.
• Your board is an engineering issue tracker. Linear's connector is built for issues, cycles and projects; Storyflow is not a bug tracker.
• Your company assigns all work in Asana or a similar tool. Claude creating tasks where your team already works beats a better canvas nobody checks.
• You want a one-click directory install. Storyflow is added as a custom connector. On Claude Free that uses your only custom slot.
• You need a desktop or phone app, or offline work. Storyflow runs in the browser only.
• You need a calendar, publishing or approvals. Storyflow has no calendar tool, does not schedule posts, and has no formal versioned approval with an approve button.
• You want the connector to delete clutter for you. The connector has no tool to delete board elements outright; you remove those yourself in Storyflow.

A Template: Your First Thirty Minutes With Claude on a Board

Use this sequence the first time you connect. It moves from safe reads to small writes to a real job, and it shows you every permission in action.

The brief template that gets the best board

Claude builds a better board from a brief with these five lines. Copy them into the top of your brief:

• Goal: what done looks like, in one sentence, with a date.
• Deadline and milestones: the fixed dates.
• People: who owns what.
• Budget: the total and the main lines.
• Unknowns: the questions nobody has answered yet.

Each line maps to something Claude can build: the goal and milestones become the weekly plan, the people become the owner column, the budget becomes a chart, and the unknowns become the open-questions group.

The Bottom Line

Connecting Claude to a project board takes five minutes and one address. The choice that matters is which board you connect, because it decides what Claude can build. For visual, deadline-driven work (a launch, a campaign, a shoot) Storyflow lets Claude build the most: plan, tasks, budget chart, diagram and deck on one canvas, plus the ability to ask what changed and who changed it. For engineering issues connect Linear, for company task assignment connect Asana, for diagram-heavy team boards connect Miro. Start with one test project, approve writes by hand for a week, and widen access when the board shows you Claude places things where you would. The MCP page has the address and the steps for every assistant.