You've already used one connector: Figma, in Week 1. This page names the mechanism and extends it.
https://www.youtube.com/watch?v=kkBFmwkDzdo&list=PLmWCw1CzcFilebjK89WLb5cAvM8K0cLB3&index=8
Model Context Protocol — an open standard for giving the agent access to external services: design files, databases, issue trackers, docs, browsers. A connector is the agent's hands beyond the repository: instead of you copy-pasting data in, the agent reads (and sometimes writes) the service directly.
You can think about MCP like an API but for AI agents.
Same two paths as everything in this track:
claude mcp add --transport http <name> <server-url>, then /mcp in a session to authorize and see what's connected.
/mcp — the CLI's view of the same list you saw in Desktop's Connectors settings. Note the "27 tools" next to figma: a connector isn't an abstraction, it's a concrete set of capabilities the agent gains.
Connect what the project actually needs: Figma for design work, your database for data tasks, Notion/docs if specs live there. Every connector is also a grant of access: the agent can now act on that account. Three rules from Week 3 carry over:
The HackYourFuture curriculum is licensed under CC BY-NC-SA 4.0 *https://hackyourfuture.net/*

Built with ❤️ by the HackYourFuture community · Thank you, contributors
Found a mistake or have a suggestion? Let us know in the feedback form.