Chapter C57 · Interactive Course
Transport and authorized access
Local processes, endpoints, streaming, scopes, tokens and revocation.
Core Learning Concept
Inspect connection endpoints, transport mechanisms, authentication credentials, and permission scopes carefully. Understand all granted tool capabilities, review restrictions, and follow documented revocation procedures using the supplied connection configuration reference card details.
What You’ll Learn in This Chapter
-
stdio connects a local process
Recognize messages traveling through a launched process's standard streams.
The stdio transport exchanges protocol messages through a local process’s standard input and output streams. The host commonly launches that server process. Its filesystem and network reach depend on operating-system permissions and any sandboxing. Local transport does not by itself make the program trustworthy or isolate its access.
-
Streamable HTTP reaches an endpoint
Recognize a network transport for MCP messages.
Streamable HTTP transmits MCP requests to remote server endpoints over standard web protocols. Network reachability alone does not prove compatibility; clients must authenticate properly and negotiate protocol versions successfully to exchange data.
-
Streaming is delivery, not a separate capability
Separate result delivery from what the operation does.
Streaming delivers response chunks incrementally rather than delaying until full completion. While this provides responsive real-time feedback, intermediate progress status notifications must always be distinguished from definitive final execution results.
-
Authentication and authorization differ
Separate identity from allowed operations.
Authentication establishes an identity or credential; authorization determines permitted access. A valid identity may lack permission for one operation. Failures can also involve expired or unsuitable credentials, so inspect the actual response. Successful sign-in does not prove every subsequent request has the required identity and scope.
-
OAuth can delegate limited access
Explain scoped authorization without sharing an account password with the agent.
OAuth supports delegated authorization, allowing a client to obtain limited access without receiving the user’s service password. The actual flow and scopes depend on the integration. Read the requested access and use the legitimate authorization surface. An access token is still a credential that must be protected.
-
Tokens have an intended recipient
Recognize why a token for one service should not be forwarded indiscriminately.
Access tokens are issued for particular recipients and permissions. Servers should validate that a token is intended for them instead of accepting arbitrary tokens from another service. Audience and scope are different checks. Narrow, correctly validated grants reduce unintended access across connected systems.
-
Disconnecting and revoking differ
Identify local configuration removal and provider-side access revocation.
Disconnecting removes or disables a connection in an application; revoking authorization withdraws a grant or credential at the relevant provider. Some products may combine these actions, but you should verify the documented behavior. Confirm access removal where it is enforced rather than assuming a deleted interface entry settles it.
-
Read a connection card
Choose the transport, identify where credentials are used and explain one allowed action, one denied action and how to revoke access.
-
Explain an MCP exchange
Trace a fictional notes integration from host to server and back, using a declared protocol version.