MCPServerDesignPatterns
title: MCP Server Design Patterns type: technique created: 2026-05-19 last_updated: 2026-05-19 related: ["Playradar", "radar/platforms/ModelContextProtocol", "radar/tools/CLIPrintingPress"] sources: ["https://taoofmac.com/space/blog/2026/04/29/2341"] radar_quadrant: Techniques radar_ring: Assess radar_position: center
A set of practical design patterns for building Model Context Protocol (MCP) servers that guide AI models effectively through multi-step tool chains. Distilled from production MCP server experience by the author of taoofmac.com. Addresses the gap between an MCP server that works and one that models can use without confusion.
Limit surface area: Expose 5-10 core verbs prominently; keep specialised tools hidden as fallbacks. "The surface the model sees is small; the surface it can reach is large." Models hallucinate less when the active tool set is narrow.
Consistent naming: Use prefixes that signal chaining (word_*, excel_*, office_*). Naming patterns let models compose tool calls logically without explicit planning steps.
Breadcrumb responses: Every tool output should suggest next steps — hints and usage examples. Smaller models that cannot plan independently can follow breadcrumbs from one tool to the next.
Persistent addressing: Use anchors and identifiers rather than line numbers or byte offsets to maintain state between calls. Offset-based references break when prior tool calls modify document structure.
Mode-based tools: Collapse related tools into a single tool with modes (dry_run, safe, strict). Reduces context overhead without reducing capability.
Discovery as data: Return structured recommendations rather than prose documentation. Models parse structured output; they interpret prose inconsistently.
The author is skeptical of MCP as a pattern but advocates doing "the boring work in the schema" — investing in tool descriptions, response formats, and naming conventions — so models can focus on task logic rather than guessing tool selection.
Model Context Protocol (Platforms/Assess/inner) is the prerequisite: these patterns apply only when building or extending an MCP server. CLI Printing Press (Tools/Assess/inner) generates MCP servers from API specs; applying these design patterns during or after generation would improve the output.
MCP Server Design Patterns sits in the Assess ring of the Techniques quadrant, at center position. First studied via taoofmac.com on 2026-05-19; no personal MCP server development. Center position reflects patterns that are concrete and immediately applicable once MCP server development begins — but contingent on trialing MCP first (Platforms/Assess/inner). The remaining gate is a first personal MCP server project where these patterns can be applied and validated.
