The 12 Best MCP Servers for Claude in 2026 (Remote and Local, for Claude.ai, Desktop and Code)

Key Takeaways

• Storyflow ranks first for makers who plan visual work in Claude: it is a remote server, so it works in Claude.ai, Claude Desktop and Claude Code from one address, and it builds boards, decks, shot cards and mind maps instead of returning text.
• Remote MCP servers live on the vendor's servers and you add them by URL. Local servers run as a program on your computer and only work in Claude Desktop and Claude Code, never in Claude.ai in the browser.
• Claude's Free plan allows one custom connector, according to Anthropic's custom connector guide. Pick that one slot carefully.
• Permissions matter more than tool count. Storyflow lets you pick projects and choose read-only at sign-in, and Linear publishes a separate read-only endpoint.
• Cost is counted in actions, not seats. Zapier's pricing page gives 2 tasks per tool call as its example rate, Miro's Free plan allows 100 MCP calls a day, and a free Storyflow account gets 25 actions a week.
• Claude Code warns when one MCP tool result passes 10,000 tokens and caps it at 25,000 by default, per the Claude Code MCP docs.
• The open-source reference servers (Filesystem, Fetch, Git, Memory) are teaching code, and their own repository says so. Use them, but do not treat them as hardened products.
• Three connected servers that each own one job beat ten that overlap. A good starter stack for a founder is Storyflow, Notion and Zapier.

Why "Best MCP Server" Means Something Different in Each Claude App

You open Claude, ask it to turn last week's call notes into a launch plan, and it writes you 1,400 words. Good words. Then you copy them into Notion, rebuild the tasks in Asana, sketch the timeline on a whiteboard and paste the deck outline into Canva. Claude did the thinking. You did four hours of moving it.

That copy-paste tax is what the Model Context Protocol removes. Anthropic announced and open-sourced MCP on 25 November 2024 as one standard way for assistants to reach the tools where your work lives. An MCP server is the app's side of that connection: it tells Claude which actions exist ("create a page", "read a board", "export a design") and runs them when Claude asks.

The catch is that "add an MCP server to Claude" means three different things depending on where you use Claude.

Claude.ai in the browser only takes remote servers

In Claude.ai you add a remote server as a connector, either from the directory or as a custom connector with a URL. Anthropic's guide is explicit that the connection comes from Anthropic's cloud, not from your device, so the server has to be reachable on the public internet. A program running on your laptop cannot be a Claude.ai connector. If a server only runs locally, half of the Claude surfaces you use cannot see it.

Claude Desktop takes both, through two doors

Claude Desktop shows every remote connector you added on the web. It also runs local servers, packaged as desktop extensions (.mcpb files) you install from Settings, then Extensions. Anthropic's local server guide notes that Desktop ships its own Node.js runtime and supports Node.js, Python and binary servers, and that secrets marked sensitive are stored in your operating system's keychain.

Claude Code takes all three transports

Claude Code adds servers from the terminal with claude mcp add. Remote servers use --transport http, local ones use stdio, and the docs mark SSE as deprecated. You also pick a scope: local (this project, just you), project (shared through a .mcp.json file in the repository) or user (all your projects). That scope choice is the most underrated decision in the whole setup, and we come back to it in the safety section.

How We Evaluated These MCP Servers

We read each vendor's own MCP documentation and pricing page on 9 October 2026, and every price and limit below links to that page. Anything we could not confirm on a vendor page is left out, and the list of what we dropped is at the end of the methodology.

The reader we wrote for is not a backend engineer. It is a founder, producer, marketer or creative lead who uses Claude every day and wants it to finish the job in the tool where the work lives. So the criteria reward finished output and safe defaults over raw API coverage.

The six criteria and their weights

• Output a maker can use (25%). When Claude finishes, is there a board, page, design or task list you would show a client, or just a block of text?
• Works on all three Claude surfaces without installing anything (20%). Remote servers that work in Claude.ai, Desktop and Code score highest. Local-only servers score lowest, because Claude.ai cannot reach them.
• Permission control and safety (20%). Can you limit what Claude sees, keep it read-only, and revoke access fast?
• Read and write depth (15%). Can Claude both read what is there and build or change things?
• Cost to run (10%). What do the vendor's plan and the per-call metering cost a solo user?
• Maturity of the vendor's documentation (10%). Is there an official, current setup page with an address, auth method and limits? Older products score higher here, and Storyflow, launched in October 2026, scores lower.

