Advanced Capabilities and Multiple-Server Architecture

Sampling

A server can request model generation from the host/client when the client supports it. The host retains control over model access, user control, and policy. Do not assume sampling support.

Elicitation

A server can request structured user input when supported. Do not use a general elicitation form to collect secrets or passwords; choose an approved secure flow.

Roots

The client can expose permitted filesystem roots to the server. The root list is not a replacement for an authorization boundary; the server must still validate received paths.

Multiple servers

A host can connect to multiple MCP servers. Large catalogs increase model confusion and context costs.

flowchart LR
  H[Host orchestrator] --> R[Repository server]
  H --> B[Business data server]
  H --> T[Support server]
  R --> RC[Source and docs]
  B --> DB[(Business database)]
  T --> TS[Ticket service]

Use capability routing, per-server trust levels, namespaced tools, and limited catalog exposure. For cross-server workflows, plan shared identity, data classification, rollback, and an audit trail.