Chrome
Web
iOS
Android
Best Claude MCP Servers for Business in 2026: 12 Connectors That Do Real Work
The best Claude MCP servers and connectors for business teams in 2026: shared inboxes, project management, CRM, support, payments, and automation. Written by the team that runs its own MCP server, with what each connector actually lets Claude do.
- Claude's connector directory now holds well over a thousand integrations, but most ranked lists cover developer tools. This list covers the twelve that do real business work: email, projects, CRM, support, payments, data, and automation.
- Every connector here is free to use with the account you already have for the underlying tool. Directory connectors work on every Claude plan, including free, as of August 2026.
- The practical difference between connectors is what Claude is allowed to do once attached: some only read, the best ones act. For each entry we state plainly what Claude can do after you connect it.
- This list is written by the team that runs its own MCP server, a live 47-tool server for Gmail shared inboxes, so we describe setup and permissions from experience rather than from a scraped directory.
Table of contents
- How this list was chosen
- The twelve best Claude connectors at a glance
- 1. Drag: run a shared Gmail inbox from Claude
- 2. Notion: give Claude your company's knowledge
- 3. Zapier: one connector that reaches almost everything
- 4. Asana: project status without the status meeting
- 5. Linear: for product teams that live in issues
- 6. Atlassian: Jira and Confluence in both directions
- 7. HubSpot: your CRM, answering questions
- 8. Intercom: customer history where you are working
- 9. Stripe: payment answers without the dashboard
- 10. Airtable: the operational data teams actually run on
- 11. Canva: production design from a prompt
- 12. Slack: put the answers where the team talks
- Which connector should you connect first?
- How to connect any of these to Claude, step by step
- What about GitHub, databases, and the developer tools?
- Frequently asked questions
- Where this fits
The short version: an MCP server is what lets Claude actually work inside your business tools instead of just talking about them, and these are the twelve worth connecting if you run a team. If your team lives in a shared inbox, start with Drag, which is our own product and is disclosed as such below. If you want one connector that reaches nearly everything, start with Zapier. If your world is projects and tickets, go to Asana, Linear, or Atlassian. For customer data it is HubSpot and Intercom, for money it is Stripe, for documents Notion, for spreadsheet-style data Airtable, for design Canva, and for team chat Slack. Everything on this page can be attached from inside Claude in a few minutes, works on Claude's paid and free plans as of August 2026, and costs nothing beyond the subscription you already pay for the underlying tool.
We publish and maintain our own MCP server, so this list is written from the builder's side of the protocol, not from a scraped catalog. Most pages ranking for this search are lists of developer tools for Claude Code: databases, GitHub, browser automation. Useful if you write software, useless if you run a support queue or a sales pipeline. This page is the business list.
How this list was chosen
Three rules governed every entry:
- It must be live and attachable today. Every connector here is in Claude's own connector directory or is an official server published by the vendor. Nothing "coming soon", nothing you have to self-host from a code repository.
- It must do business work. Tools for running a team: email, projects, customers, money, data, content. Not tools for writing code, which is what most pages ranking for this search cover.
- Capabilities are stated plainly, from the vendor's own documentation. Where a vendor makes a claim, we attribute it as their claim. We have not run a lab test on all twelve, and unlike most pages on this topic we will not pretend to have done so. What we know firsthand is what it takes to build and run one of these servers, because we run one.
One definition before the list, because the vocabulary is messy. A connector is what you click in Claude's settings. An MCP server is the machinery behind it, the open standard (Model Context Protocol) that tells Claude what a tool can do. Every connector on this page is an MCP server under the hood, so for a buyer the two words mean the same thing.
The twelve best Claude connectors at a glance
| Connector | Category | What Claude can do once connected |
|---|---|---|
 Drag | Shared inbox and email | Read, triage, reply to, and organize a team's shared Gmail inbox, WhatsApp included; 47 tools |
 Notion | Docs and knowledge | Search your workspace, read and create pages, query databases |
 Zapier | Automation | Trigger actions across thousands of connected apps from one connector |
 Asana | Project management | Read projects and tasks, create and update work, summarize status |
 Linear | Product and issue tracking | Search, create, and update issues and projects |
 Atlassian | Jira and Confluence | Work with Jira tickets and Confluence pages in both directions |
 HubSpot | CRM | Look up contacts, companies, and deals, and update CRM records |
 Intercom | Customer support | Pull conversation history and customer context into any chat |
 Stripe | Payments | Look up customers, payments, subscriptions, and invoices |
 Airtable | Structured data | Query and update bases, the operational spreadsheets teams run on |
 Canva | Design and content | Generate and edit designs from a conversation |
 Slack | Team chat | Search messages and channels, post updates where the team already talks |