What we deliberately did not reward

Tool count. A server with 40 tools is not better than one with 17 if the extra tools make Claude pick the wrong one more often. We also did not reward "free" on its own, because a free server that needs Node.js, a terminal and an API key is not free for someone who has never opened a terminal.

The Weighted Scores

The scores below are our editorial judgement against the six criteria. The weighting is published so you can re-weight it: if you live in Claude Code all day, double the read and write column and halve the surfaces one, and GitHub climbs ten places.

Best MCP Servers for Claude Compared

Remote vs Local MCP Servers: The Decision That Decides Everything Else

Most "best MCP server" lists mix remote and local servers in one ranking without saying so. That is how people end up following a guide, editing a JSON file for an hour, and then discovering the server never appears in Claude.ai on their phone.

Remote is the right default for non-developers

A remote server is a web address. You paste it, sign in with the account you already have, approve what it may do, and it works everywhere Claude does. Anthropic's guide confirms that remote connectors work in Claude.ai, Claude Desktop, Cowork and the mobile apps. For a founder or creative lead, a remote server is the only kind that keeps working when you switch from laptop to phone.

Local earns its place when the data is on your machine

A local server is the right tool when the thing Claude needs is on your computer: a folder of transcripts, a browser you want it to drive, a git repository you have not pushed. Local servers also avoid sending that data through a vendor's cloud. The price is setup and responsibility. A local server runs with your user permissions, so a careless one can read anything you can read.

Transport names, translated

You will see three words in setup guides. Streamable HTTP (usually written as just "HTTP") is the current remote standard. SSE is the older remote transport, and Claude Code's docs call it deprecated. Stdio means "run this program locally and talk to it through its input and output". If a vendor offers HTTP, pick it. Storyflow, Linear, Asana and Notion all do.

The 12 Best MCP Servers for Claude, Ranked

Each review follows the same shape: the verdict, who it is for, the price, the address, why it ranks where it does, then strengths and limits.

1. Storyflow

Verdict: the MCP server that turns a Claude conversation into a finished visual project: a board with the plan, tasks, references, deck and shot list on one canvas.

Best for: founders, producers, agencies, marketers and creators who plan launches, shoots, campaigns and content in Claude.

Price: 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. Plus is $7.99/mo billed annually ($9.99 monthly), Pro $14/mo annual, Max $39/mo annual. See pricing. A free account (today, an invited one) gets 25 MCP actions a week, reset Monday UTC; Plus, Pro and Max have no MCP limit.

Address: https://mcp.storyflow.so/mcp (Streamable HTTP; it does not serve SSE).

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. Its MCP server lets Claude work on those boards. Claude can list your projects and boards, read the notes, documents and files on a board, see what changed on a board and who changed it, and search. It can also build: create a project, build a whole section, add tables, charts, diagrams, mind maps, documents, slide decks, shot cards, strip boards, colour palettes and carousel pages, apply a board template, and group or move elements. What Claude adds is placed on the board where it belongs, and it appears live if you have the board open.

Why first? Because it is the server on this list built most squarely around turning a planning conversation into a project artefact you can hand to a client or a team. Notion gives you a page. Asana gives you tasks. Storyflow gives you the board that holds the page, the tasks, the references and the deck at once. In clients that support MCP apps, the show_board tool puts the live board inside the chat, so you watch Claude build it.

The permission model is the second reason. At sign-in Storyflow asks which projects Claude may use (all or the ones you pick), whether it may make changes (otherwise it is read-only), and whether it may use your documents outside projects. Apps Storyflow does not recognise get an "I trust this app" warning. Connections expire after 30 days, and removing one in Settings, then Connected apps, ends access within a minute. Among the other servers here, Linear's separate read-only address and GitHub's --read-only flag are the closest ways to limit Claude before it connects.

How to add it in 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. In Claude Code: claude mcp add --transport http storyflow https://mcp.storyflow.so/mcp, then run /mcp to sign in. Full steps for every client are in the connection guide, and the MCP page shows the jobs people hand to it.

