Is MCP just an API Abstraction?#

William Collins — Director, Technical Evangelism

• Why: MCP is the emerging protocol substrate for agentic systems interacting with infrastructure — directly relevant to the PM's workload/agentic identity and protocol interests (how agents authenticate, discover capabilities, and get scoped access is the same problem class as OAuth/OIDC/SPIFFE, one layer up). This is the sharpest protocol-level dissection in the program.
• What: A point-by-point architectural comparison of MCP against REST APIs, concluding MCP is not merely an API wrapper: REST is stateless, URL-routed, and built for human developers; MCP is a stateful, session-based JSON-RPC protocol with dynamic capability discovery, built for AI models to interact with external systems safely. The framing of the N×M integration problem (N models × M tools = N×M custom integrations, with quadratic maintenance and vendor lock-in) collapsing to N+M (N clients + M servers) is the clearest articulation of why the protocol matters.
• How: MCP's three primitives — Resources (read data/context), Prompts (templates), Tools (execute actions) — plus context (semantically-tagged data loaded into the model's window) and logs (diagnostics pushed back). Decorators auto-generate tool schemas from docstrings, eliminating the glue code and agent-loop plumbing of hand-rolled function calling. The talk's best design guidance is intention-based tool design (run_compliance_check(device_group, policy) rather than endpoint-mapped getters), role-based capability filtering via tags to prevent decision paralysis, and MCP gateway patterns as evolution paths. It also cleanly separates intelligence (understanding intent) from scale (concurrency, multi-tenancy).
• Where applicable: Protocol-general, vendor-neutral, with working code (github.com/wcollins/talks). Caveat: the speaker is a technical evangelist, but the content is architecture analysis, not a product pitch. Directly applicable to anyone designing agent-to-infrastructure access — and the role-based tool-exposure idea is effectively least-privilege scoping for agents, a live question in agentic identity.