Connectors and Integrations

So far, Cowork has been working with files on your computer. That’s powerful on its own. But the real multiplier comes when you connect it to the tools you already use.

🔄 Quick Recall: In the previous lesson, you completed a full project using the Context + Deliverables + Format + Checkpoint + Refine pattern. Now we’ll expand Cowork’s reach beyond local files.

What Are Connectors?

Connectors let Cowork reach into external tools — Google Drive, Gmail, Slack, Notion, GitHub, Jira, and more. Instead of downloading a file from Drive, giving it to Cowork, and uploading the result back, you just say:

Read the Q1 report from Google Drive and summarize it.

Cowork uses the Drive connector to access the file directly. No downloads, no uploads, no copy-pasting between tabs.

There are 38+ connectors available as of March 2026, and they’re all free for paid plans. The technology behind them is called MCP — Model Context Protocol — an open standard that bridges AI tools with external data sources.

The Most Useful Connectors

You don’t need all 38. Here are the ones most people start with:

Setting Up a Connector

Let’s connect Google Drive as an example:

1. In Claude Desktop, go to the Cowork tab
2. Open Settings or the Customize menu
3. Find Connectors and click Google Drive
4. Click Connect — you’ll be redirected to Google’s OAuth screen
5. Grant the permissions Claude needs (read access, at minimum)
6. Done. Cowork can now access your Drive files

The process is similar for every connector: find it, click connect, authorize. Most take under a minute.

✅ Quick Check: What’s the technology standard that powers Cowork connectors? (MCP — Model Context Protocol)

Real Workflows With Connectors

Here’s where things get practical. A few workflows that combine connectors with Cowork’s file skills:

Email + Drive: Weekly Report Automation

1. Read the last 5 emails from [client name] in Gmail
2. Read the project tracker spreadsheet in Google Drive called "Project X Tracker"
3. Create a weekly status report combining email updates with tracker data
4. Save it as "weekly-status-[date].md" in my local folder
5. Draft a reply email to the client with a summary of progress

Slack + Local Files: Meeting Prep

1. Read the last 20 messages in the #product-team Slack channel
2. Read my notes file "product-meeting-prep.md" from this folder
3. Update my notes with anything mentioned in Slack I haven't captured yet
4. Create an agenda for tomorrow's meeting based on the combined information

GitHub + Local: Code Documentation

1. Read the README.md from our GitHub repo [repo-name]
2. Read the recent pull request descriptions from the last 2 weeks
3. Create an updated changelog.md file with a summary of recent changes
4. Flag any PR that's still open and needs review

These workflows take 5-10 minutes of Cowork’s time and save you 30-60 minutes of manual work. The connectors make it possible because Cowork doesn’t have to ask you to go fetch data — it gets it directly.

Connector Reliability — Be Honest About It

Here’s the thing nobody mentions in marketing materials: connectors don’t always work perfectly. User reports from early 2026 mention occasional issues:

• Gmail connector sometimes fails to load older emails
• Drive access can be spotty with shared folders you don’t own
• Some connectors disconnect after a few days and need re-authorization

This isn’t a dealbreaker — it just means you should have a fallback. If a connector isn’t cooperating:

1. Disconnect and reconnect — fixes most temporary issues
2. Export locally — download the file from Drive/email/Slack and put it in your Cowork folder
3. Use the Chrome extension — some users report it’s more reliable for web-based tools

The local file approach always works. Connectors are a convenience layer on top.

Custom Connectors (MCP)

If you’re slightly technical (or have a tech team), you can create custom connectors using remote MCP servers. This lets Cowork connect to:

• Your company’s internal APIs
• Custom databases
• Proprietary tools
• Any service with an API

Anthropic’s GitHub repository (anthropics/knowledge-work-plugins) has open-source examples. But this is intermediate-level territory — for now, the built-in connectors cover most needs.

What Not to Connect (Yet)

A practical note: don’t connect everything on day one. Start with one or two connectors you’ll actually use this week. Reasons:

• Each connector increases Cowork’s context load
• More connections means more permission surfaces
• You want to build trust incrementally

A good progression:

• Week 1: Google Drive (or OneDrive) — your primary document source
• Week 2: Add email (Gmail or Outlook) — for workflows that involve correspondence
• Week 3: Add a project tool (Slack, Notion, or Jira) — for team workflows

Key Takeaways

• 38+ connectors available — Google Drive, Gmail, Slack, Notion, GitHub, and more
• All free for paid plans — no additional cost
• Setup is simple: find the connector, click connect, authorize
• Connectors extend Cowork beyond local files to your entire tool stack
• Reliability isn’t perfect — have a local file fallback ready
• Add connectors incrementally, not all at once

Up Next

You’ve got Cowork connected to your tools. Next lesson is the tips, tricks, and troubleshooting guide — the stuff you only learn after using Cowork daily for a few weeks. We’ll shortcut that learning curve for you.