MCP Plugins in Claude Cowork: What They Are and How They Work

What Is MCP?

MCP stands for Model Context Protocol. It is an open standard created by Anthropic that lets AI tools like Claude connect to external applications — Google Drive, Gmail, Slack, DocuSign, databases, and hundreds more.

Think of MCP as a universal adapter. Without it, Claude can only work with what you paste into the chat window. With MCP, Claude can reach out and interact with your tools directly — reading emails, pulling files from Drive, updating spreadsheets, sending messages.

Why MCP Matters for Non-Technical Users

Before MCP, connecting AI to your apps required custom code, API integrations, and developer involvement. MCP changes that. In Claude Cowork, you install a plugin, grant permission, and Claude can access that tool immediately. No coding required.

This is what turns Claude from a smart chatbot into an agentic AI assistant. Instead of copying data between apps yourself, you tell Claude what you want done and it moves between your tools to get it done.

How MCP Plugins Work in Cowork

Cowork's plugin system is built on MCP. When you install a plugin, you are giving Claude a secure connection to an external app. Claude can then read from and write to that app as part of multi-step tasks.

Example workflow: You say "Find the latest sales report in Google Drive, summarise the key metrics, and draft an email to the leadership team with the highlights." Claude uses the Google Drive plugin to find the file, reads and analyses it, then uses the Gmail plugin to draft the email. One instruction, three apps, zero manual work.

Installing Plugins

In Cowork, go to Settings and select Plugins. Browse available integrations, click Install, and follow the authentication flow (usually signing into the app). Once connected, Claude can access that service whenever you ask.

Available Plugins (March 2026)

The MCP ecosystem is growing rapidly. Key plugins available in Cowork include Google Drive, Gmail, Google Calendar, Slack, DocuSign, Notion, GitHub, and various database connectors. Anthropic and third-party developers continue to add new plugins regularly.

Security and Permissions

Every MCP connection requires your explicit permission. Claude cannot access any app until you install the plugin and authenticate. You control exactly which apps Claude can reach, and you can revoke access at any time.

Data flows through encrypted channels. Plugins follow the principle of least privilege — Claude only gets the access it needs for the specific task, not blanket control over your accounts.

MCP in Claude Code vs Cowork

Both Claude Code and Claude Cowork support MCP, but the implementation differs. In Cowork, plugins install through a visual interface — click, authenticate, done. In Code, you configure MCP servers through JSON configuration files in the terminal.

The underlying protocol is the same. A plugin built for one works with the other. The difference is purely in how you set it up.

The Bigger Picture

MCP is what makes agentic AI practical. Without it, AI assistants are isolated — they can think but they cannot act across your tools. With MCP, Claude becomes a hub that connects your entire workflow.

This is why understanding MCP matters even if you never touch the technical details. It is the infrastructure that lets you say "handle this" and have Claude actually handle it — across all the tools you already use.