Enhancing Model Context Protocol (MCP) with Context-Aware Server Collaboration
On the map: LLM agents and tool use → Tool learning and function calling
Abstract (arXiv)
The Model Context Protocol (MCP) (MCP Community, 2025) has emerged as a widely used framework for enabling LLM-based agents to communicate with external tools and services. The original MCP implementation (Anthropic, 2024) relies on a Large Language Model (LLM) to decompose tasks and issue instructions to servers. In particular, the agents, models, and servers are stateless and do not have access to a global context. However, in tasks involving LLM-driven coordination, it is natural that a Shared Context Store (SCS) could improve the efficiency and coherence of multi-agent workflows by reducing redundancy and enabling knowledge transfer between servers. Thus, in this work, we design and assess the performance of a Context-Aware MCP (CA-MCP) that offloads execution logic to specialized MCP servers that read from and write to a shared context memory, allowing them to coordinate more autonomously in real time. In this design, context management serves as the central mechanism that maintains continuity across task executions by tracking intermediate states and shared variables, thereby enabling persistent collaboration among agents without repeated prompting. We present experiments showing that the CA-MCP can outperform the traditional MCP by reducing the number of LLM calls required for complex tasks and decreasing the frequency of response failures when task conditions are not satisfied. In particular, we conducted experiments on the TravelPlanner (Yang et al., 2024) and REALM-Bench (Geng & Chang, 2025) benchmark datasets and observed statistically significant results indicating the potential advantages of incorporating a shared context store via CA-MCP in LLM-driven multi-agent systems.
Key facts. Cited by 2 papers in the map (data through 7 Oct 2026). Placed in Tool learning and function calling, one of 16 directions in LLM agents and tool use. Builds on 11 of its 23 references that are in the map. First posted on arXiv 6 Jan 2026.
Builds on
11 of 23 references.
References · 11
- 2019BERTScore: Evaluating Text Generation with BERTcited by 5,462
- 2025Multi-Agent Collaboration Mechanisms: A Survey of LLMscited by 424
- 2024TravelPlanner: A Benchmark for Real-World Planning with Language Agentscited by 385
- 2025G-Memory: Tracing Hierarchical Memory for Multi-Agent Systemscited by 112
- 2025Multi-Agent Collaboration via Evolving Orchestrationcited by 102
- 2023LLM-Coordination: Evaluating and Analyzing Multi-agent Coordination Abilities in Large Language Modelscited by 65
- 2025SagaLLM: Context Management, Validation, and Transaction Guarantees for Multi-Agent LLM Planningcited by 58
- 2025LEGOMem: Modular Procedural Memory for Multi-agent LLM Systems for Workflow Automationcited by 39
- 2025REALM-Bench: A Benchmark for Evaluating Multi-Agent Systems on Real-world, Dynamic Planning and Scheduling Taskscited by 16
- 2025Exploring Advanced LLM Multi-Agent Systems Based on Blackboard Architecturecited by 10
- 2025Neural Orchestration for Multi-Agent Systems: A Deep Learning Framework for Optimal Agent Selection in Multi-Domain Task Environmentscited by 3
Built on by
Citing papers per year: 2026: 2.
2 papers.
Similar, not cited
Close in wording, no citation either way
- 2025MCP-Flow: Facilitating LLM Agents to Master Real-World, Diverse and Scaling MCP Tools
- 2025Network and Systems Performance Characterization of MCP-Enabled LLM Agents
- 2025Advancing Multi-Agent Systems Through Model Context Protocol: Architecture, Implementation, and Applications
- 2025LiveMCPBench: Can Agents Navigate an Ocean of MCP Tools?
- 2026Understanding How Enterprises Adopt the Model Context Protocol for LLM-Driven Software Engineering
- 2025ScaleMCP: Dynamic and Auto-Synchronizing Model Context Protocol Tools for LLM Agents
- 2026From Tool Orchestration to Code Execution: A Study of MCP Design Choices
- 2025MCP-Bench: Benchmarking Tool-Using LLM Agents with Complex Real-World Tasks via MCP Servers