Hey All,
Are you looking to easily enable your REST APIs for agent-based interactions, but don’t want the hassle of building a new server from scratch? In this video, I demonstrate a powerful method to “MCPify” your existing REST APIs using the apigee-go-gen tool.
This process allows you to take an OpenAPI description and convert it into an Apigee API proxy that behaves just like a native MCP (Model-Contex-Protocol) server. This means your agents can interact with your REST APIs using the MCP protocol, simplifying integration and expanding possibilities.
I have organized the video into chapters, where I give a comprehensive walkthrough, covering everything from initial setup to advanced security features. You’ll learn how to:
- Generate an MCP Proxy from an OpenAPI Description: See how a simple command transforms your API specification into a deployable Apigee proxy bundle. (Watch from 2:07)
- Deploy and Test: Witness the deployment of the generated proxy to Apigee and learn how to test it using the MCP Inspector and Gemini CLI. (Watch from 3:30, 5:06, 10:00)
- Implement Tool Filtering: Understand how to control which API operations (tools) are exposed to your agents, crucial for managing complexity. (Watch from 13:07)
- Secure Your MCP Server with Apigee Governance: Discover how to add authentication (API Keys) and authorization (product-based access control) to your newly MCPified API. (Watch from 15:50)
- Integrate with OAuth: Learn how to configure your MCP server to work seamlessly with OAuth for robust user authentication. (Watch from 25:35)
This is a must-watch for anyone working with Apigee and looking to extend their REST APIs for agent-based systems without extensive re-engineering. It’s a clear, step-by-step guide that showcases the power and flexibility of Apigee.
Watch the full video here: apigee-go-gen: Convert any REST API into an MCP server with Apigee
