Building an MCP app (draft)

Draft — rough capture of a recent project where I shipped an MCP-facing app; I’ll expand with architecture, pitfalls, and links once I pull my notes together.

MCP is the protocol; an MCP app here means the runnable piece that speaks MCP (usually a server: tools/resources/prompts over stdio or HTTP/SSE) plus whatever wraps it for local or hosted use. The interesting parts in practice are: schema for tools, auth/secrets, error surfaces back to the client, and how you test without a human in the loop on every change.

Related in this repo: OpenAPI → MCP pipeline, the various *-mcp-server notes, and Playwright MCP as a reference implementation pattern.

To fill in: problem I solved, stack, deploy shape, one “aha” failure, and what I’d do differently next time.