Strengths:

• Builds finished artefacts (decks, shot cards, strip boards, mind maps, charts) rather than text.
• Per-project scope and a read-only option chosen at sign-in.
• Runs on your Claude model, so it spends no Storyflow AI credits.
• One address works in Claude.ai, Claude Desktop, Claude Code and other MCP clients such as ChatGPT, Gemini, Grok and Cursor.

Limitations:

• New: launched October 2026, so far less community knowledge than Notion or GitHub.
• No free plan yet; a free invited account is capped at 25 actions a week.
• Browser-based product with no offline mode, so it is not the place for data that must stay on your machine.
• A photo you attach in the Claude chat does not reach Storyflow; Claude gives you an upload link instead.

2. Notion

Verdict: the best server when the deliverable is a document, wiki page or database.

Best for: teams whose source of truth is already Notion.

Price: Notion has a Free plan; Plus is $10 per member a month billed annually ($12 monthly) and Business $20 ($24 monthly), per Notion's pricing page.

Address: https://mcp.notion.com/mcp (the example Claude Code's own docs use).

Notion's hosted server lets Claude search your workspace, read pages, and create and update pages and databases, according to Notion's MCP documentation. You sign in with OAuth and Claude sees what your account can see. Notion's help centre adds that MCP tools "act with your full Notion permissions", which is the honest warning: there is no per-page scoping at sign-in like Storyflow's project picker.

It ranks second because for written work it is the most complete server we checked, with mature docs and admin controls (workspace owners manage connections in Settings, then Connections). It is not first because a Notion page is linear. Ask Claude to plan a launch and you get a well-structured document, which is right for a spec and wrong for a plan your team needs to rearrange.

Strengths:

• Mature first-party server with OAuth and admin controls.
• Read and write across pages and databases.
• Listed among the top connectors in Claude's directory.

Limitations:

• Acts with your full workspace permissions.
• Output is pages and databases, not a visual canvas.

3. Canva

Verdict: the best server for getting a finished social graphic, poster or presentation out of a Claude conversation.

Best for: marketers and creators who already design in Canva.

Price: depends on your Canva plan. We could not load Canva's pricing page to confirm which MCP features need a paid plan, so check before you rely on one.

Address: add Canva from Claude's connector directory.

Claude's Canva connector listing describes it as search, create, autofill and export Canva designs, and lists 17 tools, among them search-designs, generate-design, export-design, import-design-from-url, create-folder and add-comment-thread-to-design. Canva's developer docs add export to PDF, PNG, JPG, PPTX and MP4.

It ranks third because the output is shippable: a design you can post. It is behind Notion because its reading side is mostly about finding designs, not understanding a project, so Claude cannot use Canva to hold the plan the design belongs to.

Strengths:

• Generates and exports real designs in common formats.
• Can comment on designs and organise folders.

Limitations:

• Feature access depends on your Canva plan, which we could not verify.
• Holds designs, not the project around them.

4. Miro

Verdict: the closest whiteboard alternative to Storyflow, strongest for teams already running workshops in Miro.

Best for: product and design teams with existing Miro boards.

Price: Free with 3 editable boards and 100 MCP calls a day; Starter $8 per member a month and Business $20, both billed yearly, per Miro's pricing.

Address: https://mcp.miro.com/

Miro's MCP documentation lists summarising and searching boards, reading items and comments, replying to and resolving comments, and creating boards, widgets, diagrams, documents, tables, code widgets and images. It supports Claude on web and desktop and Claude Code. On Enterprise plans the server is off until an admin enables it.

Miro and Storyflow overlap more than any other pair here. The difference is what Claude builds. Miro's server creates diagrams, documents and tables on a collaborative whiteboard. Storyflow's builds production artefacts for creative work (slide decks, shot cards, strip boards, colour palettes, carousel pages) and applies whole board templates. For a workshop, Miro. For a shoot, a launch or a content plan, Storyflow.

Strengths:

• Clear MCP limit on the Free plan.
• Comment handling, useful for async review.

Limitations:

• Free plan keeps only the three most recent boards editable.
• No deck, shot list or strip board output.

5. Figma

