MCP Connectors & Integrations
Plugins extend Cowork beyond local files. MCP-compatible connectors let Claude read Gmail, Google Drive, Notion, Slack, and other services through structured API tools — with clear rules for personal vs. project-scoped access.
Combining Cowork with plugins
Cowork handles files on your computer. Plugins (connectors) add a second layer — live access to cloud apps and team tools. Install a connector once, authorize it, and Claude can call its tools during a Cowork task instead of opening each app by hand.
| Step | What you do |
|---|---|
| Install | Add a plugin from the connectors directory in Claude Desktop |
| Authorize | Sign in to Gmail, Drive, Notion, or Slack when prompted |
| Enable | Turn connectors on globally or inside a specific project |
| Run | Cowork calls connector tools as part of a multi-step task |
Plugins extend Cowork with structured access to external apps — no screen control required.
Common integrations
These four connectors handle email, files, docs, and team chat. Each exposes a fixed set of actions Claude can use during a task.
| Connector | What it does | Example prompt |
|---|---|---|
| Gmail | Read threads, draft replies, search by sender or date | “Summarize unread messages from legal@acme.com and draft a response.” |
| Google Drive | List files, read documents, save outputs to a shared folder | “Open Q3-budget.xlsx from the client folder and add this week's numbers.” |
| Notion | Fetch pages, update databases, pull meeting notes into a report | “Read the Sprint Retro page and turn action items into a task list.” |
| Slack | Read channel history, post updates, pull decisions from threads | “Check #product-updates for this week and add highlights to my status doc.” |
How MCP-compatible connectors work
MCP (Model Context Protocol) is the standard behind many Claude connectors. Instead of scraping a screen, the plugin registers tools — search_messages, read_file, list_pages — that Claude calls with your approval. Data flows in as structured text, not screenshots.
search, read, list, send
Project-scoped vs. personal connectors
When you enable a connector, choose whether it applies everywhere on your account or only inside one Cowork project. This keeps client data and team channels isolated.
Tied to your Claude account. Available in every Cowork project you open.
Good for: your inbox, personal calendar, account-wide tools you use everywhere.
Enabled only inside one Cowork project. Other projects cannot access that connection.
Good for: client workspaces, team Slack channels, shared Drive folders tied to one engagement.
| Personal | Project-scoped | |
|---|---|---|
| Availability | All Cowork projects on your account | Only the project where you enabled it |
| Typical apps | Gmail, personal calendar | Client Drive, team Notion, project Slack |
| Isolation | Shared across workspaces | Contained to one engagement |
| Setup | Authorize once in account settings | Enable per project in project settings |
Worked example
Client weekly status — three connectors, one task
- Open Cowork project Client-Acme with project-scoped Drive and Notion enabled.
- Personal Gmail connector stays available for your inbox.
- Run: “Read this week's Slack #client-acme posts, pull numbers from Drive/Q3-budget.xlsx, and draft a status email.”
- Claude calls Slack → Drive → Gmail tools in sequence; you approve each external read before it proceeds.
- Save the finished status doc to your local project folder.
Before you continue
- Plugins extend Cowork with Gmail, Drive, Notion, Slack, and other services.
- MCP connectors bring external data in through structured tools — not screen control.
- Personal connectors follow your account; project-scoped ones stay inside one workspace.
- Next: Tips & Best Practices — clear prompts, examples, and task breakdown for Cowork.
What's Next
Tips & Best Practices — clear prompts, examples, plan-first wording, task breakdown, and follow-ups.