Using Multiple MCP Servers with One Agent

One agent can use multiple servers, but combining tool catalogs introduces naming, latency, and trust problems.

Namespace collisions

Use server-prefixed names or a collision policy when two servers publish the same tool name.

Cache stable catalogs

Remote servers can add list-tools latency to each run. Cache lists where definitions and authorization context are stable.

Filter aggressively

Do not expose every tool from every server simply because the runtime can. Give each agent only the minimum capabilities needed for its responsibility.

Separate trust

A trusted internal database server and a public documentation server should not receive identical credentials, metadata, or approval policies.