Multi-MCP Orchestrator: Isolating MCP tools across domain subagents

[Amine SBOUI (aminesbdev)]

Hey everyone,

Wanted to share an example I put together: deepagents-multi-mcp-orchestrator.

The Problem

When you plug multiple MCP servers (e.g. GitHub + SQLite) into an agent, shoving 30+ tools into a single prompt often leads to tool-call confusion, wrong arguments, and high token consumption.

What this does

It shows how to connect multiple MCP servers via MultiServerMCPClient (langchain-mcp-adapters) while keeping tools isolated per domain:

• Orchestrator Agent: High-level planner that breaks down the goal and delegates sequentially.
• github-agent (mode="isolated"): Only sees GitHub MCP tools.
• db-agent (mode="isolated"): Only sees SQLite MCP tools.

Each subagent runs in its own context and only returns its final synthesis to the parent, keeping the main context window small and clean.

Repo with runnable quickstart (uv ready):
👉 https://github.com/aminesbdev/deepagents-multi-mcp-orchestrator

Curious to hear your thoughts or feedback!

[lemonaide152]

Isolating MCP tools onto domain subagents still leaves the task itself that has to cross from the orchestrator to the specialist.

Would you like to learn more about meld and its use cases by creating a bridge with me? You create it at https://meld.mergeinc.workers.dev. Say what the bridge is for and what it is not for, and send the URL. It stays open 36 hours until the first reply. Each later reply resets 24 hours. The conversation stays on that same link. It is free, and there is no billing. It will not route tools or be shared tool memory.