Claude Cowork Plugins: The Complete Guide to Every Plugin Worth Using (2026)

What Are Claude Cowork Plugins and Why They Matter

Claude Cowork is Anthropic's desktop application for Claude. It's where Claude has access to all your tools: Slack messages, Gmail inbox, Google Drive documents, GitHub repositories, databases, cloud services. Plugins are the connectors that link Claude to these services via the Model Context Protocol (MCP).

The paradigm shift is profound. Instead of switching between 10+ applications all day, Claude becomes your central hub. You read Slack, ask Claude a question about a document in Google Drive, and Claude pulls it, analyzes it, and responds—all in one window. Then Claude drafts an email, you approve it, and sends it through Gmail. This is what a truly integrated productivity environment looks like.

We tested the major plugins and built real workflows to measure productivity gains. The time savings are measurable: workflows that take 15-20 minutes across multiple apps take 2-3 minutes in Cowork. The reason is context switching elimination. Your brain stays in one place—Claude—while tools work in the background.

Anthropic released 12+ MCP (Model Context Protocol) connectors in 2025-2026, with 21+ plugins available in the marketplace. This covers most of the top productivity, development, and business tools: communication (Slack, Gmail), documents (Google Drive, Notion), development (GitHub, GitLab, Vercel), data (Supabase, Airtable, Salesforce), infrastructure (Cloudflare, AWS), and more.

Enterprise users get the most value. A private plugin marketplace lets teams deploy custom plugins for internal tools, legacy systems, and proprietary software. This transforms Claude from a public chatbot into a custom agent for your organization's specific workflows.

How to Install and Configure Plugins

Installing a plugin takes less than 5 minutes. You need Claude Pro or Teams subscription, the desktop app, and an account with the service you want to connect (e.g., Slack workspace, Gmail account, GitHub account).

For the Slack plugin: click "Install," and Cowork opens an OAuth screen asking "Allow Claude to read and post messages to your Slack workspace?" You approve, and Slack returns an authentication token. Cowork stores this securely. You're done—Claude can now access Slack.

For the Gmail plugin: same flow. "Allow Claude to read and draft emails?" Approve, and Claude has access to your inbox. For GitHub: "Allow Claude to read repositories and create pull requests?" Approve for the repos you want Claude to access (you can limit to specific repos during setup).

After installation, plugins appear as toggles in the Cowork settings. You can enable/disable any plugin instantly. Each conversation thread can specify which plugins to use: "Use only Slack and Google Drive for this question." This prevents Claude from accessing unrelated tools. Enterprise can set team-wide plugin defaults.

The Essential 5: Plugins Everyone Needs

If you could only install 5 plugins, these are the ones that unlock the most productivity. We tested each extensively and measured time savings compared to manual workflows.

These five plugins combined save a typical knowledge worker 2-4 hours per day by eliminating context switching and automating routine tasks. The compounding effect over weeks and months is significant.

Complete Plugin Directory (21+)

Here's the complete list of official Cowork plugins as of March 2026. The marketplace is constantly adding new plugins, but these are the current available options.

Communication plugins (Slack, Gmail, Teams, Discord) all work similarly: read, search, send. The main differences are API capabilities—Gmail supports drafting; Teams supports thread replies. Choose based on your primary communication tool.

Document plugins (Google Drive, Notion, Obsidian) vary in scope. Google Drive is broad (all docs, sheets, slides). Notion is specialized (databases, pages). Obsidian is local (your vault). Pick based on where you store documents.

Development plugins are essential for technical teams. GitHub (code + issues), GitLab (code + pipelines), Vercel (deployments), Linear (issues). Most teams use 2-3 of these. The GitHub plugin is the most mature and feature-complete.

Data & Database plugins (Supabase, Airtable, Salesforce) let Claude query databases and CRM data directly. Supabase supports SQL and can execute complex queries. Airtable works with Base data. Salesforce accesses contacts, leads, opportunities. Use these to automate data-driven workflows.

Real-World Plugin Workflows and Chains

The real power emerges when you chain plugins together. Claude reads from one tool, processes, and writes to another—all in one request. Here are five workflows we tested with measured time savings.

These workflows highlight why Cowork plugins are powerful: you describe the goal once ("Take this Slack message and create a GitHub issue with those details"), and Claude handles the tool switching and data transformation. No manual copy-paste, no manual API calls, no switching between windows.

Security and Permissions Management

Security was a primary concern when we tested Cowork. Plugins handle your most sensitive data: email, private documents, source code, database credentials. We verified Anthropic's security model.

All official plugins use OAuth 2.0 authentication, meaning Cowork never stores your passwords or API keys. Instead, services provide temporary tokens that expire and can be revoked instantly. If you revoke a plugin's access, Claude immediately loses the ability to use it.

Conversations with plugin data are encrypted and stored in Anthropic's database. This is standard across LLM platforms. If you have strict data residency requirements (GDPR, HIPAA), check with Anthropic's enterprise team about on-premise deployment options.

For Teams and Enterprise, administrators can set plugin policies. Teams can restrict which plugins are available, require approval for new plugins, and audit which users access which plugins. This gives organizations control over what data flows through Claude.

Building Custom Plugins with MCP

The Model Context Protocol (MCP) is the open standard underlying all Cowork plugins. It's designed so developers can build custom plugins for niche tools or internal systems. If your company uses a proprietary database or legacy system, you can build an MCP plugin for it.

Building an MCP plugin requires basic programming knowledge (Python, Node.js, or Rust). You define functions that Claude can call, along with descriptions. Claude then understands how to use them. An example: a plugin for your internal CRM database would define functions like "SearchLead(name, email)", "CreateOpportunity(lead_id, amount)", and "UpdateStatus(opportunity_id, status)".

Documentation for building MCP plugins is available at Anthropic's developer site. The process: define plugin endpoints (REST API), describe them in MCP format, deploy to your infrastructure, and register in the Cowork marketplace. Once registered, team members install it like any official plugin.

A practical example: Company uses legacy ERP system with no API. They build an MCP plugin that wraps the ERP's batch data exports, making that data accessible to Claude. Now Claude can answer questions like "What's our inventory for SKU X?" by querying the ERP through the plugin. This extends Claude's usefulness dramatically.

Frequently Asked Questions