Play the clip from YouTube. Do not put a still from the film in this deck: the deck is CC BY-SA and the film is not.
Say what the clip is: the gearing-up scene from the film Commando (1985).
Recap of lecture 02 (model + harness + tools). Today: what the gear is, and how to add more.
Exact wording in the Claude API docs (Tool use): "Claude determines when to call a tool based on the user's request and the tool's description."
Step 1 in detail: for connector tools the model first gets only the names, and looks up the rest (what it does, what to fill in) when it needs one. So a connector you do not use costs almost nothing.
ffmpeg and ARES come back later today. Just say "you will meet these later".
CLI = command-line interface. The screen is a connector that comes with Claude, off until you turn it on (computer use); it is covered near the end.
Cut if short on time.
PowerShell on Windows; Bash on a Mac, and on Windows with Git Bash. About 45 built-in tools in total. Internal names: Edit shows as Update, Glob and Grep as Search, WebFetch as Fetch, WebSearch as Web Search. On a Mac, Claude usually searches through Bash instead of the Search tool.
Claude Code docs: "To add custom tools, connect an MCP server."
Since December 2025 MCP belongs to the Agentic AI Foundation, a fund under the Linux Foundation (co-founded by Anthropic, Block and OpenAI).
Other local servers exist too, for example for FreeCAD.
Same name, different maker: the official "Affinity MCP server" is for Affinity the CRM, not for the Affinity design app by Canva, which has only community servers.
Menu paths (Sep 2026): claude.ai, Customize, Connectors. Custom connector by web address: Customize, Connectors, +, Add custom connector (Free plan: one only; Team and Enterprise: only Owners add them). In Claude Code: `claude mcp add`, and claude.ai connectors appear by themselves with a claude.ai login (not with an API key). Desktop extensions (local servers) work in the desktop app, Cowork and Claude Code, not in the web chat.
Numbers: a warning above 10,000 tokens; above 25,000 (the default limit) the answer is saved to a file and the model gets the path.
Anthropic engineering blog, Nov 2025: "Every intermediate result must pass through the model."
Cut if short on time: say it on the pros and cons slide.
One line for the window vs command line idea: HandBrake needs clicks through its settings; `ffmpeg -i talk.mp4 -vn talk.mp3` is one line, and a short loop does 200 files. HandBrake and VLC use FFmpeg's engine inside.
Cut if short on time.
Test on the teaching laptop first: after winget installs a program, a Claude Code session that was already running may not find it ("not recognized"), because the new PATH is not loaded yet. Fix: restart Claude Code, or install before the lecture.
Fallback: skip the download, use a video already in the folder.
Claude usually uses Fetch, or writes a small script. Either is fine: both use the API.
Cut if short on time: it repeats "One service, several ways in" with the new words.
The file for gws is client_secret.json. The wiki guide Connect Google Workspace has the steps.
Docs wording: "Computer use is the broadest and slowest, so Claude tries the most precise tool first." In Claude Code, computer use is itself a built-in MCP server, off by default.
Sources: Claude help center (connectors, Cowork architecture, code execution, computer use) and Claude Code docs, checked 29 Sep 2026.
More detail if asked: custom connectors by web address work in all three. Local MCP servers: in Chat only in the desktop app, not the web. Work runs code in an isolated sandbox, in Anthropic's cloud by default (some company plans run it on your own machine), with a list of allowed websites. It reaches your connected folders through the desktop app. APIs in Chat: the key would have to go into the chat. Team plans: an Owner switches connectors on, only Owners add custom connectors, and there is no computer use in any product.
The connector can send a plain email. It cannot attach a file from your folder. That is the joke.
Wiki guide: Connect Google Workspace (gws 0.22.5, March 2026). Sending a file through the connector would mean the model types the whole file out inside the call: not practical. Docs and Sheets are reached only as files through the Drive connector. Batch relabel takes up to 1,000 emails per call.
Cut if short on time, or if the invoice demo has not run on the teaching laptop yet.
Replace these lines with a real screenshot once the invoice demo has run on the teaching laptop.
Test on the teaching laptop first: gws takes JSON in --params, and quoting JSON through the PowerShell tool (especially Windows PowerShell 5.1) often goes wrong. Through Bash (Git Bash) it works as shown. --page-all stops after 10 pages unless --page-limit is raised.
Why two MCP servers: the claude.ai connector showed no newsletter (marketing email) buttons, so HubSpot's own server was added for them. HubSpot documents marketing emails for both, and says "Tool availability varies by HubSpot subscription, user permissions, and account configuration". Permissions are chosen when you connect; new ones need a reconnect. Before the lecture: reconnect the claude.ai connector, allow marketing, and compare /mcp. HubSpot's own list for its server has 32 tools and is not called complete.
Note: the claude.ai HubSpot connector is made by HubSpot (mcp.hubspot.com/anthropic, July 2025), not by Anthropic. The custom server at mcp.hubspot.com is not "almost everything": 22 tools are the same (28 and 29 in Claude Code, 29 Sep 2026), it adds marketing emails, custom properties and pipelines and the inbox, and it lacks blog posts, website pages and saved reports. Both: no delete, 10 records per change, every answer through the context. It needs an MCP auth app in HubSpot; on Team plans only an Owner can add a custom connector.
Keys: from 26 Oct 2026 existing accounts cannot create new private apps (new accounts from 28 Sep 2026). Old private apps keep working. New keys are service keys.
Exact wording (HubSpot developer changelog, 23 Jun 2026): the CLI is "designed for AI agents to consume and use"; the MCP server suits "conversational, human-in-the-loop workflows"; the Agent CLI is for "repetitive, bulk, and scheduled work".
Not the old HubSpot CLI (`hs`): that one is for developers and does not manage CRM data.
Test on the teaching laptop first: the Windows install is one PowerShell line from HubSpot's docs, then open a new terminal. The official "export everything" helper is a bash script that needs jq (and adding the skills needs Node.js). Without Git Bash and jq, Claude has to write its own loop. Run a full contacts export once before the lecture.
Internal data only on the live screen. Nothing from the CRM goes into the slides.
Step 3 only if a full export with the HubSpot CLI has run once on the teaching laptop.