The Promise
Stop installing connectors that decay in the dock. Run the three that actually move your day — and know which stack to add next when the work demands it.
The One-Sentence Setup
Most operators install twelve MCP connectors and use three. The three they use are obvious in retrospect and invisible upfront — the Connector Stack names them before you waste a month on the other nine.
The Core Insight
The MCP Mental Model explains the protocol. The Connector Stack is the opinionated map of which servers earn their seat. Most operators treat the connector marketplace like an app store and end up with a dock full of half-authorized integrations they're afraid to revoke. The pattern that actually works: group connectors into four stacks tied to operator jobs-to-be-done, install only the stack(s) that match your week, and force every server to answer "what did I actually use this for the last three sessions?" If it can't, it gets pulled. Subtraction is the discipline.
The Mechanism
Four stacks. Pick by the work, not by the logo.
Stack A — The Inbox Stack (Capture + Light Act)
What: Gmail MCP, Google Calendar MCP, Slack MCP. The capture layer for any operator with an inbox and a meeting load.
How: Install Google's official Gmail MCP (read/search/label/draft — not send by default). Add Google's official Calendar MCP for find-times, read-events, draft-holds. Add Slack's official MCP for channel search, message read, and post-with-confirm. Default all three to read-heavy scopes; the moment you grant gmail.send or chat:write you've moved from Capture to Act and the Autonomy Ladder applies. The Inbox Stack is the minimum every operator runs.
Miss this and: your AI does the easy work (brainstorming) and skips the actual time sink (triage, scheduling, internal comms).
Stack B — The Build Stack (for operators who ship)
What: GitHub MCP, Vercel MCP, Supabase MCP. The wiring for anyone who runs a product, a site, or a side project with real code behind it.
How: Install GitHub's official MCP (105+ tools — enable only repos, issues, pull_requests unless you ship Actions). Add Vercel's official remote MCP (read-only by design — projects, deployments, logs, docs). Add Supabase's official MCP scoped to ?read_only=true on anything touching production. Stack B turns Claude Code from autocomplete into a colleague that can read your repo, see why the last deploy failed, and run the migration without tab-switching.
Miss this and: every code question becomes a copy-paste relay between three tabs.
Stack C — The Brain Stack (Remember + Reason)
What: Notion MCP, Filesystem MCP, Google Drive MCP. The second-brain layer for operators who maintain documentation, vaults, or knowledge bases.
How: Notion's official MCP (OAuth, full page/database/block read-write). Anthropic's reference Filesystem MCP scoped to your Obsidian vault and active project folders — nothing broader. Google's official Drive MCP for pulling Docs and Sheets into context. The Brain Stack is what makes Claude useful for synthesis work — weekly reviews, board prep, hand-off briefs. Without it, every reasoning session starts cold.
Miss this and: you keep pasting the same background into every conversation and wonder why memory features feel hollow.
Stack D — The Ops Stack (Act-heavy)
What: Stripe MCP, Twilio MCP, a task system MCP (Linear, Asana, or ClickUp — pick one), and Zapier MCP as fallback bridge.
How: Stripe's official MCP (mcp.stripe.com) handles customer lookup, refunds, and payment links with server-side scope enforcement — start read-only, add narrow write scopes only after the agent earns trust on a sample. Twilio's official MCP is still primarily a docs/search server as of May 2026; outbound SMS routes through a community SMS server or Zapier. For tasks: Linear is most mature (initiatives, milestones, issues), Asana V2 launched February 2026 over streamable HTTP, ClickUp is in public beta with no delete tools yet. Zapier MCP is the bridge of last resort — 9,000+ apps, billed two tasks per call.
Miss this and: your AI can think but can't ship. The work that pays the bills stays manual.
Step 5 — Run the Subtraction Audit
What: Every 30 days, force every installed connector to justify itself.
How: Open your Host's connector list. For each server, complete the sentence: "the last three times I used this, I used it for X." If you can't, revoke OAuth and uninstall. The Stack is a working tool, not a trophy shelf.
Miss this and: the connector list quietly becomes the junk drawer of your AI life.
The Pitfalls
The Pre-Pattern Install. Adding connectors before you know the workflow they serve. Fix: write the workflow first in plain English. If the workflow doesn't exist, the connector won't fix it.
The Toy Trap. Treating MCP servers as things to play with rather than tools that need an SOP. Fix: every installed server gets one paragraph in your operator vault — what it does, what it's authorized for, what query you run with it.
The Community Drift. Mixing official and community servers without checking maintenance. Community servers go stale fast — the original Anthropic reference servers for GitHub, Slack, Google Drive, and Postgres were archived in 2025 once vendors shipped official versions. Fix: prefer vendor-maintained. Check last-commit date on community alternatives.
The Over-Scoped OAuth. Many installs grant more than needed — full Gmail read when you only wanted draft creation, full Supabase write when read-only was enough. Fix: on every install, click into the scope screen and remove anything you can't justify with a sentence.
The "Every Tool Needs an MCP" Trap. Some workflows are faster as a one-line Zapier hook or a scheduled function. Fix: if you'll run it twice a year, don't wire it as a connector. MCP is for surfaces you touch weekly.
The Drill (this week)
Twenty minutes, before you close the tab.
- Open your Host's connector list. Screenshot it.
- For each installed server, complete the sentence: "the last three times I used this, I used it for X."
- Revoke OAuth and uninstall any server that can't answer.
- Pick the one stack above that matches your most expensive weekly work — Inbox, Build, Brain, or Ops.
- If you're missing one server from that stack, install only that one. Test it on a real query. Document the SOP in one paragraph.
You should finish with fewer connectors than you started with, not more. That's the drill working.
The Tools
| Connector | Source | Best For | One-Sentence Operator Use Case | Maturity (May 2026) |
|---|---|---|---|---|
| Gmail MCP | Official (Google) | Read, search, label, draft email | "Triage the inbox before my 9am block." | Stable |
| Google Calendar MCP | Official (Google) | Find times, read events, draft holds | "Find three 90-minute windows next week that don't break my no-meeting mornings." | Stable |
| Slack MCP | Official (Slack) | Channel search, post, canvas read/write | "Summarize what changed in #ops while I was offline." | Stable (GA 2026) |
| GitHub MCP | Official (GitHub) | Repos, PRs, issues, code search | "Open the PR that's blocking the deploy and tell me what changed." | Stable |
| Vercel MCP | Official (Vercel) | Project list, deployment logs, docs | "Why did the last production deploy fail?" | Beta — read-only by design |
| Supabase MCP | Official (Supabase) | Query DB, migrations, edge functions, types | "Count active subs in prod (read-only) and draft the migration to add a flag." | Stable — read-only mode for prod |
| Notion MCP | Official (Notion) | Page/database CRUD, blocks, search | "Pull this week's project pages into context for the review." | Stable |
| Filesystem MCP | Official (Anthropic reference) | Local file read/write, scoped to allowed dirs | "Update the Obsidian daily note with today's decisions." | Stable |
| Google Drive MCP | Official (Google) | Search, read, create Docs/Sheets | "Pull the Q2 board deck and the underlying model into this thread." | Stable (Workspace MCP GA 2026) |
| Stripe MCP | Official (Stripe) | Customers, charges, refunds, payment links | "Refund the duplicate charge on customer X with reason 'duplicate'." | Stable — scope-enforced server-side |
| Twilio MCP | Official (Twilio) | API docs/search; SMS via community or Zapier | "Show me the right endpoint for outbound SMS with delivery receipts." | Beta — docs/search only as of May 2026 |
| Linear MCP | Official (Linear) | Issues, projects, initiatives, milestones | "Create an issue from this Loom and link it to the Q3 initiative." | Stable |
| Asana MCP | Official (Asana V2) | Tasks, projects, workspace queries | "Roll up every overdue task assigned to me this week." | Stable (V2, Feb 2026) |
| ClickUp MCP | Official (ClickUp) | Tasks, lists, time tracking | "Create today's tasks from yesterday's voice memo." | Beta — no delete tools yet |
| Canva MCP | Official (Canva) | Generate, edit, export brand-aware designs | "Generate three social variants using our brand kit and export PNGs." | Stable (3.7M+ users) |
| Zapier MCP | Official (Zapier) | Bridge to 9,000+ apps without native MCP | "Send this draft to ConvertKit since there's no native MCP." | Stable — billed per task |
Cross-references
Backward: The Connector Stack is the wiring layer of The 4-Surface AI Stack — Capture, Reason, Act, Remember — and only makes sense once you've absorbed The MCP Mental Model. Don't install a stack before you understand the protocol.
Forward: The Brain Stack (C) is the entry point to The Operator Vault, where Notion and Obsidian live side by side. Stack D's write-scoped servers belong on The Autonomy Ladder — the framework that decides which actions an agent runs unattended.
One framework. One drill. One week at a time.
The Operator Stack is the architecture. Verala is the practice that runs it on your own communication delivery — voice, pitch, pause, presence. One foundation per week, until it's automatic.
Take the free 5-Foundation Voice Audit → · Book a 30-min intro call →