Apply Clean MCP Architecture

Architectural standard for TypeScript MCP servers built with mcp-use/server. Decides where files live, what each layer may import, what bootstrap wires, and how the discipline is enforced. Mechanical recipes (exact APIs, auth, transports, widgets) live in build-mcp-use-server.

When to use this skill

Trigger on phrases or contexts like:

• "where should this tool / gateway / presenter / port live?"
• "refactor this monolithic src/tools/*.ts into clean layers"
• "audit this MCP server's architecture" / "PR review for layering"
• "set up dependency-cruiser for an mcp-use server"
• "why is mcp-use imported from domain/ or application/?"
• "scaffold a greenfield mcp-use/server repo with proper folders"
• "process.env is being read all over the codebase — fix the seam"
• "design ports, adapters, and provider error classification"

Do NOT use this skill when: