Connectors (MCP)

Last verified: 14 April 2026 | Applies to: All plans (directory on Free; custom connectors on paid plans)

In 30 seconds

Connectors use the Model Context Protocol (MCP), an open standard, to link Claude to external tools and services. The Anthropic Connectors Directory at claude.com/connectors has 60+ reviewed integrations spanning communication, project management, design, engineering, finance, and healthcare. MCP Apps extend this by rendering interactive UI directly in chat. Free users can access directory connectors; paid plans can add custom MCP server URLs.

What it does

graph LR
    A[Your request] --> B[Claude]
    B -->|MCP| C[Connector]
    C -->|OAuth token| D[Slack / Asana / etc.]
    D --> C
    C --> B
    B --> E[Response with live data]

Claude can read from and write to your existing tools: Slack, Asana, Notion, Salesforce, and 60+ others. You authenticate once via OAuth (no passwords shared with Claude), and from that point Claude can pull data, push updates, and take actions in those tools directly from a conversation.

How it works in practice:

1. Browse the directory at claude.com/connectors or Settings → Connectors
2. Select an integration and authenticate via OAuth
3. Claude can now read from and write to that tool: with your approval for sensitive actions

The underlying technology is the Model Context Protocol (MCP): an open standard that defines how Claude talks to external tools. You don’t need to understand MCP to use connectors, but it matters because it means the ecosystem is growing fast. Any tool that implements the standard can connect to Claude.

MCP Apps go a step further. Instead of Claude describing what it did, you see interactive UI directly in the chat window: buttons, forms, cards, charts. Claude connects to Slack, Notion, Salesforce, and dozens more via MCP Apps. See the connector directory for the full list. MCP Apps is an open extension to the standard, so the list of interactive integrations grows as third parties build their own.

Custom connectors (paid plans): If a tool you use isn’t in the directory, you can add your own MCP server URL. This requires the tool to have an MCP-compatible server, which is increasingly common for modern SaaS products.

How to set it up

1. Go to Settings → Connectors (or visit claude.com/connectors)
2. Browse integrations by category
3. Click an integration → Authenticate with OAuth
4. Claude can now access that tool in conversations

For custom connectors (paid plans):

1. Settings → Connectors → Add custom connector
2. Enter the MCP server URL provided by your tool
3. Authenticate

How operators actually use it

Pull my open tasks from Asana, check which ones are overdue, and draft a status update for my team in Slack.

With Asana and Slack connectors enabled, Claude reads your task list, identifies overdue items, and composes a message: all in one conversation.

Show me the latest design from Figma for the landing page redesign.

With the Figma MCP App, Claude renders an interactive preview directly in chat. You can approve, comment, or request changes without leaving the conversation.

What to watch out for

• Not every tool has a connector yet. Check the directory before assuming connectivity. The list is growing but not exhaustive.
• Each connector requires separate authentication. You’ll need to OAuth into each tool individually.
• Permissions are scoped. Claude can only do what your OAuth permissions allow. If you connect with read-only access, Claude can’t write.
• Free plan limitations. Free users can access connectors from the Anthropic directory. Custom MCP server URLs require a paid plan.

Related

• Connecting Your Tools: step-by-step setup workflow
• Plugins: plugins bundle connectors with skills and commands
• Security & Privacy: how connector data is handled

---

Something wrong or outdated? Let us know →

Get weekly workflows. Subscribe to the newsletter.