Skip to the lesson
Course overviewBeyond Chat.
Lesson not marked complete.
Course content0 / 5 complete
Your progress0 / 5

Progress stays in this browser.

Connecting Your Tools.

Connect web research, Google Workspace, and Notion, with attention to what the agent can access.

Recorded in . This course is not kept up to date.

Interfaces, features and setup steps for Claude Code, Cursor and other tools are likely to have changed. Focus on the concepts, and check the provider’s current documentation when following along.

Watch, pause, and follow along in your own workspace.

Lesson notes.

The tools connected in this section

  • Agent Mail — a dedicated email address for your AI agent to send from, separate from your personal inbox

  • Reducto — converts any PDF, image, Word doc, or presentation into clean markdown. Handles handwriting and low-quality scans. roughly 15,000 free credits, then pay-as-you-go (about $0.015/page)

  • FireCrawl — crawls and scrapes websites as markdown. Has a native plugin, making setup straightforward

  • Transcript API — transcribes YouTube videos. Can also search YouTube, browse channels, and track new uploads

  • Google Workspace CLI (GWS) — connects Claude to Gmail, Drive, Docs, Sheets, and Calendar. The most powerful integration in this section, and the most complex to set up

  • Notion — read and write to your Notion workspace via the native Notion plugin


The local-first workflow

Work on files locally on your laptop first. Iterate, refine, review. Then push to your tools (Gmail, Notion, Google Docs) when you're happy with the result. This keeps your context clean and your iterations fast.


MCP: the connection layer

MCPs are the bridge between Claude Code and your external tools — think of them as USB-C connectors for AI. They let Claude read and write data in the apps you already use.

  • Check for a plugin first — many tools (Notion, FireCrawl) already have one. Much easier to set up.

  • No plugin? Paste the tool's documentation into Claude and ask it to figure out the setup.

  • Scope matters: install at user level if you want a tool available across all projects. Project level if it's specific to one project.


API key safety rule

Never paste an API key directly into a chat. Store it in a secret.txt file in your project (excluded from any sharing) and point the skill to read from there.

Up nextCapstone: Plan a Trip to Japan1:00:30