Add an explanation for implementing MCP server hosting using Higress #1041
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Adds Higress MCP Server Hosting to Additional resources. It is a solution that allows running MCP servers on API Gateway(based on Envoy)
Motivation and Context
MCP makes APIs more AI-friendly, and the management of MCP servers shares many similarities with traditional APIs, such as invocation observation of tools calls, rate limiting, authentication, and authorization. Higress offers a way to develop WASM plugins, extending the capabilities of MCP servers on the API gateway. This approach simplifies the hosting of MCP servers and allows for the reuse of governance capabilities that have been established in the era of traditional APIs.
How Has This Been Tested?
Internal testing has been completed. About to be widely promoted and used on Alibaba Cloud
Breaking Changes
None.
Types of changes
Checklist
Additional context