Claude connector guide
Claude connectors for sole traders and small teams: a practical starting stack
You do not need to understand the Model Context Protocol to benefit from it. Anthropic's Connectors Directory is a browsable, in-app catalogue that lets Claude read from—and, where you allow it, act inside—the tools you already use: your inbox, your files, your CRM, your invoicing. Connectors are free to add; a paid Claude plan is required to use them, and the connected service's own subscription still applies. This guide is written for the person doing the work themselves, not an IT department.
What a Claude connector actually is
A connector is a finished, hosted bridge between Claude and an outside service, built on MCP—the open standard Anthropic created so any AI system can talk to any tool through one consistent protocol. You do not install software or write configuration. You open the Connectors Directory inside Claude (on web, Desktop, iOS or Android), find the service, and authorise it with the same OAuth sign-in you would use for any other app.
That matters for a sole trader because it removes the two usual blockers: no developer time to wire up an integration, and no separate vendor relationship to manage. The trade-off is that you are granting a real, working connection to a real account—so the questions below are worth five minutes before you click connect.
- Free to add the connector itself.
- A paid Claude plan is required to use connectors.
- The connected service's own subscription or plan still applies separately.
- Available on Claude web, Claude Desktop and Claude for iOS/Android.
Read the permission screen like a contract
When you authorise a connector, the OAuth consent screen tells you exactly what Claude can see and do—which mailbox, which drive, which read or write scopes. That screen, not this guide and not Anthropic's marketing copy, is the authoritative record of what you are granting. Sole traders often connect a personal account because it is the only one they have; if the workflow is business-critical, consider a dedicated work identity instead so access is easy to review and revoke later.
Custom and remote MCP connectors exist for services without a directory listing, but they are not vetted by Anthropic the way directory connectors are. Treat a custom connector as a bigger trust decision, and confirm what data it can reach before pointing it at anything sensitive.
- Check the account or workspace the connector is bound to before authorising.
- Prefer read-only or draft-only scopes for the first two weeks.
- Note the connection date somewhere so you remember it exists.
- Revisit and remove anything you are not actively using.
A sensible first stack for one person
Most sole traders get the earliest value from three connections, added one at a time: an inbox for conversation context, a files or notes source for approved material, and one system of record for the commercial side of the business—payments, invoicing or a lightweight CRM.
Do not connect everything in one sitting. Prove one reviewable workflow—for example, drafting a client follow-up from a Gmail thread without sending it—before adding the next connection. A smaller, trusted stack beats a wide one you cannot account for.
- Inbox: Gmail or Outlook Mail for conversation context.
- Files: Google Drive, Notion or Dropbox for approved source material.
- Commercial record: Stripe for payment context, HubSpot for a lightweight CRM.
- Calendar: Google Calendar or Outlook Calendar once the first workflow is proven.
Keep the consequential steps human
Claude can draft a client email, summarise a payment dispute or prepare a proposal from your notes—but sending, invoicing, publishing and any change to a live financial record should stay a deliberate, reviewed step you take yourself, not an automatic action. This is not a Claude-specific caution; it is the same rule that applies to any AI connection with real-world reach.
For a sole trader, the practical version of this is simple: use Claude to prepare the first draft and gather the context, and keep the final send, save or payment action in your own hands until you have a track record of accurate output.
- Require a visible draft before any send, publish or payment action.
- Exclude full payment card data and credentials from anything you ask Claude to read.
- Ask Claude to cite the source record for any factual claim in a client-facing draft.
- If something looks off, check the source—do not assume the summary is complete.
Why this is worth doing now
The return-on-effort case for a one-person business is straightforward: a handful of narrow, reviewed connections can remove real weekly admin—chasing a thread, finding a file, drafting a follow-up—without hiring anyone or learning a new platform. The Connectors Directory is designed to be browsable without technical help, which is precisely the audience this guide is written for.
Start with the smallest stack that proves the pattern, measure whether it actually saves time and reduces mistakes, and only then decide whether a second or third connection earns its place.
