MCP: structured tools for AI
Model Context Protocol is the USB-C of AI tooling · learn the shape before you wire anything.
::TL;DR · the whole lesson in three lines
- MOVEModel Context Protocol is the USB-C of AI tooling · learn the shape before you wire anything.
- DRILLYou will list every MCP server currently connected to your AI client, audit what each one can actually do, and remove anything you cannot justify.
- WINYou can name every MCP server you have installed and what it does.
::concept · what's actually happening
MCP (Model Context Protocol) is an open standard that lets an AI client talk to a tool server in a predictable, typed way. The model does not need to know your tool was written in Python or TypeScript · it sees a list of tools, each with a name, a description, and a JSON Schema for its inputs.
read full concept · 4 more paragraphs →collapse concept ↑
Before MCP, every AI integration was a snowflake · custom function-call definitions baked into each app, no portability, no reuse. With MCP, the same Postgres server, Gmail server, or filesystem server can plug into Claude Code, Cursor, Codex, and any other MCP-aware client.
The contract is small: tools (the model can call them), resources (the model can read them), prompts (reusable templates the user can invoke). That is mostly it. The rest is implementation detail and transport (stdio for local, HTTP for remote).
MCP does not make a tool good · it just makes a tool reachable. A badly described tool will be ignored or misused by the model regardless of how cleanly it is wrapped. Tool descriptions are still prompt engineering.
Security teaches a hard lesson here: every MCP server you install is code running on your machine with your credentials. Treat them like browser extensions · read the source, prefer official servers, and grant the narrowest scope possible.
::drill · do the thing
You will list every MCP server currently connected to your AI client, audit what each one can actually do, and remove anything you cannot justify.
::L31 drill · copy-paste into any AI chat
I am auditing my installed MCP servers. For each server I list below, tell me: 1) what tools/resources it exposes (group them: read-only, write, destructive), 2) what credentials or scopes it requires, 3) what the worst-case blast radius is if the model called the wrong tool, and 4) whether the server is from a verified publisher or a community repo. My installed servers: [PASTE LIST OF SERVER NAMES]. After the per-server audit, give me a one-line keep/review/remove recommendation for each, based purely on whether the value I get justifies the surface area.
::steps
- 01Open your MCP client config (Claude Desktop config.json, Cursor settings, etc.).
- 02List every server name into the prompt above.
- 03For any 'remove' verdicts, actually remove them today · don't defer.
- 04For any 'review' verdicts, read the server's source repo before next session.
- 05Note one server you wish existed but doesn't · that's your next build idea.
::outcome · what should be true
- You can name every MCP server you have installed and what it does.
- You have removed at least one server you could not justify.
- You can explain MCP to a peer in two sentences without using the word 'protocol' twice.
- You have a written list of credentials each server holds.
::trap · the most common failure
Operators install MCP servers like browser extensions, then forget what they granted. Six months later there's a filesystem server with full read/write access to ~/, a GitHub server with admin scope, and three abandoned community servers nobody audits. The blast radius is real.
::end of the curriculum
You're at Pilot level. There's no Level 6.
The next move is doing the work, not another lesson. If you want operator-grade infrastructure, that's /orangebox. If you want the lab's working journal, /founders-view. If you want to collaborate on the curriculum itself, the source is public on GitHub.
::other lessons at Operator level
Local AI · Ollama — privacy, offline, and the limit of free
At Operator level you need an honest opinion about local-only AI. Even if you don't use it daily, you should have run it once.
Model routing — switching between Claude, GPT, Gemini mid-task
Operators don't pick one AI. They route each task to the model that does it best. Knowing the strengths is the skill.
MCP servers — the plug socket that turned AI into a real tool
Model Context Protocol is the standard plug. Knowing what plugs in changes what your AI can actually touch — your files, your inbox, your calendar, your repos.
Agent mode — when AI takes action, not just answers
The frontier of useful AI is agents that DO things — browse, click, file, send. The actual skill is the safety pattern, not the magic.
Computer use — when AI takes the mouse and keyboard
Claude in Chrome, ChatGPT Atlas, computer-use beta — the frontier is AI that drives your browser like a human. Knowing the safety pattern is the actual skill.
What AI cannot replace — taste, judgment, relationships
The operators winning in 2026 are the ones who learned what AI is for and what is theirs. Knowing the line is more valuable than any prompt.
Agents 101: model plus tools plus loop
An agent is a model with tools running in a loop until done · know when you need one and when you don't.
Skill primers: teach a session your context in 30 seconds
A skill is a reusable file that primes a fresh AI session with your project, voice, and rules · stop re-explaining yourself.
Local models with Ollama
Run Llama, Qwen, or Mistral on your own laptop · no API, no logs, no monthly bill for the work that should stay home.
Vision models: when to use them
Vision lets the model see images · powerful for screenshots and diagrams · weak for precise spatial work · know the line.
Audio and Whisper transcription
Whisper turns audio into text · meetings, voice memos, interviews · the AI-era replacement for note-taking.
RAG vs long context: when to retrieve, when to dump
RAG fetches the right slice of your data at query time · long context stuffs everything in · know which problem you actually have.
Embeddings: meaning as numbers
An embedding is a list of numbers that captures the meaning of text · learn the shape and you unlock semantic search, deduplication, and clustering.
Fine-tuning vs prompt engineering
For individuals, fine-tuning is almost never worth it · know exactly when it actually is.
AI safety in personal use
PII, NDAs, financial data, and other people's secrets · know the rules of what you do not paste.
Multimodal prompting: combining text, image, audio
The strongest prompts use the medium that fits the question · sometimes you describe, sometimes you show, sometimes you do both.
Chain-of-thought: making the model show its work
Asking the model to reason step-by-step before answering raises accuracy on hard problems · know when it earns its cost.
Tool use and structured output
Function calling makes the model return JSON your code can use · know the contract before you build on it.
Cost optimization: tokens, caching, model selection
AI is metered · the operators who stay profitable measure what they spend and choose the model that fits the task.
::part of the AtomEons /learn curriculum · 45 lessons · 5 levels · cc-by 4.0