← all free guides

free field guide workflows

20 Claude Connector Setup Guide

Choose and connect twenty useful Claude integrations with a permission-first setup checklist.

20 Claude Connector Setup Guide

Claude's connector directory changes over time and availability can differ by plan or administrator. Use this as a job list, then choose the current verified connector in Claude rather than pasting an unreviewed server URL.

What this helps you do

Match twenty common services to a real job and install only the connections your workflow needs.

Before you start

Open Claude and go to Customize → Connectors → + → Browse connectors. For work accounts, confirm your administrator allows the integration. Review the provider, requested scopes, data policy, and whether actions are read-only or can write.

Terms to know

  • Connector: an integration that lets Claude access another service.
  • MCP: the protocol many connectors use to expose tools and data.
  • Scope: the specific account permission requested during sign-in.

Step-by-step

Check the current Claude connector directory for these jobs:

  1. Perplexity for sourced web research.
  2. Firecrawl for reading public websites.
  3. Playwright for browser testing.
  4. Composio for supported app actions.
  5. Google Drive for files.
  6. Gmail for mail search and drafting.
  7. Google Calendar for schedules.
  8. Slack for channel context.
  9. Notion for workspace pages.
  10. GitHub for repositories and issues.
  11. Linear for product issues.
  12. Jira for team tickets.
  13. Confluence for company knowledge.
  14. Figma for design context.
  15. Canva for supported creative workflows.
  16. Stripe for approved business data tasks.
  17. HubSpot for CRM context.
  18. Salesforce for CRM context.
  19. Dropbox for files.
  20. Microsoft 365 services for mail, files, calendars, or collaboration.

Install one at a time. Run a read-only test before allowing a connector to create, send, edit, or delete anything.

Copy this

Copy this

CONNECTOR REVIEW
Connector and publisher: [NAME]
Job it must do: [ONE JOB]
Requested permissions: [LIST]
Data it can reach: [LIST]
Read actions allowed: [LIST]
Write actions allowed: [NONE OR LIST]
Test account or folder: [NAME]
Human approval required before: send, publish, edit, delete, payment, permission change
Rollback or disconnect path: [STEPS]

Things to know

The directory and verified badges help with discovery, but you still need to check permissions. A connector can expose sensitive mail, files, customer records, or code. Use the narrowest account and scope.

If something goes wrong

Disconnect the connector, revoke its access in the source service, and review recent activity. If it is not visible in the directory, check plan, region, and administrator restrictions before using a custom connector.

Final check

You pass when one read-only test returns the expected item and no unrelated folders, mailboxes, repositories, or records are accessible.

paid brand collaborations

teamwork makes the dream work.

I love working with brands that make AI easier to understand, operate ethically, and share what they know generously. If that sounds like you, drop your info below.

is this a paid opportunity?