Connectors provide Claude access to external tools, data sources, and services using the Model Context Protocol.
They give Claude access to external tools, data sources, and services.
The Model Context Protocol (MCP) is an open standard created by Anthropic.
A product manager can query Amplitude, create a Canva deck, and drop the link into Asana.
MCP defines communication between Claude and external services, allowing two main functions.
This allows Claude to perform actions like reading files, sending emails, or querying databases.
An MCP server can render interactive elements like charts, maps, or forms in the conversation.
Connectors are categorized based on their origin and functionality.
Anthropic provides ready-to-use connectors for common services requiring only login.
Services supported immediately are Google Drive, Gmail, Google Calendar, GitHub, Slack, and Microsoft 365.
Third-party developers can host servers in the cloud for Claude to connect to over HTTPS.
These are MCP servers that display interactive elements like booking flows or charts within the chat.
These packages bundle an MCP server with dependencies for enterprise or local use.
A local MCP server can be distributed via a Plugin using .mcp.json and submitted to the directory.
The availability of features varies across different Claude platforms.
The table details which features are available on each Claude platform.
| Platform | Remote MCP | MCP Apps | Local Extensions |
|---|---|---|---|
| Claude.ai (web) | Yes | Yes | No |
| Claude Desktop | Yes | Yes | Yes |
| Claude Mobile | Yes | Beta | No |
| Claude Code | Yes | No | Via plugins |
| Claude Cowork | Yes | Yes | Via plugins |
Claude dynamically surfaces the correct connector based on user activity.
Claude surfaces the appropriate connector automatically based on the user's request.
If multiple connectors apply, Claude displays all of them for the user to select from.
Strict protocols govern how user data is handled when using Connectors.
Data from connected apps is explicitly not used to train Claude's models.
A connected app cannot view the user's other conversations with Claude.
Claude confirms with the user before booking or purchasing on their behalf.
Users can build connectors for internal tools or services they wish Claude to access.
The server must be a standard HTTPS service implementing the MCP protocol and exposing tools.
Each exposed tool needs a name, description, and an input schema.
Configuration files allow connecting either a local or remote MCP server.
The claude_desktop_config.json file specifies the command and arguments for a local server.
For remote servers, the configuration requires only the server's URL.
The server can return HTML-based components for inline rendering within the conversation.
Submissions are reviewed by Anthropic for inclusion in the Connectors Directory.
Connectors provide Claude access to external tools, data sources, and services using the Model Context Protocol.
They give Claude access to external tools, data sources, and services.
The Model Context Protocol (MCP) is an open standard created by Anthropic.
A product manager can query Amplitude, create a Canva deck, and drop the link into Asana.
MCP defines communication between Claude and external services, allowing two main functions.
This allows Claude to perform actions like reading files, sending emails, or querying databases.
An MCP server can render interactive elements like charts, maps, or forms in the conversation.
Connectors are categorized based on their origin and functionality.
Anthropic provides ready-to-use connectors for common services requiring only login.
Services supported immediately are Google Drive, Gmail, Google Calendar, GitHub, Slack, and Microsoft 365.
Third-party developers can host servers in the cloud for Claude to connect to over HTTPS.
These are MCP servers that display interactive elements like booking flows or charts within the chat.
These packages bundle an MCP server with dependencies for enterprise or local use.
A local MCP server can be distributed via a Plugin using .mcp.json and submitted to the directory.
The availability of features varies across different Claude platforms.
The table details which features are available on each Claude platform.
| Platform | Remote MCP | MCP Apps | Local Extensions |
|---|---|---|---|
| Claude.ai (web) | Yes | Yes | No |
| Claude Desktop | Yes | Yes | Yes |
| Claude Mobile | Yes | Beta | No |
| Claude Code | Yes | No | Via plugins |
| Claude Cowork | Yes | Yes | Via plugins |
Claude dynamically surfaces the correct connector based on user activity.
Claude surfaces the appropriate connector automatically based on the user's request.
If multiple connectors apply, Claude displays all of them for the user to select from.
Strict protocols govern how user data is handled when using Connectors.
Data from connected apps is explicitly not used to train Claude's models.
A connected app cannot view the user's other conversations with Claude.
Claude confirms with the user before booking or purchasing on their behalf.
Users can build connectors for internal tools or services they wish Claude to access.
The server must be a standard HTTPS service implementing the MCP protocol and exposing tools.
Each exposed tool needs a name, description, and an input schema.
Configuration files allow connecting either a local or remote MCP server.
The claude_desktop_config.json file specifies the command and arguments for a local server.
For remote servers, the configuration requires only the server's URL.
The server can return HTML-based components for inline rendering within the conversation.
Submissions are reviewed by Anthropic for inclusion in the Connectors Directory.