Chapter 18 · DESKTOP
Connectors, MCP and local extensions
A connector gives Claude access to another service's tools or data through MCP. Directory connectors, custom remote connections and local extensions have different setup, permissions and maintenance.
Video
Steps
- Open Settings > Connectors or the connection area in your interface. Select a needed service and inspect its Verified, Community or Custom status.
- Authenticate to the correct account and read the permissions. Read access differs from editing access, and OAuth consent is not consent to disclose information.
- Enable the connection for the relevant conversation and ask a limited question. Verify the source and result link. Do not assume it sees every organization document.
- For an unlisted connection, verify the remote MCP URL and authentication or the local desktop extension/MCPB package. Install only trusted components. MCP Apps may provide an interactive interface inside the chat.
Common pitfall: An expired or failed connection is not a reason to grant broader permissions without understanding the failure.
Hands-on exercise: Inspect a sample connector's read and action scopes. Do not authorize edits or sending for practice.
Filmed demo · Video is added in the media phase
Recap
Comprehension check
What should you check before connecting a service?
Recap
- Connectors expose tools and data
- Directory, remote and local setup differ
- MCP Apps add an interface