Control which AI agents can reach which MCP servers from one switchboard
MCP Switchboard connects all your MCP servers and APIs in one place, then controls exactly which AI agents can access what. The author runs it every day.
Source
@cmercier on X · 2026-10-13
Written in our own words. Credit to the original author. Link checked 2026-10-16.
What they did
MCP Switchboard connects all your MCP servers and APIs in one place, then controls exactly which AI agents can access what. The author runs it every day.
Result (as claimed)
Says it became one of the most useful things they run.
Tools they used
The source does not name specific tools.
Cost: Pricing depends on the tools you pick; check each official pricing page.
Set it up
Pick a contained repo or task
Start on a branch or side project where mistakes are cheap.
Install and configure
Set up the tools you choose. Read what it can run on your machine and limit permissions where possible.
Run it on a real task
Give it a well-scoped issue and let it work. Review the diff like any pull request.
Add guardrails
Keep tests and CI in the loop, and never let an agent push to main or touch production secrets unattended.
Copy the full setup prompt
Paste into your agent and it will walk you through the setup, asking before anything that sends, posts or spends.
You are helping me set up this AI use case end to end in Claude Code. Goal: Control which AI agents can reach which MCP servers from one switchboard What the original author did: MCP Switchboard connects all your MCP servers and APIs in one place, then controls exactly which AI agents can access what. The author runs it every day. Reported result (as claimed by the author): Says it became one of the most useful things they run. Source: https://x.com/cmercier/status/2109815620510327045 Tools they used: not named in the source Category: Dev & ops Please: 1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like). 2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure. 3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data. 4. Finish with a checklist to run it again next time.
You are helping me set up this AI use case end to end in Codex. Goal: Control which AI agents can reach which MCP servers from one switchboard What the original author did: MCP Switchboard connects all your MCP servers and APIs in one place, then controls exactly which AI agents can access what. The author runs it every day. Reported result (as claimed by the author): Says it became one of the most useful things they run. Source: https://x.com/cmercier/status/2109815620510327045 Tools they used: not named in the source Category: Dev & ops Please: 1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like). 2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure. 3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data. 4. Finish with a checklist to run it again next time.
You are helping me set up this AI use case end to end in Grok Bot. Goal: Control which AI agents can reach which MCP servers from one switchboard What the original author did: MCP Switchboard connects all your MCP servers and APIs in one place, then controls exactly which AI agents can access what. The author runs it every day. Reported result (as claimed by the author): Says it became one of the most useful things they run. Source: https://x.com/cmercier/status/2109815620510327045 Tools they used: not named in the source Category: Dev & ops Please: 1. Ask me 3 short questions about my situation (accounts I have, budget, what I want the output to look like). 2. Propose a step-by-step plan using these tools or cheaper alternatives, with the time and cost of each step. Use official pricing pages; say "check pricing" if unsure. 3. Then do the setup with me one step at a time, waiting for my OK before anything that sends messages, posts publicly, spends money or deletes data. 4. Finish with a checklist to run it again next time.
The Daily 5
Get five new use cases tomorrow morning
Free. Real sources. Unsubscribe any time.
Related use cases
Keep coding agents running after you close the laptop lid
Built Lidless for timed closed-lid sessions that stay verified, journaled and restored so Claude Code and SSH agent runs survive closing the Mac.
Give AI agents persistent memory through a simple API
Built MemorySync so apps can give agents lasting user memory without building storage from scratch.
Give coding agents procedural memory that only keeps what passed tests
MuscleMemory remembers how a task was done only when tests passed, and trusts it after two more passing sessions. Claude Code reusing skills Codex learned used 43.5% fewer input tokens.
Run AI agents in low-cost sandboxes under a dollar a month
YC F26 team built Agent37 sandboxes for running agents at a reported average of $0.37 per sandbox per month.