Article reader Listen + reading controls
Article reader
Preparing the reader…
Reading settings
The protocol is becoming an organizational boundary¶
Anthropic's June 18 update adds remote Model Context Protocol (MCP) support to Claude Code. Developers can connect the coding agent to hosted tools and knowledge sources without operating each integration locally.
This is convenient infrastructure. It also moves an important boundary: the agent can now cross from a code repository into project systems, observability platforms, knowledge bases, and other services through a common protocol.
MCP standardizes how an artificial intelligence application discovers and invokes external tools and resources. Standardization reduces bespoke integration work and can improve portability. It also makes the protocol a control surface.
Context and authority travel together¶
An agent that reads an error from an observability service and edits code crosses several professional and system boundaries. If it can also update the issue, trigger a workflow, or alter production state, it moves from information access to organizational action.
Authentication tells the service which identity is present. Authorization must still answer whether this agent, acting for this user, on this task, under these conditions, may take this action.
Broad delegated credentials are especially dangerous because the agent's technical reach can exceed the user's intent. Tool descriptions and server behavior can also change after the initial connection.
Treat servers as suppliers¶
Organizations should manage remote protocol servers with the same discipline applied to software dependencies and service providers:
- owner and purpose;
- approved tools and data classes;
- identity and least-privilege design;
- version and change notification;
- logging and retention;
- security testing;
- availability and failure behavior;
- and a revocation path.
A directory entry is not an assurance case. The server sits inside the trust chain of every agent that uses it.
Make the handoff inspectable¶
Carlile's concept of boundary objects helps explain the organizational value. A protocol object can allow different systems and communities to exchange work without sharing every internal detail.
But useful boundary objects preserve enough context for interpretation. A tool call should include the task purpose, relevant provenance, requested authority, and expected result. The receiving system should return not only data but confidence, status, and a record that can be traced.
Plan for partial failure¶
Remote services will time out, return stale data, change schemas, or become unavailable. Agents may retry in ways that duplicate an action. Designers need idempotency, clear error states, bounded retries, and human escalation for ambiguous outcomes.
The agent should never infer that silence means success.
Protocols can accelerate a healthy ecosystem of interoperable tools. Their adoption will also expose whether organizations make authority and responsibility explicit enough to be encoded.
The protocol is not merely a connector. It is where data, action, trust, and accountability cross from one system to another. That boundary deserves first-class engineering and governance.
Sources and research trail¶
- Anthropic, “Remote MCP Support in Claude Code” (June 18, 2025).
- Model Context Protocol, specification and documentation.
- Carlile, “A Pragmatic View of Knowledge and Boundaries” (2002).
- Okhuysen and Bechky, “Coordination in Organizations” (2009).