Connectors: which to enable, which to disable, and why it matters
Connectors give Claude access to your tools. But having all of them on all the time costs tokens and introduces noise. Here is how to manage them.
Connectors link Claude to the tools you already use — Google Drive, Slack, Notion, Jira, GitHub, Dropbox, and others. Once connected, Claude can search your documents, read messages, and pull in relevant context from these services.
This is powerful. It is also easy to mismanage.
How connectors affect your experience
When a connector is active, Claude can pull content from that service into your conversation. This happens automatically — if you ask about a project and your Jira connector is active, Claude might search your Jira board for relevant issues.
Every piece of content pulled in consumes tokens. A Jira issue with 40 comments pulled into context can be thousands of tokens. Multiply that by several connectors pulling in content simultaneously, and you can burn through your usage limits quickly on context you didn't need.
The principle: connect what you need, disconnect what you don't
Think of connectors like browser tabs. Having 30 tabs open doesn't make you more productive — it makes everything slower and harder to find. Same with connectors.
For each conversation or Project, ask: what external information does Claude actually need?
Writing a marketing brief? You need Google Drive (for brand docs) and maybe Notion (for strategy docs). You do not need Jira, GitHub, or Slack.
Debugging a customer issue? You need your knowledge base connector and maybe Jira. You do not need Google Drive or Dropbox.
How to manage connectors
Per conversation
Toggle connectors on/off in the message bar before you start. Get in the habit of disabling the ones you won't use. It takes 5 seconds and saves tokens.
Per Project
In your Project settings, configure which connectors are available. This is the better approach for teams — the admin decides what's relevant for each use case, and team members don't need to think about it.
Recommended Project-connector mapping:
- CS team Project: Knowledge base, CRM, ticketing system
- Marketing Project: Google Drive (brand assets), Notion (strategy docs)
- Sales Project: CRM, Google Drive (proposals and decks)
- Engineering Project: GitHub, Jira, Confluence
- Operations Project: Google Drive, Notion, Slack (for context searching)
For your own workflows
If you switch between different types of work throughout the day, toggle connectors as you switch context. Writing mode: Drive + Notion. Research mode: web search + Drive. Issue triage: Jira + knowledge base.
What happens when too many connectors are active
Three things, all bad:
- Token waste. Claude pulls in context you didn't ask for and didn't need. Each retrieval costs tokens.
- Slower responses. More connectors means more sources to search. Responses take longer.
- Noise in outputs. Claude might reference a Slack thread from three months ago that's no longer relevant, or pull in a draft Google Doc instead of the final version. More sources means more opportunities for irrelevant or outdated information to enter the conversation.
The admin checklist
If you are setting up Claude for a team:
- Audit which connectors your team actually uses. Not which they could use — which they do use daily.
- Connect only those. You can always add more later.
- Set defaults per Project. Don't rely on individuals to manage their own connectors. Configure it once in the Project.
- Review quarterly. Services change, team needs change. Check whether your connector setup still matches how people actually work.
Security note
Each connector grants Claude access to read from an external service using someone's authentication. Make sure the person who connects the service has appropriate permissions — if they connect their personal Google Drive, Claude can access their personal files, not just work files. For team deployments, use service accounts or team-scoped authentication where available.