The interest in Model Context Protocol is sustained. Many people working in larger companies want to know - how can I control access to MCP Servers? How can I ensure consistency across my portfolio? Do I need an MCP Gateway? All the interest in MCP has led to an explosion of tactical products, MCP Managers, MCP Gateways, MCP registries... But the truth is MCP is just another kind of API, and the enterprise tools you know that are really good at managing other kinds of APIs are also good at managing MCP APIs. In this extended screencast, I talk about some of the issues and show a working example of an MCP Server being proxied by Apigee. Hit me up with questions. Source code for this example, including - MCP Server - Authorization server - API Proxies - deployment scripts - extensive README ...is here: