§ Internal tool · MCP
One MCP that knows every tool I use to run Devfrend.
Jira, Cal.com, Gmail, Stripe, Notion — all behind a single MCP surface I can script against from any AI assistant.
- Sector
- Internal tools
- Year
- 2026
- Role
- Sole engineer
- Stack
- TypeScript · MCP · OAuth 2.0
01 · Problem
Running a one-person studio means switching between 12 apps a day. Each AI assistant needs its own integrations wired up. Duplication everywhere.
02 · Approach
- 01
Built a single MCP server with a plugin model per tool.
- 02
Auth via OAuth device flow, secrets in macOS Keychain.
- 03
Published as a private npm package I can pin in any Claude or Cursor config.
03 · Outcome
-71%
Daily context switches
Measured over a two-week baseline.
14
Tool integrations
All behind one MCP entry.
Stack
- TypeScript
- MCP
- OAuth 2.0
- Keychain
- Zod
Next case
OpenClaw →
A scroll-driven product site for a dev-tool launch.