Connectors allow Claude to integrate with external tools like Google Drive, Gmail, and GitHub.

Made with Rinto — analyse your own content free

What Connectors are and function

Connectors provide Claude access to external tools, data sources, and services using the Model Context Protocol.

How the integration works via MCP

MCP defines communication between Claude and external services, allowing two main functions.

Types of available Connectors

Connectors are categorized based on their origin and functionality.

Platform compatibility matrix shown

The availability of features varies across different Claude platforms.

Feature availability across 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

Discovery and usage of Connectors

Claude dynamically surfaces the correct connector based on user activity.

Privacy and data boundary assurances

Strict protocols govern how user data is handled when using Connectors.

Guide to building a custom connector

Users can build connectors for internal tools or services they wish Claude to access.

▸ 7 Expand

APEX

Claude Connectors extend Claude's capabilities

Connectors allow Claude to integrate with external tools like Google Drive, Gmail, and GitHub.

Made with Rinto — analyse your own content free

▸ 3 Expand

SECT

What Connectors are and function

Connectors provide Claude access to external tools, data sources, and services using the Model Context Protocol.

FACT

Connectors extend Claude's capabilities

They give Claude access to external tools, data sources, and services.

FACT

MCP is the powering protocol

The Model Context Protocol (MCP) is an open standard created by Anthropic.

FACT

Workflow example using connected apps

A product manager can query Amplitude, create a Canva deck, and drop the link into Asana.

▸ 2 Expand

SECT

How the integration works via MCP

MCP defines communication between Claude and external services, allowing two main functions.

FACT

Connector function one: Provide tools and data

This allows Claude to perform actions like reading files, sending emails, or querying databases.

FACT

Connector function two: Surface UI components

An MCP server can render interactive elements like charts, maps, or forms in the conversation.

▸ 5 Expand

SECT

Types of available Connectors

Connectors are categorized based on their origin and functionality.

▸ 1 Expand

FACT

Prebuilt First-Party Integrations exist

Anthropic provides ready-to-use connectors for common services requiring only login.

FACT

First-party services include Google Drive

Services supported immediately are Google Drive, Gmail, Google Calendar, GitHub, Slack, and Microsoft 365.

FACT

Remote MCP Servers are available

Third-party developers can host servers in the cloud for Claude to connect to over HTTPS.

FACT

MCP Apps render UI in chat thread

These are MCP servers that display interactive elements like booking flows or charts within the chat.

FACT

MCP Bundles are desktop extensions

These packages bundle an MCP server with dependencies for enterprise or local use.

FACT

Local MCP uses Plugins for distribution

A local MCP server can be distributed via a Plugin using .mcp.json and submitted to the directory.

▸ 1 Expand

SECT

Platform compatibility matrix shown

The availability of features varies across different Claude platforms.

CMPR

Feature availability across 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

▸ 2 Expand

SECT

Discovery and usage of Connectors

Claude dynamically surfaces the correct connector based on user activity.

FACT

Dynamic surfacing of connectors occurs

Claude surfaces the appropriate connector automatically based on the user's request.

FACT

Multiple options are presented to user

If multiple connectors apply, Claude displays all of them for the user to select from.

▸ 3 Expand

SECT

Privacy and data boundary assurances

Strict protocols govern how user data is handled when using Connectors.

FACT

User data is not used for model training

Data from connected apps is explicitly not used to train Claude's models.

FACT

Conversation isolation is maintained

A connected app cannot view the user's other conversations with Claude.

FACT

Confirmation required for actions taken

Claude confirms with the user before booking or purchasing on their behalf.

▸ 4 Expand

SECT

Guide to building a custom connector

Users can build connectors for internal tools or services they wish Claude to access.

▸ 1 Expand

FACT

Step 1: Build an MCP Server

The server must be a standard HTTPS service implementing the MCP protocol and exposing tools.

FACT

Tool definition requires schema and description

Each exposed tool needs a name, description, and an input schema.

▸ 2 Expand

FACT

Step 2: Connect in Claude Desktop

Configuration files allow connecting either a local or remote MCP server.

FACT

Local connection uses command arguments

The claude_desktop_config.json file specifies the command and arguments for a local server.

FACT

Remote connection uses a URL endpoint

For remote servers, the configuration requires only the server's URL.

FACT

Step 3 Optional: Add UI with MCP Apps

The server can return HTML-based components for inline rendering within the conversation.

FACT

Step 4 Optional: Submit to Directory

Submissions are reviewed by Anthropic for inclusion in the Connectors Directory.