TL;DR: Repeated agent integrations are where Model Context Protocol starts to pay off, Archestra argues, as shared discovery and reusable schemas begin to outweigh custom adapters and repeated auth flows. Server allowlists and ownership rules matter more once multiple services can reach the same tool surface.
Editorial analysis by NHI Mgmt Group, based on content published by Archestra: “When MCP makes sense the second time around”.
Key questions
Q: Why do direct API integrations create more risk as agent use expands?
A: Direct integrations tend to scatter access logic and tool definitions across code, prompts, and service-specific adapters.
Q: What breaks when every agent integration is custom-built?
A: What breaks first is consistency.
Q: When does MCP become worth using instead of direct API calls?
A: MCP becomes more defensible when repeated integrations start to create duplicated auth handling, schema maintenance, and tool definitions across multiple services or agents.
Practitioner guidance
- Map where bespoke adapters are already compounding Inventory agent integrations that each carry separate auth, pagination, and schema handling so you can see where maintenance cost is already repeating across services.
- Define server allowlists before standardising on MCP Set explicit rules for which servers each agent can discover and use, especially where internal tooling and consumer-facing workflows have different trust requirements.
- Separate tool schema governance from application code Move tool descriptions into a managed layer so schema changes do not depend on scattered prompt strings or one-off adapter logic.
Bottom line: MCP is most useful once repeated integrations create enough duplication that reusable discovery and shared schemas reduce real operational burden.
Glossary terms: Model Context Protocol, Tool Surface, Schema Drift, Server allowlist
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
MCP is becoming a governance layer, not just an integration convenience: The article shows that the protocol only looks optional when teams have one or two services and no reusable agent surface to govern. Once multiple agents consume the same service set, the control problem shifts from coding effort to consistent access and schema governance. The practitioner takeaway is that MCP should be evaluated as an identity and access boundary, not only as a developer convenience.
A few things that frame the scale:
- 24,008 unique secrets were exposed in MCP configuration files in 2025 alone, the protocol's first year of widespread adoption, according to the State of Secrets Sprawl 2026.
A question worth separating out:
Q: How should teams govern agent access when both CLI and MCP are available?
A: Govern them separately, because they expose different execution patterns. CLI is usually easier to inventory, validate, and retire, while MCP can preserve state across multiple actions and therefore needs tighter session controls. Access reviews should include interface type, exposed tools, and how state is retained or discarded.
👉 Read our full editorial: MCP pays off after the third integration, not the first