Skip to content

MCP Servers in the Wild: Managing Tool Complexity at Scale - Arnav Balyan, Concierge AI#

MCP Dev Summit North America 2026 digest Program Adjacent pick 2–3 April 2026

Abstract

Arnav Balyan, CEO, Concierge AI

  • Why: At high tool counts, agents make wrong calls, burn tokens, and skip required call sequences — a reliability and compliance risk precisely in the high-stakes domains the PM cares about (infrastructure, finance).
  • What: A server design pattern called "progressive tool exposure": the MCP server actively controls which tools are visible to the agent at each point in execution, refreshing and scoping tools as the agent progresses, directing the action space and enforcing runbooks; the server also tracks state so backtracking reverts server-side state, making agent behavior transactional. Claims: fewer invalid tool calls, lower inference cost, improved determinism (from abstract only).
  • How: Server-driven tool visibility plus stateful workflow scoping — the server shapes what the agent can see and do at each step.
  • Where applicable: Tool-heavy, high-stakes MCP systems; the vendor manages 400+ public MCP deployments (real data, but also product positioning — treat the claims as directionally interesting until details land). The pattern itself is implementation-agnostic.