Connecting Your Tools

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

In 30 seconds

Connectors let Claude read from and write to your existing tools — Slack, Asana, Notion, Google Drive, and 50+ more. Once connected, Claude can pull data, post updates, and work across tools in a single conversation. This workflow walks you through connecting your first tool and getting real value from it immediately.

Prerequisites

• A Claude account (Free plan gets directory connectors; paid plans can add custom MCP servers)
• At least one supported tool you want to connect (check the directory at claude.com/connectors)
• Admin or user-level access to authenticate the tool via OAuth

Step by step

Step 1: Browse available connectors

Go to Settings → Connectors in Claude Desktop, or visit claude.com/connectors.

Connectors are organised by category:

• Communication: Slack, Microsoft Teams, Gmail
• Project management: Asana, Linear, Jira, monday.com, Notion
• Design: Figma, Canva
• Data & analytics: Google Sheets, Hex, Amplitude
• File storage: Google Drive, Box, Dropbox
• CRM: Salesforce (upcoming), HubSpot
• Finance: various accounting integrations

Step 2: Connect your first tool

We recommend starting with the tool you use most frequently. For most operators, that’s Slack, Asana/Notion, or Google Drive.

1. Click the integration you want
2. Click Connect (or Add)
3. You’ll be redirected to the tool’s OAuth page — sign in and authorise Claude
4. Return to Claude — the connector is now active

What happens during OAuth: You’re signing in directly with your tool’s account. Claude receives a scoped access token — your password is never shared. You can revoke access at any time from Settings → Connectors.

Step 3: Test the connection

Start a chat and try a simple read operation:

Slack: “Show me unread messages from #general from today.”

Asana: “What are my open tasks in Asana? Sort by due date.”

Notion: “Find the page titled ‘Q1 Planning’ in Notion.”

Google Drive: “Find the most recent file in my ‘Weekly Reports’ folder.”

If it works, you’re connected. If not, check that your OAuth permissions include read access for the relevant workspace or project.

Step 4: Try a write operation

Once reads work, try a write:

Slack: “Post to #team-updates: ‘Q1 close is on track. Finance review scheduled for Friday.’”

Asana: “Create a new task in my ‘Website Redesign’ project: ‘Review homepage copy — due Friday.’”

Notion: “Add a new row to my ‘Meeting Notes’ database with today’s date and the title ‘Budget review with Marcus.’”

Claude will typically ask for confirmation before posting or creating.

Step 5: Work across tools

Once multiple tools are connected, Claude can work across them in a single conversation:

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

This is where connectors become genuinely powerful — replacing the context-switching between apps.

MCP Apps: Interactive integrations

Some connectors support MCP Apps — interactive UI elements that render directly in Claude’s chat window. Instead of Claude describing what it did, you see buttons, forms, and cards you can interact with.

Current MCP Apps partners: Slack, Asana, Figma, Canva, Box, Hex, monday.com, Notion, Amplitude, Clay. Salesforce is announced as upcoming.

With an MCP App connector, you might see an Asana task card in chat that you can mark complete without leaving the conversation.

Custom connectors (paid plans)

If a tool you use isn’t in the directory, you can add a custom MCP server URL:

1. Settings → Connectors → Add custom connector
2. Enter the MCP server URL (provided by the tool — check their docs for “MCP support” or “Claude integration”)
3. Authenticate

Custom connectors are increasingly common as SaaS products adopt the MCP standard. If your tool has an API and a developer community, check if someone has built an MCP server for it.

How operators actually use it

What operators say

“Every morning I ask Claude to check my email for anything urgent, review my Asana tasks for the day, and give me a prioritised briefing. It takes 30 seconds instead of 15 minutes of app-switching.”

What to watch out for

• Permissions are scoped. Claude can only do what your OAuth permissions allow. If you connected with read-only access, Claude can’t write. Re-authenticate with write permissions if needed.
• 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. There’s no “connect everything at once” option.
• Free plan limitations. Free users can access connectors from the Anthropic directory only. Custom MCP server URLs require a paid plan.
• Some tools have rate limits. If Claude is pulling large amounts of data, you may hit the tool’s API limits.

Related

• Connectors (MCP) — how the protocol works under the hood
• Workplace Memory — combine memory with connected tools for powerful workflows
• Browser Automation — for tools that don’t have connectors, Chrome can interact with the web UI
• Security & Privacy — how connector data is handled

---

Something wrong or outdated? Let us know →

Get weekly workflows — subscribe to the newsletter.