There are two main ways to connect outside apps and data to Claude — connectors, which you switch on with a few clicks, and the MCP (Model Context Protocol) servers that make those connections work. There are so many that it is easy to lose track of what exists and where to start. This page is a category-by-category map of the common connectors and MCP servers, linking each one to a deeper setup guide.
Connectors and MCP, in one line
Connector — a "connect switch" in Claude settings that lets Claude use an app once you turn it on. MCP (Model Context Protocol) — the shared standard that makes the connection work, like a standard plug. Just as USB-C lets one port handle a charger, monitor, or keyboard, MCP lets many apps connect to Claude the same way.
New to the idea? Start with What Is MCP — a simple explanation and What Is MCP? Architecture and security. For the exact steps, see How to connect & use MCP (4 ways).
The catalog, by category
The lists below are representative examples to help you get oriented. Which connectors you can use depends on your plan and changes often, so check the connector screen in Claude settings and the official connector guide for the full, current list.
1. Productivity, docs & collaboration
The everyday tools — docs, notes, chat. Examples: Notion, Google Workspace (Drive, Calendar, Gmail), Slack, Box, Dropbox. Ready guides — Notion, Google, Slack.
2. Project & issue tracking
Tools that track tasks and issues. Examples: Linear, Jira/Confluence (Atlassian), Asana.
3. Development, code & ops
Developer infrastructure — code hosting, deploys, error tracking, databases. Examples: GitHub, Sentry, Supabase, Vercel, Cloudflare. Developers should start with Claude Code MCP setup and Claude Code GitHub integration.
4. Design & content
Design files and visual content. Examples: Figma, Canva. Guide — Figma (design to code).
5. Payments, commerce & financial data
Tools that handle payments and financial data. Examples: Stripe, Square, PayPal, Plaid. Because they touch sensitive data, granting only the narrow permissions you need matters even more (see security below).
6. Local MCP servers for developers
MCP servers you run yourself on your machine or a server. Examples: filesystem, databases such as PostgreSQL, browser automation (Playwright, Puppeteer), web search. For picks by use case see Recommended MCP servers, and to find them see Where to find MCP servers.
How to add a connector (in brief)
For most, you open Claude settings → Connectors, turn on the service, and sign in (grant access). For services not in the directory, you can add a "custom connector" with a remote MCP server URL. Step-by-step details are in How to connect & use MCP (4 ways).
Using them safely
Connectors reach your account and data, so it matters whether the provider is trustworthy and whether you grant only the permissions needed. For the criteria see MCP connector security; if a connection fails, see the troubleshooting guide.
Where to find the full, current list
Connectors are added continually. The most accurate list is the connector screen in Claude settings; the official explanation is the Anthropic connector guide, and the developer-facing server list is the official MCP registry.
Individual setup guides — Connectors: Linear, Jira & Atlassian, Asana, Canva, Zapier. MCP servers: Filesystem, GitHub MCP, PostgreSQL MCP, Playwright MCP.