Built ConnectStack: 57 MCP Tools Across 10 Integrations in One Session

Just wrapped up a marathon build session on ConnectStack™ — my new MCP (Model Context Protocol) framework that connects AI assistants to your entire dev stack.

What I Built

Started completely from scratch and built out 57 MCP tools across 10 different integrations:

Phase 1 (5 servers):

• GitHub (6 tools) — repos, issues, PRs, the works
• Stripe (6 tools) — payments, customers, subscriptions
• Supabase (6 tools) — database ops, auth, storage
• Railway (6 tools) — deployments, services, variables
• SendGrid (5 tools) — email campaigns and delivery

Phase 2 (5 more servers):

• Netlify (6 tools) — sites, builds, DNS management
• Cloudflare (5 tools) — zones, Workers, cache control
• Hetzner (6 tools) — server management, firewalls, metrics
• n8n (5 tools) — workflow automation control
• UptimeRobot (6 tools) — monitoring and alerting

The Fun Technical Bits

Built everything from scratch using ESM Node.js with the official @modelcontextprotocol/sdk. No wrapper libraries — I wanted full control and consistency across all integrations.

The setup wizard was particularly satisfying to build. Interactive CLI that validates your API credentials in real-time and encrypts everything with AES-256-GCM (using your machine ID + salt via PBKDF2). No plaintext secrets lying around.

Bug Hunting Adventures

Hit some fun gotchas along the way:

• GitHub's API is picky about auth headers — classic PATs need token prefix, not Bearer
• Railway moved from .com to .app for their API endpoint
• Supabase's /pg/query REST endpoint is broken, had to switch to direct Postgres connections
• UptimeRobot does auth via POST form body instead of headers (quirky but whatever)

The usual suspects, but satisfying to track down and fix.

What's Next

Got the core framework solid now. Next up is Phase 3 (Notion, Linear, Discord) and then Phase 4 — the DevLog Pipeline as a Service that I'm really excited about.

Also need to do real-world testing with actual API keys across all 10 services. The setup script looks clean but you never know until you run it against the real APIs.

Thinking about pricing and how this fits into the broader stack alongside MemStack Pro. Could be a nice cross-sell opportunity.

The Vibe

This was one of those flow-state coding sessions where everything just clicked. 38 files, 5 commits, zero uncommitted changes. Clean repo, clean architecture, ready for the next phase.

ConnectStack is shaping up to be exactly what I wanted — a unified way to give AI assistants full access to your development workflow. No more context switching between tools.