Verdict: essential if you design in Figma and hand off to code; narrower for everyone else.

Best for: product designers and design engineers.

Price: the remote server is available on all seats and plans; the desktop server needs a Dev or Full seat on a paid plan. Professional Full seats are $16 a month per Figma's pricing.

Address: https://mcp.figma.com/mcp (remote, preferred) or the local desktop server.

Figma's guide lists extracting design context (variables, components, layout), generating code from selected frames, and, on the remote server only, writing native content to Figma Design and FigJam canvases, which Figma describes as free during beta and paid by usage later. Claude Code is listed as supporting desktop, remote and write-to-canvas.

It ranks fifth because its strongest jobs are design-to-code, which matter to a smaller slice of Claude users. For a designer it may be the first server you add.

Strengths:

• Both remote and local options, documented in one place.
• Writes to the canvas from Claude.

Limitations:

• Canvas writing is in beta and will become usage-based.
• Local desktop server needs a paid seat.

6. Zapier

Verdict: the widest reach on this list: one connection gives Claude actions in the apps you have connected to Zapier.

Best for: operators who need Claude to touch email, calendars, CRMs and spreadsheets that have no MCP server of their own.

Price: Free with 100 tasks a month; Professional from $19.99/mo billed annually, per Zapier's pricing. Zapier's MCP calls draw from the same task pool as your Zaps; the pricing page's example rate is 2 tasks per tool call, and failed actions do not count.

Address: add Zapier as a connector in Claude and sign in. Zapier's setup guide says the server is created for you at sign-in, with actions enabled for apps already connected to your Zapier account.

Zapier ranks sixth because breadth is its whole value and its weakness. On the Free plan, 100 tasks is about 50 tool calls a month. And because one server exposes actions across many apps, its permission model is only as narrow as the actions you enable.

Strengths:

• Reaches apps that will never ship their own MCP server.
• Published metering, with 2 tasks per tool call as the example rate.

Limitations:

• Tasks are shared with your Zaps, so heavy Claude use eats automation budget.
• Broad by design, so review which actions are on.

7. Asana

Verdict: the right server when tasks already live in Asana and Claude should create and update them.

Best for: marketing and operations teams on Asana.

Price: Personal is free for up to 2 users; Starter $10.99 per user a month annual, Advanced $24.99, per Asana's pricing.

Address: https://mcp.asana.com/v2/mcp

Asana's MCP page lists Streamable HTTP with OAuth, and names the Asana app in Claude and Claude Code among supported clients. The beta server at https://mcp.asana.com/sse is deprecated and Asana's page gives its shutdown date as 11 May 2026, so any old setup guide pointing at it is out of date.

Strengths:

• First-party, OAuth, Streamable HTTP.
• Enterprise admins can allow or block MCP clients.

Limitations:

• Tasks and projects only; no visual board or deck output.
• Old SSE guides on the web point at a retired address.

8. Linear

Verdict: the best-designed permissions of any server here, for a job most makers do not have.

Best for: product and engineering teams.

Price: Free (250 issues, 2 teams); Basic $10 per user a month annual, Business $16, per Linear's pricing.

Address: https://mcp.linear.app/mcp, or https://mcp.linear.app/mcp/readonly for read tools only.

Linear's MCP docs describe OAuth 2.1 with dynamic client registration, a bearer-token option, and a separate read-only endpoint. That read-only URL is the pattern every vendor should copy: you decide Claude cannot write before it ever connects.

Strengths:

• Separate read-only endpoint.
• Streamable HTTP, with SSE as a documented fallback.

Limitations:

• Issues and projects for software teams; little use for a shoot or a campaign.

9. Atlassian Rovo

Verdict: the one server to add if your company runs on Jira and Confluence.

Best for: teams inside the Atlassian suite.

Price: usage is billed in Rovo credits per call, which scale with data volume and reasoning depth.

Address: https://mcp.atlassian.com/v2/mcp

Atlassian's guide names Jira, Jira Service Management, Confluence, Bitbucket, Projects, Goals and Loom, with OAuth 2.1 that respects users' existing access. In Claude Code the command is claude mcp add --transport http atlassian https://mcp.atlassian.com/v2/mcp.

Strengths:

