The 12 Best Claude Connectors in 2026 (Ranked by the Job You Give Claude)

Key Takeaways

• Storyflow is the best Claude connector for creative project planning: Claude reads your Storyflow boards and builds the plan, the tasks, the shot cards and the deck onto them, in the projects you allow.
• Claude has two ways to connect a tool: the Connectors Directory (listings reviewed by Anthropic) and custom connectors, where you paste a remote MCP server address yourself.
• Custom connectors work on every Claude plan, Free included, but Anthropic's help center limits Free users to one. Spend that slot on the tool where Claude's output should live.
• A connector is only as useful as the artifact it leaves behind. Connectors that only read (search the inbox, summarise a page) save minutes. Connectors that write a structured thing your team keeps save the afternoon.
• Storyflow and Miro are the two connectors on this list where Claude builds tables, documents and diagrams on a board from a chat (Figma's draws diagrams in FigJam). Miro's MCP is on every Miro plan with a daily cap of 100 calls on Free, according to Miro's pricing page.
• Zapier reaches 9,000 apps, but every tool call costs two tasks from your Zapier quota, and the Free plan has 100 tasks a month: about 50 calls.
• Claude's Research mode can call connector tools without asking for approval, so Anthropic recommends turning off write tools you do not want it to use. Check this before you connect anything that can send, share or delete.
• Storyflow is paid-only during early access (from $7.99 a month billed annually), runs in the browser only, and does not publish posts, schedule a calendar or send emails. Those jobs belong to other connectors on this list.

What a Claude Connector Actually Changes

You spend forty minutes with Claude turning a client brief into a production plan. The plan is good. Then you copy it into a doc, paste the task list into Asana, rebuild the moodboard section in another tool and email the client a PDF. The thinking took forty minutes. The copying took longer.

A connector closes that gap. It is a remote MCP (Model Context Protocol) server that Claude calls during a conversation, with your permission, to read from or write to another app. Anthropic's connectors directory article describes each listed connector as having a page that sets out its use cases, its read and write capabilities and its availability. Some connectors carry an "Interactive" badge, which means they can render a live interface inside the chat, such as a dashboard, a task board or a design tool.

Directory connectors versus custom connectors

There are two doors into Claude.

• The Connectors Directory. Open it from a chat with the plus button or by typing a slash, then Connectors, Manage connectors, and the plus next to Connectors. Every listing we opened on claude.com/connectors carried an "Anthropic verified" badge, the publisher's name and the server's address.
• Custom connectors. You add any remote MCP server by its address. Anthropic warns that custom connectors connect Claude to services it has not verified, so you only add servers from companies you trust.
• Desktop extensions. Local servers that run on your machine through Claude Desktop. Useful for developers, outside the scope of this list.

Storyflow is added as a custom connector with one address, which takes about a minute. The other eleven connectors below are all directory listings.

Read connectors and write connectors

The question to ask about any connector is not "what can Claude see?" It is "what does Claude leave behind?"

• Read connectors give Claude context: an inbox, a drive, a CRM record. The answer improves, then disappears into the chat history.
• Write connectors let Claude create the thing: a task, a page, a design, a board. The output survives the conversation and reaches people who never saw the chat.
• Structured write connectors create something with shape (a table with columns, a deck with slides, a board with sections), which is what a creative team works from.

It is not the number of tools a connector exposes that matters. It is whether the thing it writes is the thing your team opens on Monday.

How We Ranked the Best Claude Connectors

We ranked connectors for one job: a creative team, studio or solo creator using Claude to plan client and campaign work. That is a narrower job than "best connectors overall", and we say so because the ranking changes with the job. A developer would rank Linear and Atlassian far higher. A sales team would put HubSpot near the top.

Each connector was checked against its own listing on claude.com and its vendor's documentation on October 9, 2026. Tool counts below are the counts each listing shows.

How the scores add up

Every connector gets a 1 to 10 score on each criterion, and the rating is the weighted sum. Storyflow scores 10, 9, 10, 8, 7 and 8 for 8.95. Miro scores 8, 8, 7, 7, 9 and 7 for 7.60. Storyflow loses points on setup (it is a custom connector, and Storyflow itself is paid-only during early access) and on cost against tools with a free tier. It wins on what Claude leaves behind for a creative team.

What we did not weigh

We did not score connectors on how many tools they list. Asana's listing shows 15 tools, HubSpot's 36, Gamma's 3. Gamma's three tools produce a full presentation; some 30-tool connectors mostly read. We also did not score the underlying app as a product. A great app with a read-mostly connector ranks lower here than in a general software review.

Comparison Table: The 12 Best Claude Connectors Side by Side

Storyflow leads on building a plan your team keeps. Miro leads for teams whose boards already live in Miro. Canva leads on finished visuals. The best connector is the one that writes into the place your work already gets reviewed.

The 12 Best Claude Connectors in 2026, Reviewed

Each review follows the same shape: the verdict, who it is for, what Claude can do through it (from its claude.com listing), the cost to run it, and where it falls short.

1. Storyflow

Verdict: The best Claude connector for turning a brief or a long Claude conversation into a working project board.

Best for: Creative studios, agencies, producers, marketers and creators who plan client and campaign work and need the plan to outlive the chat.

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, launched in October 2026, lets Claude work on those boards directly. You add it once as a custom connector with the address https://mcp.storyflow.so/mcp, sign in to Storyflow, and choose which projects Claude may use.

What Claude can read. Boards, notes, documents and files in the projects you allow, plus what changed on a board and who changed it. That last part matters on Monday morning: "what changed on the launch board in the last week, and who changed it?" is one question, not a scroll through history.

What Claude can build. Notes, groups, tables, charts, diagrams, mind maps, documents, slide decks, shot cards, strip boards, colour palettes and carousel pages, and it can apply board templates. It places what it builds on the board where it belongs, and what it adds appears live on a board you have open. It can also edit and move elements, remove deck slides and clear table cells, so treat "allow changes" as a real permission.

Permissions. At sign-in you pick all projects or only some, whether Claude may make changes (without it, Claude can only read), and whether it may use documents outside projects. If Storyflow does not recognise the app connecting, it shows a warning and you tick "I trust this app". Disconnect in Settings, Connected apps, and access ends within a minute. Connections expire after 30 days and ask you to sign in again.

Photos. A picture you attach in the Claude chat does not reach Storyflow. Claude calls a tool that gives you an upload link for the board instead.

Cost to run it. Storyflow is paid-only during early access: Plus is $7.99 a month billed annually ($9.99 monthly), Pro $14 a month annually ($19 monthly) and adds AI image generation, Max $39 a month annually ($49 monthly) and adds a team workspace with roles and permissions. Plus, Pro and Max have no MCP limit. A free account (today, one invited by a paid member) gets 25 actions a week, where every read and change counts as one, reset each Monday UTC. The connector runs on Claude's model, so it does not spend Storyflow AI credits. See Storyflow pricing.

Strengths:

• Claude writes structured planning artifacts (tables, documents, shot cards, decks) rather than loose text
• Reads what changed and who changed it, so Claude starts from the board's current state
• Per-project scope, a read-only mode and a one-minute disconnect
• The same board opens in Storyflow's own AI agent, which reads the board plus up to 5 attached documents and 3 other boards

Limitations:

• Custom connector, so on Claude Free it uses your one custom connector slot
• Paid-only during early access; the Free plan launches before the end of 2026, and anyone a paid member invites to a board joins free now
• Browser only, no native mobile or desktop app, no offline mode
• Does not publish or schedule posts, send emails or run formal approvals

Try it: the Storyflow MCP page has the address and setup, and the help article walks through Claude step by step.

2. Miro

Verdict: The strongest directory connector for building on a whiteboard, and the right pick if your team's boards already live in Miro.

Best for: Product, UX and workshop teams with an existing Miro workspace.

The Miro listing shows 31 tools, including board_create, diagram_create, doc_create, table_create and table_sync_rows, plus tools to read, reply to and resolve comments. The listed jobs are summarising and searching boards, building new boards with frames, notes, tables and diagrams, and turning specs into diagrams. It was added to the directory in February 2026.

Cost to run it. Miro's pricing page lists Free at $0 with 3 editable boards, Starter at $8 per member a month and Business at $20 per member a month, both billed yearly. MCP is on every plan with daily call caps: 100 on Free, 500 on Starter and 2,000 on Business.

Strengths:

• Builds diagrams, docs and tables on a board from a prompt
• Comment tools let Claude work through review threads
• Usable on the Free plan

Limitations:

• Free keeps only 3 boards editable, which a single client project can fill
• Miro's workshop tooling fits product and UX teams better than shoot or campaign planning
• No shot cards, strip boards or decks built from the board

Trade-off: If your team is already on Miro, connect Miro. If you are choosing where a creative plan should live, read Miro alternatives for creative teams first.

3. Notion

Verdict: The best connector when the plan should end up as wiki pages and databases.

Best for: Teams who already run their operations, docs and content tracking in Notion.

The Notion listing points to Notion's hosted server at mcp.notion.com and shows tools to search, fetch, create pages, update pages, move and duplicate pages, create and update databases, and read and create comments. Notion's developer docs describe it as a hosted server that reads, creates and updates content you have access to, with workspace owners able to manage client access in Settings.

Cost to run it. Notion's pricing page lists a Free plan, Plus at $10 per member a month billed annually ($12 monthly) and Business at $20 per member a month billed annually ($24 monthly).

Strengths:

• Writes pages and databases your team already uses
• Strong for briefs, content trackers and documentation
• Workspace owners can manage and revoke connections

Limitations:

• A plan in Notion is a page and a database: references, frames and sequence sit in a list, not side by side
• No board layout for moodboards, storyboards or shot cards
• Large databases get slow for Claude to page through

Trade-off: Strong for text-shaped plans. For visual creative work, see Notion alternatives for creative teams.

4. Canva

Verdict: The best connector for getting from an approved idea to a finished, on-brand design.

Best for: Social and marketing teams producing posts, ads and one-pagers.

The Canva listing describes browsing, summarising, autofilling and generating Canva designs from Claude. It shows 17 tools, including search-designs, generate-design, export-design, import-design-from-url, create-folder and add-comment-thread-to-design. It sits in the Creative and Education categories.

Cost to run it. Canva's pricing page refused our fetch on October 9, 2026, so we leave its prices out. Check canva.com/pricing directly.

Strengths:

• Generates and exports real designs, not descriptions of designs
• Comment threads let Claude leave notes on a design
• Pairs well with a planning connector upstream

Limitations:

• It makes the asset, not the plan around it: no deliverables table, no shot list, no schedule
• Generated designs still need a human pass for brand fit

Trade-off: Use Canva to finish what Storyflow or Notion planned. Our Canva alternatives roundup covers when Canva is the wrong home for the plan itself.

5. Google Drive

Verdict: The connector that feeds every other one, because briefs, decks and transcripts arrive as Drive files.

Best for: Anyone whose clients send briefs as Google Docs, Slides or PDFs.

The Google Drive listing is made by Google, added in March 2026, and shows 11 tools: search_files, read_file_content, list_recent_files, get_file_metadata, create_file, update_file, copy_file, share_file, trash_file and two more. Anthropic's Google Workspace connectors article notes that Claude extracts text from Drive files and does not process images embedded in documents, and that on Team and Enterprise plans an Owner enables the connector before members authenticate.

Cost to run it. Uses your existing Google account.

Strengths:

• Claude reads the brief where it already lives
• Can create and update files
• Gmail and Google Calendar connectors sit alongside it

Limitations:

• Embedded images in documents are not processed, which matters for moodboard decks
• share_file and trash_file are powerful write tools: review them before you allow them
• Drive stores the plan; it does not structure it

6. Figma

Verdict: The best connector for pulling design context into Claude and drawing FigJam diagrams.

Best for: Designers and design-led teams handing work to developers.

The Figma listing describes pulling Figma context and generating code, with 9 tools including get_design_context, get_variable_defs, get_figjam and generate_diagram, which creates flow charts and other diagrams in FigJam. The listing notes that get_screenshot currently returns a description of the screenshot in Claude rather than the image. Figma's guide says the remote server is available on all seats and plans.

Strengths:

• Rich design context for design-to-code work
• FigJam diagrams from a prompt
• Remote server on every Figma plan

Limitations:

• Built for design and development handoff, not campaign or production planning
• Screenshots arrive as descriptions in Claude, not images

7. Asana

Verdict: The right connector once the plan is set and the job is assigning and tracking tasks.

Best for: Agencies and in-house teams whose delivery runs through Asana.

The Asana listing describes searching, creating, updating and tracking tasks, projects and goals. It shows 15 tools, including create_project_preview, create_task_preview, update_task, get_status_overview and portfolio tools.

Cost to run it. Asana's pricing page lists Personal free for 2 users, Starter at $10.99 per user a month annually ($13.49 monthly) and Advanced at $24.99 annually ($30.49 monthly).

Strengths:

• Tasks and status where your delivery team already looks
• Status overview tools answer "where are we?" well

Limitations:

• A task list, not the brief, the references or the deck behind it
• Personal free plan caps at 2 users

Trade-off: See Asana alternatives if your tasks need to sit next to the creative material.

8. Gamma

Verdict: The quickest way to turn a Claude outline into a presentable deck.

Best for: Founders and marketers who need a deck today and will polish it later.

The Gamma listing describes turning ideas into presentations, documents, social posts and websites from Claude, with three tools: generate, get_themes and get_folders. It was added in January 2026.

Cost to run it. Gamma's pricing page refused our fetch, so check gamma.app for current plans.

Strengths:

• One tool call can produce a whole deck
• Theme selection keeps output consistent

Limitations:

• Output is a presentation, not a working plan with tasks and references
• Little to read back: Claude cannot audit what changed in the deck

For a deeper comparison, read the best AI presentation tools.

9. Atlassian

Verdict: The safest connector for agencies whose delivery lives in Jira and Confluence.

Best for: Larger agencies and in-house teams with Atlassian admins.

The Atlassian listing covers Jira, Confluence, Bitbucket and Loom with your existing Atlassian permissions, showing 21 tools including createJiraIssue, transitionJiraIssue, createConfluenceContent and getLoomVideo. Read, write and delete operations are controlled by an admin setting, Jira delete and project-administration tools are off unless an admin enables them, and every tool call is recorded in the organisation's audit log.

Strengths:

• Best admin control on this list
• Respects existing Atlassian permissions

Limitations:

• Built for engineering-shaped work
• Needs an Atlassian setup most small studios do not have

10. Linear

Verdict: Excellent for product teams, a stretch for creative ones.

Best for: In-house teams building software alongside content.

The Linear listing shows 22 tools for issues, projects, cycles, comments and documents, including create_issue, update_issue and create_project.

Strengths:

• Fast, clean issue creation from a conversation
• Good project and cycle reads

Limitations:

• Issues are the wrong unit for a shoot, a campaign or a pitch
• No visual layer for references

11. Slack

Verdict: The last step of most workflows: tell the team what changed.

Best for: Any team that coordinates in Slack.

The Slack listing shows 11 tools, including slack_send_message, slack_read_channel, slack_read_thread, slack_create_canvas and slack_update_canvas.

Strengths:

• Claude can read a thread and summarise the decision
• Canvases hold a short brief or status

Limitations:

• Sending messages is a real action on your behalf: review before you allow it
• A canvas is not a plan your team will maintain

12. Zapier

Verdict: The fallback for apps with no connector of their own.

Best for: Operators connecting Claude to niche tools.

The Zapier listing describes connecting Claude to 9,000 apps. Zapier MCP is included in every Zapier plan, and each tool call uses two tasks from your quota. Zapier's pricing lists Free at 100 tasks a month and Pro at 750 tasks a month for $19.99 a month billed annually ($29.99 monthly).

Strengths:

• Reaches apps no one else connects to
• Saved workflows can become reusable Zaps

Limitations:

• Two tasks per call burns a Free quota in about 50 calls
• Generic actions, not structured planning output

Honourable Mentions and Tools Without a Claude Connector

These directory connectors are worth knowing, but sit outside the job this list ranks.

Milanote is the honest gap. It is a pleasant moodboard tool with a free tier of 100 notes, images or links and 10 file uploads, and $9.99 per person a month billed annually ($12.50 monthly). Without a connector, Claude cannot read or build on a Milanote board, so any plan Claude writes has to be pasted in by hand. Our Milanote alternatives roundup covers the trade-off.

A Worked Example: One Launch Campaign, Five Connectors, One Afternoon

This example is illustrative: the counts and times are our estimates, not measurements. A two-person studio gets a brief on a Tuesday: a skincare launch with one 60-second hero film, six 15-second cutdowns and twelve social stills, due in five weeks. The brief arrives as a 9-page Google Doc and a 14-slide reference deck in Drive. Here is the afternoon with connectors, in the order Claude uses them.

Step 1: Claude reads the brief from Drive (3 calls)

Prompt: "Find the Lumen launch brief and reference deck in my Drive, read both, and list the deliverables, the dates, the mandatory claims and anything the brief leaves open."

Claude runs search_files once and read_file_content twice. It returns 19 deliverables (1 hero, 6 cutdowns, 12 stills), 4 dates, 3 mandatory claims and 6 open questions. Because Drive does not process embedded images, the 14 reference images in the deck come back as slide text only. You note that and upload the key references to the board yourself.

Step 2: Claude builds the project board in Storyflow (about 12 actions)

Prompt: "In my Storyflow project Lumen Launch, build the campaign board: a brief summary document, a deliverables table with format, length, platform and due date, the open questions as notes, and a section for references. Show me the board first."

Claude calls list_projects and list_boards to find the project, show_board so you can watch, then build_section four times (brief, deliverables, open questions, references) and request_photo_upload for the references. Call it 12 actions on a free invited account's 25 a week; on Plus, Pro or Max there is no MCP limit.

Step 3: Shot cards and the client deck (about 4 actions)

After the client answers the open questions, you ask for 16 shot cards for the hero film from the approved references, then an 8-slide concept deck built from the board. Claude calls create_shot_cards once, create_deck once and add_deck_slides if the deck needs more. The client opens the board by a view-only link with no account, and signs in to comment.

Step 4: Tasks into Asana, a post in Slack (about 28 calls)

Claude creates 24 tasks in Asana from the deliverables table (one per deliverable, plus 5 production milestones) and posts a 6-line summary in the team channel with the board link.

What the afternoon cost

The by-hand column is our estimate of retyping the same output; your numbers will differ. The pattern does not: the time goes where the output is structured, and that is where a write connector pays back.

Prompts You Can Copy

These prompts assume the connector is added and enabled for the chat. Replace the project and file names with your own.

What It Costs to Run a Claude Connector Stack

Connectors are free inside Claude; the apps behind them are not. Prices below are from each vendor's pricing page on October 9, 2026.

Reading the table

A solo creator on Claude Pro, Storyflow Plus and Asana Personal pays about $24.99 a month billed annually. A studio of three on Claude Team, Storyflow Max and Asana Starter pays about $131.97 a month. Claude Max starts at $100 a month for heavier use. The cost that matters more is quota: Zapier's two tasks per call and Miro's daily MCP caps are the limits a busy week hits first.

Decision Rules: Which Claude Connector Should You Add First?

If Claude Free gives you one custom connector, or your team will only adopt one new habit, pick by where the output must live.

• The plan must be visual and shared with a client: Storyflow.
• Your team already works in Miro: Miro.
• The plan is a document or database your team maintains: Notion.
• The output is a finished design: Canva.
• You mostly need Claude to read what clients send: Google Drive (or Microsoft 365).
• The next step is assigning work: Asana, or Linear or Atlassian on technical teams.
• The app you need has no connector: Zapier.

Which connectors for which creative role

Common Mistakes With Claude Connectors

Connecting everything at once

Every enabled connector adds tools Claude may choose. Enable the two or three that a conversation needs from the plus menu, and leave the rest off. A focused tool list means fewer wrong calls.

Leaving write tools on during Research

Anthropic's help center warns that Research can invoke connector tools without approval and recommends disabling tools that write. Turn off send, share and delete tools before you start a Research run.

Spending Claude Free's one custom slot on a read-only tool

On Claude Free, custom connectors are limited to one. Directory connectors do not use that slot, so put your custom slot where Claude's output should be built.

Asking a read connector to plan

A Drive or Gmail connector makes Claude better informed, not better organised. If the output of the chat should be a plan, connect the tool that holds plans.

Forgetting that images do not travel

Drive does not process images embedded in documents, and a photo attached in the Claude chat does not reach Storyflow (Claude gives you an upload link instead). Plan for references to be uploaded where they are needed.

Granting all projects when one will do

Storyflow lets you pick projects at sign-in, and Atlassian respects existing permissions. Scope the connection to the client or campaign you are working on.

Sending without a preview

Ask Claude to show any message, email or post before it sends. Slack and Gmail connectors act on your behalf.

Treating a connection as permanent

Storyflow connections expire after 30 days, and any connector can lose access when a password or admin policy changes. When Claude says it cannot see a project, reconnect before you debug the prompt.

When Storyflow Is Not the Right Choice

Storyflow ranks first for one job. It is the wrong connector for several others.

You need a free tool today

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. If you cannot pay for anything today, Miro's Free plan with its MCP access or Notion's Free plan are the honest picks.

Your plan is a wiki or a database

If the output is a policy page, an onboarding doc or a content database with many properties, Notion's page and database tools fit better than a board.

You need posts published or scheduled

Storyflow does not publish or schedule social posts, does not have a calendar view and cannot sort a table by date. Use a scheduler for publishing, and keep rows in date order on the board if you plan there.

You need formal approvals, invoices or contracts

There is no approve button or versioned proofing in Storyflow, and no invoicing or contracts. Clients view by link with no account and sign in to comment.

You work offline or on a phone app

Storyflow runs in the browser only, with no native mobile or desktop app and no offline mode.

Your team is engineering-led

If the work is software, Linear or Atlassian connectors map to how your team already tracks it.

Template: A Claude Connector Setup for a Creative Studio

Copy this setup for a studio of one to five people. It takes about 20 minutes.

The connectors

1. Google Drive from the directory, read tools on, share and trash off.
2. Storyflow as a custom connector: Customize, Connectors, Add, Add custom connector, name it Storyflow, paste https://mcp.storyflow.so/mcp, Continue, Sign in now, Add, then sign in to Storyflow and pick the client projects.
3. Canva from the directory for finished assets.
4. Slack from the directory, with "show me before sending" in every prompt.
5. On Team or Enterprise, an Owner adds each connector in Organization settings, Connectors first, then each member clicks Connect.

The board layout Claude builds into

The weekly check-in prompt

"Read the [client] board. What changed in the last week and who changed it? List deliverables due in the next 7 days, open questions still unanswered, and anything on the board that contradicts the brief."

Setting Up Claude Connectors, Plan by Plan

Claude Free

Directory connectors and one custom connector. Claude's pricing page lists connectors on Free. Pick your custom connector carefully.

Claude Pro and Max

Add custom connectors yourself under Customize, Connectors. Pro is $20 a month or $17 a month billed annually; Max starts at $100 a month.

Claude Team and Enterprise

An Owner or Primary Owner adds connectors at the organisation level, then each member authenticates individually so Claude only sees what that person can see. Anthropic's directory article adds that on Team and Enterprise, connectors are only available in private projects, and Owners can set actions to always allow, need approval or block.

Claude Code

For Storyflow, run claude mcp add --transport http storyflow https://mcp.storyflow.so/mcp in your terminal, then /mcp inside Claude Code to sign in.

The Bottom Line

The best Claude connector is the one that writes into the place your work gets reviewed. For creative teams that place is a project board, which is why Storyflow ranks first: Claude reads the board, builds the plan, the shot cards and the deck onto it, and the client opens the result by link. Add Google Drive so Claude reads what clients send, Canva for finished assets and Slack for the update. If your team already lives in Miro or Notion, connect those instead.

Start with one brief. Add Storyflow from the Storyflow MCP page, ask Claude to build the board from it, and judge the connector by what is still useful on Monday.