One Conversation,
Sixteen Services

The MCP bridge behind Amplifier's Agency bundle

The Frame

A dozen internal services usually means a dozen custom integrations

Reaching many walled-off enterprise services from one agent normally means writing bespoke plumbing for each. Amplifier's tool-mcp bridge is how it avoids that.

And this isn't theory — it already runs at scale.

The bridge: microsoft/amplifier-module-tool-mcp, v0.2.2 — adds MCP server integration to Amplifier bundles.
What it does: connect to any MCP-compatible server and make its tools available to your AI agents.

Proof

The bridge already runs at multi-server scale

Its own reference deployment is production-proven: 60 capabilities drawn from 5 MCP servers — 41 tools plus 19 prompts — all reachable from one agent.

So the pattern works. Why isn't every service wired this way already?

60

Capabilities from one deployment

5

MCP servers

41

Tools

19

Prompts

The Tension

The old way makes each new service its own integration project

Without a shared bridge, every service brings its own bespoke code, its own auth, and its own glue — per server, over and over.

The bridge exists to erase exactly this cost. Here's how.

Bespoke integration code — per server
Its own auth wiring — per server
Its own glue to the agent — per server

Mechanism — Connect

One agent connects to many MCP servers at once

The bridge does multi-server orchestration: stdio servers are spawned as child processes via command + args; Streamable HTTP servers connect over HTTP.

Many connections — but how do they become one usable toolset?

1

stdio — server spawned as a child process via command + args

2

Streamable HTTP — server connected over HTTP (2025-03-26 MCP spec)

3

Each server's tools, resources and prompts are registered into the agent

Mechanism — Compose

Every server's tools compose into one toolset without collisions

Each tool is namespaced per server, so many servers merge into a single agent toolset with no name clashes.

Connected and composed — and still, no per-server code to write.

# tool naming pattern (wrapper.py)
mcp_{server_name}_{tool_name}

# many servers, one namespaced toolset
mcp_serverA_search
mcp_serverB_search   # no collision

Mechanism — Zero Plumbing

It's zero per-server code: MCP ships as a composable behavior

MCP support is delivered as behaviors/mcp.yaml (v0.2.0), added with the --app flag. Servers resolve from four config sources — priority inline > env > project > user — with nothing to hand-wire, and zero overhead when unconfigured.

Now put a real set of services on top of it.

# add MCP as an app bundle (composes every session)
amplifier bundle add \
  git+https://github.com/microsoft/amplifier-module-tool-mcp@main#subdirectory=behaviors/mcp.yaml --app

# config priority (code-verified, config.py)
inline > env > project > user

The Payoff

The Agency bundle reaches 16 Microsoft internal services from one conversation

On top of this bridge, Samuel Lee's amplifier-bundle-agency — established 2026-04-03 in 2 commits — packages 16 zero-config MCP servers for Microsoft internal services. One conversation, sixteen services, no per-server code.

And the walls collapse for any services that speak MCP.

16

Zero-config MCP servers for Microsoft internal services

2

Commits to establish the bundle (2026-04-03)

0

Lines of per-server code

The Takeaway

Any set of MCP-compatible services can compose into one conversation

The Agency bundle is one instance of a reusable pattern: the tool-mcp bridge connects many MCP servers over stdio or Streamable HTTP, namespaces their tools into a single toolset, and needs zero per-server code. Point it at your services — the walls collapse the same way.

Sources

Research Methodology

Bridge: verified from source Agency: corpus snapshot 2026-06-25

Data as of: Agency corpus snapshot 2026-06-25 (module.md last_updated 2026-06-26); tool-mcp cloned repo HEAD b32b7ce, 2026-05-03.

Commands run:

git remote -v — confirms origin microsoft/amplifier-module-tool-mcp; grep version pyproject.toml → v0.2.2
sed -n '208,275p' amplifier_module_tool_mcp/manager.py — multi-server capability registration
grep -n 'stdio_client|command|args' client.py — stdio (command+args) and Streamable HTTP transports
sed -n '47,60p' amplifier_module_tool_mcp/wrapper.py — tool naming mcp_{server}_{tool}
cat behaviors/mcp.yaml & sed -n '14,90p' config.py — composable behavior, 4-source config priority inline > env > project > user
grep -n 'Production Proven|60 capabilities' README.md — 60 capabilities, 5 servers, 41 tools + 19 prompts
cat samueljklee__amplifier-bundle-agency-2026-06-25-changes.md — 16 zero-config servers, 2 commits, 2026-04-03, Samuel Lee

Contributors: Samuel Lee (samueljklee) — author of amplifier-bundle-agency, both 2026-04-03 commits. Marc Goodner — earliest cloned tool-mcp commits (2025-10-28). sadlilas — latest cloned tool-mcp commit (2026-05-03, transport hardening).

Gaps: The Agency repo was not accessible via gh (“Could not resolve to a Repository”); its live source could not be read. Agency facts come solely from the corpus snapshot documenting the initial 2026-04-03 state. Claims such as 226 tools, a two-agent 75+151 split, Entra auth, and an IcM→Kusto→ADO→Teams flow could not be verified and are deliberately omitted. The bridge mechanism is fully verified from the cloned microsoft/amplifier-module-tool-mcp repo.

One Conversation,Sixteen Services