• Covers several Atlassian products through one server.
• Respects existing Atlassian permissions.

Limitations:

• Credit-based billing is harder to predict than a flat call count.

10. GitHub

Verdict: the first server any developer adds; a read-only flag makes it safe to start with.

Best for: anyone whose work lives in repositories, issues and pull requests.

Price: the server is open source.

Address: https://api.githubcopilot.com/mcp/ remotely, or the Docker image ghcr.io/github/github-mcp-server locally.

GitHub's repository documents OAuth or a personal access token, toolsets you can switch on and off (the default set is context, repos, issues, pull requests and users), and a --read-only flag that skips every write tool. It ranks tenth on this list only because our reader is not mainly a developer.

Strengths:

• Both remote and local, with fine-grained toolsets.
• Read-only mode overrides any tool you request.

Limitations:

• Token setup is unfamiliar for non-developers.

11. Filesystem (reference server)

Verdict: the simplest way to let Claude Desktop or Claude Code read and write one folder on your computer.

Best for: writers, researchers and editors with a folder of drafts, transcripts or notes.

Price: open source.

Install: a local server; add it to Claude Desktop or Claude Code with the folder path you allow.

Filesystem is one of seven reference servers maintained by the MCP steering group in the modelcontextprotocol/servers repository, alongside Everything, Fetch, Git, Memory, Sequential Thinking and Time. The repository describes them as reference implementations, not production-ready solutions, and tells you to assess your own security needs. Give it one folder, never your home directory.

Strengths:

• Data stays on your machine.
• No account or vendor in the loop.

Limitations:

• Invisible to Claude.ai and the mobile apps.
• Reference code, not a hardened product.

12. Playwright

Verdict: gives Claude a real browser to click, fill and read, without a vision model.

Best for: checking a live page, testing a form, or collecting details from a site.

Price: open source.

Install: in Claude Code, claude mcp add playwright npx @playwright/mcp@latest; needs Node.js 18 or newer.

Microsoft's Playwright MCP works from the page's accessibility tree rather than screenshots. It is listed among the top plugins in Claude's directory. It sits last because it is a local developer tool, but it is the most useful local server for a non-developer once someone sets it up.

Strengths:

• Structured page snapshots, so it is fast and cheap on tokens.
• Works with any site you can open.

Limitations:

• Local only.
• A browser that reads web pages is the most exposed path for prompt injection.

Other Servers We Considered

Milanote is the board tool most often compared with Storyflow, and we checked for an MCP server. Its homepage and plans page mention no AI features, API or MCP. Its Free plan holds 100 items and 10 uploads, and paid is $9.99 per person a month billed annually. If you want Claude to build on a moodboard, Milanote cannot take that job today.

Google Drive, Gmail, Slack, HubSpot, monday.com and Microsoft 365 all appear among the top connectors in Claude's connector directory. We left them out because we did not verify their MCP details on the vendor's own pages in this session, and a list built on unverified setup steps is worse than a shorter one.

The archived reference servers (the old GitHub, Google Drive, Slack, PostgreSQL, Puppeteer and others) moved to an archive repository. Several were replaced by official vendor servers. If a tutorial tells you to install the old Google Drive or GitHub reference server, it is out of date.

Worked Example: A Product Launch Board From One Claude Conversation

