Why it matters
Understanding these established MCP server patterns can help developers build more robust and scalable LLM-integrated applications. It provides a framework for organizing the complex interactions between LLMs and external tools or data, potentially reducing development time and improving system reliability.

What changed

This industry experience paper introduces and catalogues five recurring architectural patterns for Model Context Protocol (MCP) servers. MCP, an interface developed by Anthropic in November 2024, standardizes how large language models (LLMs) connect to external tools, data sources, and services. The paper identifies these patterns by analyzing a corpus of fifteen independently developed MCP servers, including production servers from the ANSYR voice AI platform and public servers from the official MCP registry. The five identified patterns are: Resource Gateway, Tool Orchestrator, Stateful Session Server, Proxy Aggregator, and Domain-Specific Adapter. Each pattern is described using the structured format of "context, problem, solution, and consequences." Additionally, the research documents four anti-patterns and discusses cross-cutting concerns such as authentication, versioning, and observability within the MCP ecosystem.

The paper also presents quantitative evaluations. It measures the inter-rater reliability of the pattern taxonomy across two independent LLM raters on 54 held-out servers, achieving a Cohen's kappa of 0.76 and identifying three pattern-boundary ambiguities. Transport overhead was measured end-to-end on loopback and modeled for cross-host paths. A tool-count study revealed that tool-selection accuracy for Claude Haiku 4.5 drops below 90% when using between 10 and 15 tools per context, and for Claude Sonnet 4, this accuracy threshold is crossed between 20 and 30 tools.

A replication package containing code, the corpus of servers analyzed, and prompts used in the study has been released.

Why it matters for builders

For developers working with LLM-integrated applications, this paper offers a valuable taxonomy of established architectural patterns for MCP servers. Recognizing these patterns can guide the design and implementation of new systems, promoting consistency and best practices within the rapidly evolving LLM ecosystem. By understanding common solutions and potential pitfalls, builders can more effectively manage the complexity of connecting LLMs to diverse external resources.

Practical impact

Developers can leverage the described patterns to structure their own MCP server implementations. For instance, a "Resource Gateway" pattern might be suitable for exposing specific data sources to an LLM, while a "Tool Orchestrator" could manage complex workflows involving multiple external tools. The identification of anti-patterns provides crucial warnings against common mistakes. The quantitative data on tool-selection accuracy offers practical guidance for optimizing LLM performance, suggesting that developers should be mindful of the number of tools exposed to the LLM to maintain high accuracy, especially with models like Claude Haiku 4.5.

Caveats and source limits

The paper is an industry experience paper, offering observations and cataloged patterns rather than a formal, prescriptive standard. The analysis is based on a corpus of fifteen servers, which, while diverse, may not represent the entirety of the MCP server ecosystem. The quantitative evaluations, such as transport overhead and tool-selection accuracy, are specific to the tested configurations and models (Claude Haiku 4.5 and Sonnet 4) and may vary with different LLMs or network conditions. The inter-rater reliability score of 0.76 indicates good agreement but also highlights three identified ambiguities in pattern boundaries, suggesting that the classification might require further refinement. The paper notes that no software-maintenance literature has yet described how the MCP ecosystem is being structured in production, indicating this is an early-stage analysis.

Sources

Written with AI assistance from the linked sources; every claim below was checked against them automatically. How we produce articles.

Claim check: 8/8 supported claims - 8 evidence links - 100% avg confidence
  • The Model Context Protocol (MCP) defines a standardized interface for connecting large language models (LLMs) to external tools, data sources, and services.supported - arxiv.org
  • Hundreds of community-built MCP servers appeared on GitHub within months of MCP's release.supported - arxiv.org
  • The paper catalogues five recurring MCP server architectural patterns: Resource Gateway, Tool Orchestrator, Stateful Session Server, Proxy Aggregator, and Domain-Specific Adapter.supported - arxiv.org
  • The research documents four anti-patterns related to MCP server architecture.supported - arxiv.org
  • The study found inter-rater reliability of the MCP server pattern taxonomy across two independent LLM raters on 54 held-out servers to be Cohen's kappa = 0.76.supported - arxiv.org
  • Tool-selection accuracy drops below 90% between 10 and 15 tools per context for Claude Haiku 4.5.supported - arxiv.org
  • Tool-selection accuracy drops below 90% between 20 and 30 tools per context for Claude Sonnet 4.supported - arxiv.org
  • A replication package containing code, corpus, and prompts for the study is released.supported - arxiv.org

Caveats

  • The MCP was introduced by Anthropic in November 2024.
  • Single-source caution: verify critical details at the linked source.
Radar score 80/100 - how it was calculated
Reliability80
Freshness90
Novelty77
Technical82
Developer72
Ecosystem68
Confidence98
  • Reliability 80: Research metadata source
  • Freshness 90: Fresh research date
  • Novelty 77: Research implementation signal
  • Technical 82: Research technical evidence
  • Developer 72: Research developer relevance
  • Ecosystem 68: Research implementation signal
  • Confidence 98: Claims have reliable evidence
Share
XLinkedInHacker News

Discussion

Loading comments...

Related articles

Agents - Nov 15, 2026Couchbase MCP Server Connects LLMs to Couchbase DataCouchbase has released an MCP Server that enables AI agents and LLMs, such as Claude and Copilot, to interact with data stored in Couchbase or Capella. The server supports various tools for cluster health, data schema, and query analysis, with built-in safety features.AI Tools - Oct 5, 2026Pairlet v2.3.0 Released for Local AI Coding TasksPairlet, formerly CC Pocket, has released version 2.3.0. This Kotlin-based project allows users to continue local AI coding tasks from various devices, including phones, tablets, and desktops.AI Tools - Oct 22, 2026Obsidian Vault Intelligence Plugin UpdatedThe Obsidian Vault Intelligence plugin, a TypeScript project focused on enhancing Obsidian vaults with AI capabilities, has recently released version 9.9.1. This update signifies ongoing development for the plugin, which leverages AI agents and RAG for knowledge management within Obsidian.Agents - Oct 25, 2026CUBRID MCP Server for LLM Database InteractionThe CUBRID MCP Server is a Python-based Model Context Protocol server designed to enable Large Language Models (LLMs) to interact with the CUBRID database. It allows LLMs to inspect database schemas and execute read-only SQL queries through the pycubrid library.AI Tools - Nov 14, 20260sec-labs/0 Cybersecurity Harness with Agent CapabilitiesThe 0sec-labs/0 repository offers an open-source cybersecurity harness. It features a web interface for code analysis, pentesting, vulnerability research, reverse engineering, verification, and fixing, alongside CLI and MCP for agent integration.AI Tools - Oct 21, 2026Douban CLI with AI Agent SkillMarvae/douban-cli is a TypeScript-based command-line tool for interacting with Douban services. It allows users to search for movies, TV shows, and books, export their viewing and reading records, and integrate AI for rating content.