CHAPTERS
- 0:03 – 0:33
Why connectors make Claude a stronger productivity partner
The video explains that Claude becomes more capable when it can securely access your existing tools, knowledge, and files. Connectors enable this access (including optional action-taking permissions), leading to more informed, useful outputs.
- •Connectors link Claude to the tools you already use
- •More access to knowledge/files improves response quality
- •Connectors can optionally allow Claude to perform actions in connected apps
- •Goal: a smarter, more context-aware productivity workflow
- 0:33 – 0:49
What Claude can do with connected files and context
With file-handling and richer context, Claude can work across documents, spreadsheets, presentations, and reports while staying aligned with broader goals. This sets the expectation for end-to-end work, not just single responses.
- •Read and analyze uploaded documents
- •Work with spreadsheet data
- •Create presentations and generate reports
- •Maintain context and broader goals across tasks
- 0:49 – 1:04
Finding connectors in the Claude UI (Search and Tools)
The walkthrough shows where connectors live in the chat interface and what you might see when opening the menu. It highlights entry points for adding and managing connections.
- •Open the lower-left 'Search and Tools' button
- •View existing connectors if already set up
- •Use 'Add connections' to create new ones
- •Use 'Manage connectors' for ongoing administration
- 1:04 – 1:19
Adding a new connector from the directory
You’re guided to the connector directory, which includes both web tools and local desktop file connectors. The directory is organized by common work categories to help you pick the right integration.
- •Click 'Add Connectors' to open the directory
- •Connectors can support web tools and local desktop files
- •Categories include productivity, communication, development, business, automation, and desktop extensions
- •Choose a connector to begin setup
- 1:19 – 1:34
Secure setup via MCP (Model Context Protocol)
The setup flow is described as safe and largely automatic thanks to MCP handling configuration. Once configured, Claude can begin using that tool for context and, where allowed, actions.
- •Follow the connector-specific setup steps
- •Configuration is handled safely and automatically
- •Uses the Model Context Protocol (MCP)
- •After setup, Claude can use the connected tool’s context and capabilities
- 1:34 – 2:05
Verifying access and understanding permissions
The video recommends a simple test—ask Claude whether it has access to a tool—to confirm the connector works. It also shows how to inspect and toggle permissions for each connection.
- •Ask Claude directly if it has access to a specific tool
- •Click a connection to view its permissions
- •Toggle permissions on/off as needed
- •Browse permissions to spark ideas for workflows
- 2:05 – 2:35
Managing connectors and choosing between web search vs. connected sources
This section explains where to manage connectors later and how Claude decides whether to use connected sources when web search is enabled. It also notes you can explicitly instruct Claude which sources to use.
- •Use 'Manage Connectors' to add/remove and view details
- •When toggled on, Claude may use connectors and web search as appropriate
- •Claude considers which sources best answer your question
- •You can explicitly prompt Claude to use a particular source
- 2:35 – 3:05
Real workflow example: generating sprint release notes automatically
A practical example shows Claude pulling completed sprint tickets and producing release notes in a company template. The workflow demonstrates cross-tool retrieval (tickets + files) and producing polished, accurate output quickly.
- •Prompt: pull completed sprint tickets and create release notes from a standard template
- •Claude connects to Linear to identify completed sprint tickets
- •Pulls real feature descriptions, bug fixes, and improvements
- •Finds the release note template from your files automatically
- 3:05 – 3:37
Outcome: stakeholder-ready notes with accurate details and formatting
The output is positioned as non-generic and reflective of actual shipped work, formatted in company style. The emphasis is on speed plus fidelity—real technical details and professional presentation.
- •Release notes reflect real shipped work, not generic text
- •Includes accurate technical details
- •Matches proper formatting and company style
- •Ready to share with stakeholders quickly
- 3:37 – 3:43
Scaling connectors across your workflow + where to browse connectors
The closing expands the idea beyond release notes to broader automations that turn one artifact into another (meetings to tasks, updates to summaries, docs to designs). It ends with the directory link to explore available connectors.
- •Apply the same connector pattern across many workflows
- •Examples: meeting notes → tasks; project updates → exec summaries; documentation → visual designs
- •Connectors act as a bridge across tools you use daily
- •Browse and start at Claude.ai/directory
