Multi-MCP workflows: what changes when agents and tools multiply?

TL;DR: Scaling MCP adoption creates three compounding problems, configuration sprawl, tool overload, and orchestration inefficiency, and that layered controls can separate connection management, tool discovery, and workflow execution, according to Stacklok. The governance gap is no longer just access to one server, but consistent control over many NHI-like tool connections across developers and AI agents.

NHIMG editorial — based on content published by Stacklok: Optimizing multi-MCP workflows

By the numbers:

• Only 18% of MCP server deployments implement any form of access scoping for tool permissions.

Questions worth separating out

Q: How should security teams govern access to MCP registry-discovered servers?

A: Security teams should treat registry-discovered servers as governed non-human access, not as simple developer convenience.

Q: Why do multi-MCP setups create so much operational risk?

A: They multiply credentials, endpoints, and tool definitions faster than teams can govern them.

Q: What breaks when too many tools are exposed to an AI assistant?

A: Selection quality drops because the model must evaluate more options than it can efficiently reason over.

Practitioner guidance

• Centralise MCP connection ownership Move credentials, endpoints, and transport settings into a single governed gateway so every developer and agent inherits the same policy state.
• Reduce exposed tool surface area Limit each assistant or persona to the smallest practical tool set and hide irrelevant tool definitions by default.
• Treat composite workflows as privileged automation Version-control workflow definitions, require review before changes, and separate approval-gated actions from read-only steps.

What's in the full article

Stacklok's full blog post covers the operational detail this post intentionally leaves for the source:

• The vMCP gateway configuration model for centralised authentication, token exchange, and tool scoping.
• The MCP Optimizer benchmark data showing how just-in-time discovery changes token usage and tool selection accuracy.
• The composite tool YAML pattern for parallel execution, conditional branching, and approval-gated steps.
• The development roadmap for MCP sampling and scripting extensions that change workflow expressiveness.

👉 Read Stacklok's analysis of multi-MCP workflow scaling and governance →

Multi-MCP workflows: what changes when agents and tools multiply?

Explore further

View Full Forum →  |  NHI Foundation Course →