Connectors and MCP: connect Claude to your tools
Connect Claude to business information sources and applications. Understand the difference between reading and taking action, and manage permissions carefully.
What Connectors do
Connectors give Claude access to information and features in other systems, such as documents, project software or business applications. Cloud Connectors link to online services; local desktop extensions can provide access to local apps or files. Manage them under Customize > Connectors. The directory groups Skills, Connectors and Plugins in one place, but each still has its own tab.
MCP as a connection standard
Many Connectors use the Model Context Protocol (MCP). This is an open standard that lets AI applications communicate with external tools and data sources in a structured way. You can use ready-made Connectors or connect your own and third-party MCP servers.
Reading is different from changing data
A Connector may only read data, but depending on its available tools it may also create, edit or delete information. Always check which actions are possible. Remote MCP servers must be reachable from Anthropic's cloud over the public internet using HTTPS port 443. A local MCP server uses your own network and works only in a local desktop session, not in a Cowork cloud session. Start with read-only access where possible and disable write actions when they are not needed.
Open and edit apps in Claude
Some Connectors can now open as interactive apps inside Claude. For example, you may see a full editor for a document or page alongside your conversation. You and Claude can work in the same screen; changes appear in the connected app and require the same kind of approval as other Connector actions. This only works with supported Connectors and is rolling out in the new Claude experience on web and desktop. Check whether your Connector supports this view and which actions are allowed.
Secure access and actions
Treat a Connector as a gateway into your business environment. Connect only trusted services, review requested permissions and assess approval requests carefully. A connected tool may contain incomplete, outdated or misleading information. Verify important details at the source.
Learning objectives
- Explain what Connectors and MCP do
- Recognize the difference between read and write permissions
- Set up a Connector with limited permissions
- Assess risks from external tools and data sources
- Explain what interactive Connectors add and how to review changes
Step by step
- 1Open Customize > Connectors and choose one trusted Connector
- 2Review which data and actions the Connector makes available
- 3Connect the account with the minimum permissions required
- 4Test a read-only request first and verify the source
- 5For a supported Connector, open its app view and test a small change on a copy
Pro tips
- ·Start with read-only access if that is sufficient
- ·Disable unused tools and review permissions regularly
- ·Ask Claude to identify the source and location behind important conclusions
- ·Do not assume every Connector has an embedded app view
Real-world examples
Find a report in a connected knowledge source
Task prompt:
“Find the most recent quarterly report in the connected project workspace. Provide its title, date and link. Summarize the five main points. Do not change anything in the source environment.”
Result: A summary with a verifiable reference to the original report.
Common mistakes
- ✕Giving a Connector full write and delete permissions when read access is enough
- ✕Connecting an unknown MCP server without checking its origin
- ✕Assuming a connected source is always current and complete
- ✕Forgetting that changes in an interactive Connector can change the real connected app
Practical exercise: Review one Connector
Choose a Connector you already use or one available in your account. Review its access before asking Claude to perform a task.
Task prompt
Help me assess this Connector safely. List the data Claude can read, the actions it can take, the permissions requested and the risks. Recommend the minimum access needed for this task: [describe the task].
- The Connector comes from a trusted source
- The required permissions are limited
- You tested a read-only request first
Knowledge check
What is a sensible first step when connecting a Connector?


