How to Use MCP in Claude Code (No More Copy-Paste)

Here’s what an “AI-powered” day looks like for most people: open the chat. Copy the answer. Paste it into Gmail. Back to the chat. Copy again. Paste into a sheet. Over and over — until you realize you’ve become the messenger for your own AI.

The truth: your AI isn’t lazy. It just can’t reach past your folder. It can’t open your browser, can’t read your Gmail. So you’re the bridge — every single time.

That’s exactly what we fix in Module 3 of the free Claude Code course (Taglish), using MCP — the Model Context Protocol.

The analogy: phone apps

To get MCP in one glance: think of your Claude as a brand-new phone. It has a brain (Module 1) and memory (Module 2) — but no apps. Does it work? Sure. But its reach is limited.

MCP is how you install apps on it: a browser app — now it can browse. A Gmail app — now it can read email. A database app — now it talks to your data. And everything plugs into one standard port — the industry literally calls it the “USB-C of AI.”

What’s inside Module 3

Connectors — literal on-off switches in the claude.ai settings. Gmail, Drive, Calendar — flip them ON, sign in with Google directly (your password never passes through Claude), then back in Claude Code: they’re just there. Not a single command needed.
Any other tool — if it’s not on the switches, just tell Claude: “add the Playwright MCP” — it writes the config itself. Eight lines, and you’ll see in the video how readable they are. Then: the browser moves on its own. No hands.
GLOBAL vs LOCAL — if you’re a freelancer with multiple clients, this is the most important 30 seconds of the video: one folder per client + each client’s MCP in that folder’s own .mcp.json = Client B’s session can never reach Client A’s data. That’s how you protect your clients.
And the proof: one prompt — it browsed a website, read Gmail, and produced a report file. Not a single copy-paste.

3 rules before you connect anything

Official directory only (claude.ai/directory) or a vendor you know — anyone can build an MCP server; not all of them are your friends.
Read the approval prompt before you approve — don’t next-next through it. Don’t recognize the server? Don’t approve it.
OAuth ≠ giving Claude your password — you log in with Google itself. But API keys? They go in the .secrets/ folder (we built that in Module 2) — never in the chat, never on screen.

You connect once. After that, you’re not the bridge anymore — Claude is.

New to the course? Start with Module 2 (setup + memory), then follow the free Beginner Roadmap checklist — now updated with the MCP steps.

Less manual work, more lakwatsa. 🌴