1mcp/agent
by Various
A unified Model Context Protocol server implementation that aggregates multiple MCP servers into one.
MCP
1mcp/agent
Added 1 June 2026
Overview
1mcp/agent is a TypeScript library that aggregates multiple Model Context Protocol (MCP) servers into a single unified server. It provides a single endpoint for clients to interact with multiple MCP servers without managing separate connections.
Best for
Best for
Developers building MCP-based agents or tools that need to interact with multiple MCP servers
Use cases
- Combine multiple MCP servers into one endpoint for simpler client configuration
- Build an agent that can route requests to different MCP servers based on context
- Reduce the number of network connections needed when using several MCP servers
Notes
1mcp/agent is a TypeScript library that aggregates multiple Model Context Protocol (MCP) servers into a single unified server. It provides a single endpoint for clients to interact with multiple MCP servers without managing separate connections.
447 stars on GitHub. Last updated 2026-06-01. Licensed Apache-2.0.
Use cases
- Combine multiple MCP servers into one endpoint for simpler client configuration
- Build an agent that can route requests to different MCP servers based on context
- Reduce the number of network connections needed when using several MCP servers
Pros
- Simplifies client setup by exposing a single MCP server interface
- Open source with active development (447 stars on GitHub)
- Written in TypeScript for type safety and broad ecosystem compatibility
Cons
- Introduces a single point of failure if the aggregator goes down
- Adds an extra layer of abstraction that may increase latency
- Limited to MCP protocol servers; cannot aggregate non-MCP services
Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.
Pros
- Simplifies client setup by exposing a single MCP server interface
- Open source with active development (447 stars on GitHub)
- Written in TypeScript for type safety and broad ecosystem compatibility
Cons
- Introduces a single point of failure if the aggregator goes down
- Adds an extra layer of abstraction that may increase latency
- Limited to MCP protocol servers; cannot aggregate non-MCP services
Pairs with
Other entries in the index that connect to this one. Click through to see the chain.