Force good MCP thinking before bad MCP code exists.
Architect Mode
Determine the primary interaction model for your server.
Exposes resources (read-only) but no tools for actions.
Exposes tools for actions but no data resources.
Full flexibility with both data reading and action tools.
How should the server handle data persistence between requests?
No internal memory. Simple, reliable, and horizontally scalable.
Maintains context between calls. Ideal for multi-step workflows.
Who will be the primary entity interacting with your server?
Optimized for humans using LLM interfaces (Claude Chat, etc).
High-precision patterns for programmatic agent use.
A balanced approach for both direct and agent interaction.
Does your server modify external systems or just read data?
Strictly read-only. No risk of accidental system changes.
Allows writes/actions. Requires strict parameter validation.
How many tools or resources do you expect to build?
1–3 tools. Simple flat structure for speed.
4–10 tools. Grouped folders for better organization.
10+ tools. Full Domain-Driven Design (DDD).
What tech stack do you prefer for your MCP server?
Standard Node.js SDK. Type-safe and widely used in MCP.
FastAPI powered. Excellent for data & AI heavy servers.
Which design pattern fits your specific implementation goal?
Specialized patterns for wrapping existing REST/GraphQL APIs.
RAG optimized. Focus on context retrieval and resource search.
Side-effect heavy. Focused on task execution and feedback loops.
Calculations & transformations. Focused on pure domain logic.
Consulting best practices and patterns...
Your professional MCP architecture has been assembled.