Numbers make this concrete. Here is a founder planning a product launch, with Storyflow, Notion and Zapier connected to Claude Pro ($17 a month billed annually or $20 monthly, per Claude's pricing).

The input

A 1,200-word launch brief pasted into Claude, plus a request: "Build a Storyflow board for this launch with the plan, the tasks, the open questions and a ten-slide pitch deck. Then write the press page in Notion."

The calls Claude makes

Every read and every change is one Storyflow action. The table below is an illustrative run, not a measurement; the exact count depends on how Claude splits the work.

What it costs

• Storyflow: 8 actions. On Plus or above there is no MCP limit. On a free invited account, 8 of the 25 weekly actions, so about three runs like this a week.
• Zapier: at the example rate, 1 call is 2 tasks. On Zapier Free (100 tasks a month), that is 2% of the month.
• Notion: no per-call metering is published on Notion's pages we checked.
• Storyflow AI credits: zero, because the MCP runs on Claude's model.

What you have at the end

A board with three groups (plan, tasks, open questions), a timeline table, and a ten-slide deck on the same canvas, plus a Notion press page. It is not that Claude wrote more. It is that nothing it wrote needs to be moved. The founder's next step is to drag two tasks into a different week, which is one drag on a canvas and a cut-and-paste job in a document.

Prompts You Can Copy

These are written to make Claude pick the right server and the right tool. Paste them as they are, then edit the nouns.

Three prompt habits that save actions

• Name the server. "In Storyflow" or "in Notion" stops Claude from asking or guessing.
• Name the project. It saves a list_projects call and stops Claude from building in the wrong place.
• Say "without changing anything" for reviews, even on a read-only connection. It also keeps Claude from proposing writes you then have to decline.

How to Add an MCP Server in Each Claude App

The steps differ by surface. These are the current ones from Anthropic's pages.

Claude.ai and Claude Desktop (remote)

1. Open Customize, then Connectors.
2. Click Add, then Add custom connector (or pick the server from the directory).
3. Enter a name and the server URL, review the authentication, and click Add.
4. Sign in to the service and approve what Claude may do.

On Claude's Team and Enterprise plans, an Owner or Primary Owner adds the connector under Organization settings, then Connectors, and members then connect individually.

Claude Desktop (local)

1. Open Settings, then Extensions.
2. Click Browse extensions for Anthropic-reviewed tools, or Advanced settings, then Install Extension for a .mcpb file.
3. Fill in any keys the extension asks for. Fields marked sensitive go to your OS keychain.

Claude Code

1. Remote: claude mcp add --transport http name URL, then /mcp in a session to sign in.
2. Local: claude mcp add name -- command arguments (the double hyphen separates Claude's options from the server's command).
3. Choose a scope with --scope local, project or user.
4. Check with claude mcp list, and remove with claude mcp remove name.

Safety: What Can Go Wrong and the Settings That Prevent It

An MCP server is a set of hands you give Claude. Anthropic's own guide lists the risks plainly: servers not verified by Anthropic, hidden instructions in a malicious server (prompt injection), and developers changing tool behaviour after you connect.

The three risks that actually happen

• Prompt injection through content. A server that fetches web pages, emails or shared documents can feed Claude text written by someone else, and that text can carry instructions. The Claude Code docs warn about exactly this.
• Over-broad permission. A connector with write access to every project gives a confused instruction a large blast radius.
• Stale or unofficial servers. A community wrapper around a vendor's API, or an old reference server, may be unmaintained.

The settings that prevent them

• Choose read-only first. Storyflow asks at sign-in; Linear has a read-only URL; GitHub has --read-only. Turn writes on when you need them.
• Scope to projects. Pick the projects Claude may use instead of all of them.
• Do not click "Allow always" on write tools from servers you do not control. Anthropic recommends it only for trusted tools, and notes that in Research mode Claude can call connector tools without asking, so disable write tools there.
• Review project-scoped servers. In Claude Code, a .mcp.json in a repository you cloned asks for approval before it loads. Read it before you approve.
• Revoke on a schedule. Storyflow connections expire after 30 days by design. For other servers, put a monthly reminder in your calendar to review Connected apps.

Cost Table: What a Month of Claude Plus MCP Servers Costs

Prices are as of 9 October 2026 from each vendor's page, for one person, billed annually where the vendor offers it.

There is no free Storyflow row because Storyflow is paid-only during early access; its Free plan launches before the end of 2026. The one way to try the connection without paying today is to be invited to a board by a paid member: the invited account joins free and gets 25 MCP actions a week, which you can connect to Claude Free as its single custom connector.

Decision Rules: Which MCP Server Should You Add First?

Use the first rule that matches you.

Personas and top picks

• Founder running the business: Storyflow and Notion. Storyflow holds the launch and fundraising boards Claude builds; Notion holds the written policies.
• Agency or studio lead: Storyflow and Asana. Client plans and decks on boards, team tasks in Asana.
• Producer or filmmaker: Storyflow and Filesystem. Shot cards and strip boards on the board, transcripts in a local folder.
• Marketing or brand lead: Storyflow and Canva. The campaign board and the finished assets; see the best AI tools for marketers for the rest of the stack.
• Creator on YouTube or social: Storyflow and Zapier. The content pipeline on a board, and the glue to whatever else you use.
• Product designer: Figma and Storyflow. Design context for code, and the research board around it.

Common Mistakes When Adding MCP Servers to Claude

Following a local-server guide for Claude.ai

If the guide says "edit claude_desktop_config.json" or "run npx", it is a local server and Claude.ai cannot use it. Look for a remote URL first.

Spending Claude Free's one connector on something you rarely use

Claude Free allows one custom connector. Spend it on the tool where your work lives every day.

Connecting everything with write access on day one

Read-only first, then widen. Most of the value in week one is Claude reading and summarising what is already there.

Installing an archived reference server

The old Google Drive, GitHub and Slack reference servers are archived. Use the vendor's official server.

Using SSE because an old guide said so

Asana's beta SSE address is deprecated and Claude Code calls SSE deprecated. Use the HTTP address.

Letting tool results blow the context

Claude Code warns at 10,000 tokens per tool result and caps at 25,000 by default (raise it with MAX_MCP_OUTPUT_TOKENS). Ask for summaries and filtered lists, not "everything on the board".

Expecting the server to see what you attached in chat

A photo you drop into Claude stays in Claude. Storyflow's server answers with an upload link through request_photo_upload; other servers may simply not see it.

When Storyflow Is Not the Right Choice

Storyflow ranks first on this list because the criteria reward finished visual output for makers. Change the job and the answer changes.

Your work is code

Use GitHub, Linear and Playwright. Storyflow does not hold repositories or issues.

Your deliverable is a long written document

Notion or Google Docs is the better home for a 20-page spec. Storyflow holds documents on a board, but a wiki is Notion's job.

Your data cannot leave your machine

Storyflow is a browser product with no offline mode and no local server. Use the Filesystem reference server with a local folder.

You need to publish, schedule or approve

Storyflow does not publish or schedule social posts, has no calendar tool, and has no formal approval button. Use your scheduling tool or a proofing tool, and keep the plan on the board.

You want a free tool today

Storyflow is paid-only during early access, and its Free plan launches before the end of 2026. Miro Free (100 MCP calls a day) or Notion Free are free today.

You care most about years of track record

Storyflow's MCP server launched in October 2026. Notion, GitHub and Atlassian have been documenting theirs for longer.

Template: Your MCP Setup Checklist

Copy this list into a note and work down it, one server at a time.

1. Write down the one output you most want from Claude this month (a board, a page, a design, a task list).
2. Pick the server that produces that output from the decision table above.
3. Check whether it is remote. If not, confirm you use Claude Desktop or Claude Code.
4. Check your Claude plan. On Free, this is your one custom connector.
5. Add it with the server's own address from this article or the vendor's page.
6. At sign-in, choose read-only and the narrowest project scope.
7. Run one read prompt ("summarise what is on X") and check the answer against the real thing.
8. Turn on write access for one project and run one build prompt.
9. Add a second server only when the first one is used daily.
10. Set a monthly reminder to review connected apps and remove what you no longer use.

Starter template for a creative project board

If you start with Storyflow, ask Claude to build this structure on a new board in one go: a Brief group (the brief and goals), a Plan group (milestones as a table with rows kept in date order), an Open Questions group, a References group, and a Deliverables group with a slide deck. Then use the board for a week before adding anything else. Storyflow's AI creative brief generator, AI shot list generator and AI storyboard generator pages show the same jobs done with the in-app AI instead of Claude, and the AI moodboard generators roundup covers the reference side. If you are new to planning on a canvas, start with visual project planning.

The Bottom Line

Pick MCP servers by the output you want, not by how many tools they expose. For anyone planning launches, shoots, campaigns or content in Claude, Storyflow is the first server to add: one remote address, every Claude surface, scoped to the projects you choose, and the result is a board with the plan, the tasks and the deck instead of text you have to move. Add Notion for documents, Canva or Figma for design, and Zapier for the long tail. Keep local servers for data that must stay on your machine.

Take your next brief, connect Storyflow at storyflow.so/mcp, and ask Claude to build the board. You will know within one conversation whether the copy-paste tax is gone.