Claude Code. The MCP stack. One live app.

The configuration I actually ship with. Version-pinned, smoke-tested, with the tools I dropped and why.

Powers DSGVO.pro (scan → reports → email) — live since 2026-04.

The principle

Boring is good. I pick tools I can replace in one afternoon — not because I plan to, but because optionality is its own feature.

Every tool here earns its row twice: once in a real project, once again surviving the monthly review. The ones that didn't are in anti-picks.

Claude Code↗ ref— The agent. Anthropic Opus + Sonnet, MCP-native, terminal-first.
Custom subagents— Specialized .claude/agents/ — Explore, Plan, domain helpers.

Next.js— Framework. App Router, server components, the boring choice.
Supabase— Postgres + auth + EU hosting. DPA available, predictable pricing.
Vercel— Deploy + edge. Fast iteration, no infra to babysit.
Trigger.dev v4— Background jobs, scheduled tasks, debounced triggers. Replaces 3 services.
DSGVO.pro MCP— Own product, dogfooded. Compliance scan during builds — actually used.
Playwright— Browser automation. Powers the DSGVO.pro site scanner — fetch, render, extract.
Brevo— Web forms + transactional email. The contact form on this site routes through it.

Obsidian— Second Brain — local-first markdown vault. Claude Code reads it directly, no MCP needed.
Google Workspace MCPs— Gmail + Calendar + Drive in one cluster. Daily ops surface.

atypica↗ ref— Synthetic-persona research. Brand validation before commit.
Higgsfield— Image and video generation. Faster than the alternative I tried.
Gamma↗ ref— Presentations from prose. Output good enough to ship.
Context7— Live library docs in-prompt. Skips outdated training data.
gsc-toolkit— Local CLI for Google Search Console data. SEO context for any project.

DSGVO.pro— Own product, in production. Powers the compliance banner across my client sites.

The list of tools that didn't survive contact with my actual workflow. The reason is more useful than the name.

Figma MCPsupersedence
Claude Design (Anthropic) replaces the design-to-code role in my workflow. I haven't needed Figma MCP since.
Notion MCPsupersedence
Obsidian is my Second Brain — local-first markdown that Claude Code reads natively without an MCP layer. Notion never won the daily-use slot.
Slack MCPplatform mismatch
Solo operator, no team chat to integrate. Adding Slack MCP would be cargo-cult of someone else's stack shape.
Sentrymaintenance abandoned
Tried, didn't stick. Noise-to-signal stayed bad in solo-operator scale; alerts I cared about were already visible in Vercel logs + Trigger.dev runs. Sentry became dead actor in my stack.

Full list with reasons → docs/anti-picks.md

Known failure modes, with fixes. The full list lives in the repo.

STDIO corruption— `console.log` writes to the same channel MCP uses for JSON-RPC. Replace with `console.error`.
Windows MSIX paths— spaces in `Program Files` break MCP launchers. Use nvm-windows or WSL.
Zombie MCP processes— missing SIGTERM handlers leave processes alive after Claude exits.
~/.claude/settings.json vs ~/.claude.json— two settings locations with overlapping keys. Keep only the newer one.

With reproductions and fixes → docs/failure-modes.md

For EU enterprise sharing — where each tool lives, and whether a DPA exists.