Show us your MCP stack — what are you running right now?

Drop:

• Which MCP servers you use
• What client (Claude, Cursor, etc.)
• One thing that's been surprisingly useful

I'll go first:

Servers:

• playwright (@playwright/mcp@latest, stdio) — in 4 different projects
• bridge (bridge-mcp, stdio)
• jira / atlassian (mcp-atlassian, stdio)
• designforyou (http)
• document_operations (document-edit-mcp, stdio)

All of them configured per-project rather than globally — different projects genuinely need different servers, and a global config just becomes noise in every session.

Client: Claude Code (no Claude Desktop config in use at all).

Surprisingly useful: Playwright MCP, but not as a casual browser-automation toy. It's a hard QA-verification requirement here — a frontend change isn't done until it's been run in a real browser and asserted: computed CSS values, video.muted === true, bounding-box overlap checks, that kind of thing. It has caught real bugs unit tests missed, like a text-muted class that resolved to zero computed CSS, and a GitHub-connect 401 that only surfaced in a live browser session.