Once you know how to connect MCP, the next question is "what should I connect?" Here we organize the frequently recommended MCP servers of 2026 by use case. (These are examples, not a ranking; for the concept see What is MCP?)
Representative servers by use case
- Dev: GitHub (PRs, issues, code search), Sentry (error tracking), Supabase (DB/backend), Context7 (up-to-date library docs).
- Database: PostgreSQL / SQLite connectors for direct queries.
- Docs & project management: Notion (wiki/DB), Linear (issues/sprints), Atlassian/Jira (tickets).
- Files & storage: Google Drive (cloud docs), Filesystem (local files).
- Communication: Slack (summarize, search, post).
- Browser & web scraping: Playwright (browser automation, Microsoft), Firecrawl (web scraping).
- Business & payments: Stripe (payments), Shopify (commerce), HubSpot (CRM).
- Automation: Zapier (hundreds of apps via one connection).
Many of these connect straight from the claude.ai connector directory (Google Drive, Slack, GitHub, Notion, etc.); the rest are added as custom connectors (Settings > Connectors) or in Claude Code (claude mcp add).
How to choose
- Start with 2-3 you use daily. You don't need to add everything at once.
- Don't add too many. Many note that going beyond 5-7 at once bloats the tool list and degrades the agent's decision quality.
- Claude Code has built-in file tools, so a Filesystem MCP is usually redundant there.
Auth & security notes
- Auth varies: OAuth login (Linear, Sentry), API key (Firecrawl), no-credential local (Playwright).
- OAuth servers inherit your permissions — the agent can close real tickets or post messages as you, so start with read-only scopes.
- Connect only trusted servers (official/verified). See the security check in the MCP connection guide.