Add http header suggestion #995
stone955
started this conversation in
Ideas - Transports
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
At present, there are a large number of REST APIs within enterprises that can and are required to be directly converted into MCP Tools for LLM use. Most of these REST APIs use service grids for microservice governance. The existing JSONRPC protocol forces the Proxy (such as Envoy) to parse the request body before routing forwarding, which will undoubtedly affect the performance of the Proxy.
Therefore it is recommended to add the following HTTP Header so that the routing path can be inferred without inspecting the HTTP request body when serving routes. Please use some standard headers to allow existing standard tools/routes to work without changes.
Recommended HTTP Headers:
1.MCP-Method
2.MCP-Tools-Call-Name
Beta Was this translation helpful? Give feedback.
All reactions