In Lesson 27, you explored browser integration for web-based workflows. Now you will connect Cowork to the services where your real data lives — Google Drive, Slack, Jira, and dozens more — through Plugins and Connectors.
You learned about MCP (Model Context Protocol) in Lesson 12 — how developers create servers that expose tools to Claude Code. Plugins and Connectors bring the same capability to Cowork, but without requiring any development work.
A Plugin is a workflow package that bundles multiple capabilities into a single, installable unit. Think of it like an app on your phone — one download gives you everything you need.
A Plugin can contain any combination of:
You install a Plugin with one click from the Plugin directory, and all its components become available in your Cowork session.
Department-specific Plugin templates provide ready-to-use packages for common roles:
These templates are starting points. You can customize them by adding or removing individual components.
Connectors are one component within a Plugin. They are pre-packaged remote MCP servers that link Claude to external data sources.
Here is how the layers relate:
The Anthropic Connectors Directory lists 50+ Connectors across categories:
You don't write code. You don't configure servers. You authenticate, grant permissions, and Claude can access the data.
Connectors use remote MCP servers — hosted in the cloud by Anthropic and partners — rather than local servers running on your machine. This means Connectors work across all Claude platforms: web, desktop, mobile apps, and API.
MCP (Lesson 12) is for developers building custom integrations:
Connectors are for knowledge workers using common services:
The relationship: Connectors are MCP servers. Someone else built them, packaged them, and maintains them. You just use them.
When you add a Connector to Cowork:
From that point forward, Claude can reference data from the connected service alongside your local files.
Example: With the Google Drive Connector, you could ask:
"Look at the project planning document in my Google Drive, compare it to the local project files I showed you, and tell me what's missing from the local version."
Claude reads the Google Doc via Connector, reads your local files, and performs the comparison — all without you manually copying anything.
Some Connectors also render interactive apps inline in the chat. For example, a calendar Connector might display an interactive calendar widget where you can select dates directly, rather than typing them out.
In Claude Desktop (Cowork mode):
Each Connector has permission scopes:
Start with read-only access. Only enable read-write when you trust the workflow and understand what Claude will do.
Plugins and Connectors require a paid plan:
Connectors shine when combined with local file operations:
Scenario: You're preparing a quarterly report. The data lives in:
Without Connectors: You download exports from each service, copy-paste into your document, and hope nothing changes.
With Connectors:
"Create a quarterly report using the template in my local files. Pull sales figures from the Q4 Sales Google Sheet, include product updates from the Notion product database, summarize customer feedback from the #customers Slack channel, and compare everything to last quarter's performance."
Claude:
The advantage: Live data, no manual export/import, and one request does the work of accessing four different systems.
Document and Knowledge:
Communication:
Development:
Business Data:
Design:
Content:
New Connectors are added regularly. The Connectors Directory at claude.com/connectors shows all available integrations, with 50+ and growing.
Plugins can expose slash commands — shortcuts you type in the chat input (like /weekly-report or /standup-summary). When you invoke a slash command, Cowork can present a structured form — a fill-in UI with labeled fields — instead of requiring you to type a free-text prompt. You fill in the form fields, click submit, and the Plugin executes the workflow with your inputs.
This matters because structured forms reduce ambiguity. Instead of hoping Claude interprets your free-text prompt correctly, the form guides you to provide exactly the inputs the workflow needs.
You don't have to wait for Anthropic or partners to build a Plugin for your workflow. The Plugin Create tool lets you build custom Plugins directly inside Cowork:
Private GitHub repositories can also serve as Plugin sources (currently in beta). This means your team can maintain internal Plugins in version control, with updates deployed through standard git workflows.
For organizations deploying Plugins at scale:
These features mean Plugins scale from individual productivity to organization-wide automation.
A key architectural insight: Plugins are portable file systems you own. They aren't locked to the Cowork desktop interface. The same Plugin works across:
This portability means investing in Plugin creation isn't a bet on a single interface. The workflows you build today carry forward as Claude's platform evolves.
Plugins and Connectors are powerful but have constraints:
Rate Limits: External APIs have usage limits. Claude queries efficiently, but massive data pulls may hit limits.
Authentication: Some services require re-authentication periodically. You'll be prompted when this happens.
Read-only vs. Read-write: Not all Connectors support modification. Check capabilities before planning write workflows.
Service availability: If the external service is down, the Connector won't work.
Data freshness: Connectors fetch current data, not real-time streams. Changes after Claude queries won't be reflected.
Ideal for:
Less ideal for:
Plugins and Connectors require granting Claude access to your external accounts. Consider:
Principle of Least Privilege: Grant only the access needed. Read-only for reporting, specific folders rather than entire workspaces.
Regular Audits: Periodically review which Connectors are active and revoke access you no longer need.
Sensitive Data: Be cautious connecting accounts with highly sensitive information (HR data, financial systems).
Service Terms: Ensure using Plugins and Connectors complies with your organization's policies on external tool access.
Map Your Data Sources to Connectors:
"List the 5 services where I spend the most time accessing data for my work (e.g., Google Drive, Slack, Jira, Salesforce). For each one, check whether a Connector exists in the Anthropic directory (50+ available). Then identify which 2-3 would save the most time if Claude could query them directly in a single prompt — and describe one specific multi-source task I do today that would benefit."
What you're learning: Data source mapping — connecting your real workflow to the Connector ecosystem. This is the first step to replacing manual export/import with live multi-source queries.
Design a Plugin for Your Role:
"Based on what you know about my work, design a custom Plugin for my role. Include: (1) which Connectors it would bundle, (2) two slash commands with structured form fields for tasks I repeat weekly, (3) one custom skill for domain reasoning I apply often. Explain why this bundle is more valuable than using each component separately."
What you're learning: Plugin architecture thinking — understanding how bundling Connectors, skills, and slash commands into a single package creates compound value. This is the mental model that separates using Cowork from designing workflows in Cowork.