MCP · CONNECTIONNeill's Vibe · Field Notes

“Check my Notion.” It can't. It's in an empty room.

A chat model has no hands. MCP is the standard plug that gives it tools.

✓ what worked

01 · the learning

What I set out to add

I kept asking the AI to do things it had no way to reach — read my Notion, touch my files, hit a database. It's not stubborn; it simply has no tools until you hand it some. The concept that fixed my mental model: MCP — a standard plug. One protocol, and any compliant tool snaps in.

02 · the test

The thing I actually tried

I tested wiring an MCP server through a single config file — a filesystem server so it could read my project, and a Notion server behind an environment secret so it could actually reach my workspace.

→ .mcp.json→ WHAT-TO-PLUG-IN-FIRST.md

03 · the frustrations

Where it bit

"Check my Notion." It can't. It was standing in an empty room, asked to fetch from a building it couldn't see.

04 · the verdict

What worked, what didn't

✓ worked

The standard plug. One config, real tools, and secrets passed by reference instead of pasted in. Read-only by default kept the first connection safe.

✗ didn't

Assuming a chat model could already touch my data. Until you plug something in, it's guessing about a room it can't enter.

the durable rule

The model isn't dumb, it's unplugged. MCP is the socket; you decide what gets wired in.

🔒 this became a classT4·F34 — An MCP Server members