APIM MCP Server Fails to Handle Both URL Parameters and JSON Body in the Same Request
- Dominant language
- No language data
- Stars
- 28
- Forks
- 75
- Avg merge
- 9d 2h
- Merged PRs (30d)
- 3
Description
We are experiencing an issue with the MCP server where it does not handle both URL parameters and a JSON body simultaneously in requests. This issue occurs specifically when the request has the header:
**Observations:**
-> When a request is sent with Content-Type: application/json and includes a JSON body, URL parameters like cartId are not visible in the MCP Inspector.
-> If the JSON body is removed, the URL parameters like cartId is correctly recognized.
-> Based on inspection using MCP Inspector, this behavior confirms that MCP only handles one input source at a time (either URL parameters or JSON body, but not both).
**Impact:**
This prevents sending valid requests that include both a required URL parameter and a JSON body payload. As a result, requests fail or behave incorrectly due to missing required parameters.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.