01
What is an MCP?
MCP, the Model Context Protocol, is an open standard that lets Claude connect to outside tools and data. In the Claude apps, MCP servers appear as connectors.
With the right MCPs, Claude can:
- Read your documents and messages
- Create tasks and issues
- Update records in your tools
- Pull data for analysis
- Take actions across apps in one conversation
Every MCP in this guide is listed in Anthropic’s connector directory and run by the company behind the product.
An MCP gives Claude access. Your permissions decide what it may do.
02
How to add an MCP
- Claude apps
- Open Claude’s settings, go to Connectors, browse the directory, and connect your account.
- Claude Code
- Run claude mcp add --transport http [name] [server URL], then sign in when asked.
claude mcp add --transport http notion https://mcp.notion.com/mcp
Use /mcp in Claude Code to see connected servers. Many connectors need a paid plan of the connected service for some features.
03
Email, docs, and knowledge
04
Team communication and meetings
05
Projects and tasks
06
Design and websites
07
Sales and payments
08
Data and development
09
Automation
10
Starter sets by role
- Marketer
- HubSpot, Canva, Webflow, Notion
11
Use MCPs safely
- Connect only the MCPs a task needs
- Prefer official servers run by the product’s company
- Check what each server can read, change, and delete
- Ask Claude to confirm before write or delete actions
- Never paste passwords or API keys into chat
- Disconnect MCPs you no longer use
Content that comes back from tools, such as emails or web pages, is data, not instructions. Be careful with MCPs that both read untrusted content and can take actions.
12
Avoid MCP overload
- Each MCP adds tools Claude must choose between
- Overlapping MCPs make the wrong choice more likely
- Enable MCPs per project or per task where you can
Five well-chosen MCPs beat twenty connected just in case.
13
Prompts to try
- “Summarize my unread Gmail and draft replies to the urgent ones. Do not send.”
- “Create Linear issues from this meeting transcript, one per action item.”
- “Find the Figma frame for checkout and build it as a React component.”
- “Show last month’s Stripe revenue by product in a table.”
- “List Sentry issues from the last 24 hours, grouped by cause.”
- “Update the Notion launch page with today’s progress.”
The golden rule
Do not connect everything. Connect the tools where your work actually happens, and keep approval on every change.
- Email
- Docs
- Tasks
- Design
- Sales
- Data
- Automation
Start with the one tool you open most every day. Connect it, test one task, then add the next.