# MCP Server架构模式论文：LLM集成应用工具设计需遵循5种模式、避免4类错误

- 来源：Rohan Paul (@rohanpaul_ai)
- 发布时间：2026-07-02 09:56
- AIHOT 分数：69
- AIHOT 链接：https://aihot.virxact.com/items/cmr2v42gn0bjjsl8znutphiq5
- 原文链接：https://x.com/rohanpaul_ai/status/2072499557712507190

## AI 摘要

该论文指出，MCP服务器设计不同于普通API，因为LLM通过纯语言描述选择工具，过多或模糊的工具会导致混淆。作者归纳了5种实际模式（如暴露数据、运行工作流、保持会话状态、组合服务器、翻译混乱领域API），并警告4个常见错误（大而全工具、模糊描述、不安全外部内容、慢工具应返回job ID）。在54个额外服务器上测试发现，弱模型在可见工具超过10-15个时准确率降至90%以下。良好MCP设计的核心是使工具列表小巧、清晰、安全且稳定。

## 正文

Very timely paper.

MCP servers need clear design patterns because LLMs get confused when too many tools or vague tools are shown.

This paper explains how MCP servers should be structured so LLM tools stay useful， safe， and manageable.

s MCP server design is not just normal API design， because the client is an LLM that chooses tools by reading plain-language descriptions.

It groups real MCP servers into 5 useful patterns， such as servers that expose data， run workflows， keep session state， combine many servers， or translate messy domain APIs.

The authors also warn about 4 common mistakes， especially giant all-purpose tools， vague tool descriptions， unsafe outside content， and slow tools that should return a job ID instead.

They tested the pattern labels on 54 extra servers， measured transport delay， and studied how tool accuracy changes as more tools are shown.

The key result is that too many visible tools hurt accuracy， with weaker models dropping below 90% between 10 and 15 tools.

Good MCP design is mostly about making the tool list small， clear， safe， and stable enough for LLMs to choose the right action.

----

Link - arxiv. org/abs/2606.30317

Title： "MCP Server Architecture Patterns for LLM-Integrated Applications"