All twelve are free to connect: you pay for the underlying tool, not for the connector. The sections below cover what each one is actually for.
1. Drag: run a shared Gmail inbox from Claude
What's waiting in support from overnight? Draft replies to the three oldest.
Found 9 open threads from overnight in the Support board. Three drafts are ready for your review; nothing was sent.
Drafting needed your permission the first time. Sending always does.
Full disclosure first: Drag is our product, and this is the connector we built. It is on this list because a shared inbox is where a business team most obviously needs an assistant that can act, and as of August 2026 Drag is one of very few shared inbox tools with a live MCP server at all.
Connected, Claude gets 47 tools across the whole workspace: it can find and read email threads, draft and send replies, move cards across boards, assign conversations, apply labels, search your knowledge base, send WhatsApp messages, and read response-time analytics. In practice that means you can ask Claude "what's waiting in support from overnight, and draft replies to the three oldest" and it does the work in the inbox your team already shares. Setup uses a secure connect flow: you click Connect in Claude, paste your DragApp API key once from Settings, then Integrations inside Drag, the key is verified and handed to Claude as its access token, and the MCP service stores nothing. Claude asks permission per tool, so you decide whether it may send or only read.
Drag itself is a shared inbox for Gmail teams from $12 per user per month as of August 2026, with AI included from $18. Try Drag free for 7 days, no card required, and the full setup guide takes about two minutes to follow.
What the 47 tools cover:
- Find, read, and filter email threads across your boards
- Draft and send replies, or start new emails and WhatsApp messages
- Move, assign, label, and archive conversations
- Search your knowledge base and reuse article content in replies
- Create and update cards, tasks, and board columns
- Read response-time and team activity analytics
AI Platform
The inbox your team and your AI work in together
Shared inbox, live chat, and AI in Gmail, with an MCP server your AI tools can drive.
2. Notion: give Claude your company's knowledge
What does our onboarding doc say about refunds?
From "Customer Onboarding v3": refunds inside 30 days are approved by support directly; after 30 days they escalate to finance.
Illustrative conversation, shortened.
Notion is where many teams keep everything: wikis, meeting notes, project docs, structured databases. Its connector lets Claude search the workspace, read pages, create new ones, and query databases, which turns "check the onboarding doc" from a tab-switch into a sentence. The strongest everyday use is retrieval: asking Claude a question and having it answer from your own documentation rather than from the open internet. Teams that keep procedures in Notion get something close to an instant internal help desk.
What Claude can do with Notion connected (23 tools as of August 2026):
- Search the whole workspace, plus connected sources like Slack, Google Drive, and Jira
- Read any page or database it has permission to see
- Create and update pages, databases, and views
- Query databases for structured answers, not just text
- Read and add comments, and look up teammates
3. Zapier: one connector that reaches almost everything
Add this lead to our newsletter list and notify the sales channel.
Done. Lead added to the list and the sales channel was notified.
Illustrative conversation, shortened.
Zapier's connector is the pragmatic answer when the tool you need is not on this page. Rather than exposing one product, it exposes Zapier's catalog of connected apps, thousands of them by Zapier's own count, so Claude can trigger actions in tools that have no connector of their own. The trade-off is directness: you are working through Zapier's account limits and pricing tiers, and multi-step actions need a Zap behind them. As a bridge to the long tail of business software, nothing else on this list matches it.
What Claude can do with Zapier connected:
- Run actions across more than 9,000 apps and 30,000 actions, by Zapier's own count as of August 2026
- Send emails and messages in tools that have no connector of their own
- Update spreadsheets, calendars, and CRM records
- Chain a lookup in one app with an action in another
4. Asana: project status without the status meeting
Create tasks for everything we just agreed in this conversation.
Created 3 tasks in "Q3 Launch": pricing page copy (Fri), legal review (Wed), changelog draft (Thu). All assigned.
Illustrative conversation, shortened.
Asana's connector gives Claude read and write access to projects and tasks: it can list what is overdue, create tasks from a conversation, update assignees and due dates, and summarize where a project stands. The obvious win is turning any discussion into tracked work ("create tasks for everything we just agreed") and the quieter one is reporting, since Claude can read across projects and write the Monday summary nobody enjoys writing.
What Claude can do with Asana connected:
- Search across tasks, projects, portfolios, and goals
- Pull filtered task lists, including everything assigned to you
- Create up to 50 tasks in one request, or a whole project with sections
- Update tasks in bulk: assignees, dates, status
- Add comments and post project status updates
5. Linear: for product teams that live in issues
File this bug from the customer email, priority high.
Created DRA-214 "CSV export drops header row", priority High, labeled bug, added to the current cycle.
Illustrative conversation, shortened.
Linear is the issue tracker of choice for many product and engineering teams, and its connector was one of the earliest official remote MCP servers. Claude can search issues, file new ones with proper labels and priorities, update status, and summarize a cycle. For a business reader the point is triage: customer feedback arriving in support can become a well-formed Linear issue without anyone re-typing it, especially when paired with a support-side connector like Drag or Intercom.
What Claude can do with Linear connected:
- Find, create, and update issues with labels, priority, and cycle
- Work with projects and comments
- Turn a pasted customer email into a well-formed issue
6. Atlassian: Jira and Confluence in both directions
Summarize sprint 14 for stakeholders who do not open Jira.
Sprint 14: 21 of 24 issues done. The 3 carrying over are all in the reporting epic; nothing customer-facing slipped.
Illustrative conversation, shortened.
The Atlassian connector covers the two tools that run large-company work: Jira for tickets and Confluence for documentation. Claude can search and create Jira issues, move them through workflows, and read and draft Confluence pages. If your company is big enough that "raise a ticket" is a sentence people say out loud, this is the connector that makes Claude useful inside that reality, from writing well-formed tickets to summarizing a sprint for stakeholders who do not open Jira.
What Claude can do with Atlassian connected:
- Search Jira with plain questions, it writes the query language for you
- Create, edit, and transition Jira issues, and add comments and worklogs
- Search Confluence and read any page or space
- Create and update Confluence pages and comments
7. HubSpot: your CRM, answering questions
What do we know about Acme Corp before my 3pm call?
Acme Corp: 2 open deals ($14k expansion, $6k renewal), last touch Jul 28. Renewal owner flagged pricing sensitivity in notes.
Illustrative conversation, shortened.
HubSpot's connector lets Claude look up contacts, companies, and deals, and update records. The everyday value is context on demand: "what do we know about this company before my call" becomes a question you ask in chat, answered from your own CRM instead of your memory. Sales teams also use it for hygiene, the unglamorous work of logging notes and updating deal stages, which is exactly the work an assistant should absorb.
What Claude can do with HubSpot connected:
- Read and update contacts, companies, deals, tickets, quotes, and invoices
- Log engagements: calls, emails, meetings, notes, and tasks
- Read marketing campaigns, landing pages, and blog posts
- Look up owners, teams, and reporting structure
8. Intercom: customer history where you are working
What has this customer raised with us before?
4 previous conversations, three about billing. The unresolved theme: invoices arriving after their finance cutoff date.
Illustrative conversation, shortened.
Intercom's connector brings support conversation history and customer context into Claude. Ask what a customer has raised before, get a summary of their history, and use it while drafting anything from a renewal email to a product decision. It pairs naturally with the project-side connectors: reading what customers say in Intercom and turning it into tracked work in Linear or Jira is the workflow the whole MCP idea was made for. Intercom also sells its own AI agent, Fin; our resolution-rates audit covers how to read that category's claims.
What Claude can do with Intercom connected (13 tools as of August 2026):
- Search conversations with filters: state, author, assignment
- Pull a full conversation with every message
- Search contacts and companies
- Read, search, create, and update Help Center articles
9. Stripe: payment answers without the dashboard
Has invoice 4821 been paid, and when does their plan renew?
Invoice 4821 was paid Aug 2. The subscription renews Sep 1 on the annual plan.
Illustrative conversation, shortened.
Stripe's connector lets Claude look up customers, payments, subscriptions, and invoices. For founders and finance-adjacent people this replaces a whole class of dashboard visits: has this customer paid, when does their subscription renew, what did we refund last month. Treat write-access with care here for the obvious reason that this connector touches money; Claude's per-tool permission prompts are exactly the control to use, and read-only is the sensible default.
What Claude can do with Stripe connected:
- Read across customers, charges, invoices, subscriptions, disputes, payouts, and balance
- Create refunds and invoices, and update subscriptions, where you allow write access
- Search Stripe's own documentation for how-to answers
10. Airtable: the operational data teams actually run on
Which items in the inventory base are below reorder level?
6 records match: all in the packaging category. Lowest stock is shipping boxes at 12 units against a reorder level of 50.
Illustrative conversation, shortened.
Airtable sits between spreadsheet and database, and a surprising amount of real business operations lives in it: content calendars, applicant tracking, inventory, CRM-lite. Its connector lets Claude query and update bases, which means natural-language questions against your own operational data ("which items are below reorder level") and bulk-ish updates without formula wrangling. If your team's source of truth is an Airtable base, this connector makes that truth conversational.
What Claude can do with Airtable connected:
- Query records in any base it can see, with filters
- Update records from a conversation
- Answer natural-language questions against your operational data
11. Canva: production design from a prompt
Resize the launch banner for LinkedIn and X.
Two resized designs are ready in your Canva projects, one per platform, copy and layout preserved.
Illustrative conversation, shortened.
Canva's connector lets Claude generate and edit designs from a conversation, which lands squarely in the marketing workflow: social posts, one-pagers, simple ads, resized variants. It will not replace a designer, and it does not try to. What it removes is the blank-canvas step for the everyday assets that teams otherwise queue behind a busy design resource.
What Claude can do with Canva connected:
- Generate new designs from a described brief
- Edit and resize existing designs for different platforms
- Work from your existing projects and brand assets
12. Slack: put the answers where the team talks
Find the thread where we decided the pricing change.
Found it: #pricing, March 14. Decision: move the entry tier to $12 at the April billing cycle. Link is below.
Illustrative conversation, shortened.
Slack's connector lets Claude search messages and channels and post updates. The search half is quietly the valuable one: an enormous amount of company knowledge exists only as a Slack thread someone half-remembers, and Claude can find it. The posting half turns any of the workflows above into a shared one, since a summary Claude wrote from Asana or Drag can land directly in the channel where the team will read it.
What Claude can do with Slack connected:
- Search messages and channels for decisions and context
- Post messages and summaries where the team reads them
- Turn a found thread into input for any other connector in this list
Which connector should you connect first?
One is a decision, twelve is a mess. Pick by where your team's real work sits:
- Your team answers customers by email: Drag first, Intercom if your support lives in chat instead.
- You run projects and want fewer status meetings: Asana, or Atlassian if your company already says "raise a ticket".
- You build product: Linear, then pair it with whichever support connector holds your customer feedback.
- You do sales: HubSpot, with Stripe alongside if you also chase invoices.
- Your company's brain is in documents: Notion, and Slack for everything that was decided in a thread instead of a doc.
- The tool you need is not on this page: Zapier, the bridge to the long tail.
Connect one, use it for a week, then add the second. The pattern that compounds is pairs: a connector that reads customer reality (Drag, Intercom) plus one that creates tracked work (Asana, Linear, Atlassian).
How to connect any of these to Claude, step by step
The flow is the same for all twelve, and takes a few minutes:
- Open the connector directory. In Claude, go to Settings, then Connectors. Or, faster, type "/" in any chat and choose Manage connectors.
- Find the tool and click Connect. Browse or search the directory, click the connector you want.
- Approve access in the tool's own sign-in flow. You authenticate with the vendor directly, in their screen, with your existing account. Drag's flow, for example, opens a hosted connect page where you paste your API key once from Drag's Settings, then Integrations; the key is verified and handed to Claude as its access token, and nothing is stored by the MCP service.
- Set per-tool permissions. Claude lists everything the connector can do and asks before acting: allow once, always allow, or deny, tool by tool. Sensible default: allow reading, approve anything that sends, pays, or deletes case by case.
- Ask for something real. The fastest proof is a question you would otherwise open the tool to answer: "what's waiting in support from overnight" or "has invoice 4821 been paid".
Directory connectors are available on every Claude plan as of August 2026, including free, on web, desktop, and mobile. Our Gmail walkthrough shows the flow end to end with screenshots.
What about GitHub, databases, and the developer tools?
They are real and good, and they are deliberately not on this list. GitHub, PostgreSQL, Sentry, Figma, browser automation, and the rest of the developer set are what most "best MCP servers" pages cover, because those pages are written for people building software with Claude Code. If that is you, any of the developer-focused lists will serve. This page exists for the other reader: the one whose work is customers, projects, and money, who was underserved by every list we found while researching this one.
Frequently asked questions
What is an MCP server, in plain terms?
MCP (Model Context Protocol) is an open standard that describes a tool's abilities to an AI assistant. An MCP server is a live service that speaks that standard for one product, so Claude knows it can, say, search threads or create tasks there. In Claude's interface, MCP servers appear as connectors. One protocol, many tools, no custom integration per app.
Do Claude connectors cost anything?
The connectors themselves are free as of August 2026. You need an account with the underlying tool, on whatever plan unlocks the features Claude will use, and directory connectors work on every Claude plan including free. Custom connectors, meaning servers you add by URL rather than from the directory, are limited to one on Claude's free plan.
Are MCP connectors safe to give access to business data?
The controls are better than most integrations: you approve access through the vendor's own sign-in, and Claude asks permission per tool, so a connector can be read-only in practice even if it offers write tools. The sensible policy is deny-by-default on anything that sends, pays, or deletes, then allow specific tools as trust builds.
What is the difference between a connector and an MCP server?
For a buyer, nothing that matters: a connector is Claude's word for an MCP server you can attach from its settings screen. The distinction matters only to builders, where the MCP server is the software the vendor runs and the connector is its listing inside Claude. Every entry on this page is both.
Can Claude send emails and messages through these connectors?
Yes, where the connector offers write tools and you permit them. Drag's connector can draft and send replies in a shared Gmail inbox, Slack's can post messages, and Zapier's can trigger sends in other tools. Claude asks before using a write tool, so sending is always something you switched on, not a default.
Where this fits
If the shared inbox use case is the one that grabbed you, the connect guide gets Claude attached to a Drag workspace in a few minutes, the MCP docs list all 47 tools, and the day-to-day guide shows what running an inbox from Claude actually looks like. For the wider thinking: why support tools need MCP servers, MCP vs API, and the AI shared inbox guide for choosing the inbox itself. And if you connect one thing from this page today, connect the tool your team opens most: the assistant is only as useful as the work you let it reach.
Co-founder
Building Drag for nearly ten years: shared inboxes, boards, and now the AI and agent layer, all on Gmail, plus HeyHelp for the personal inbox. Writes the honest versions of the comparisons.
