You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
A clear and concise description of what the bug is.
This PR (5a25fe3) was recently submitted and break our MCP server's usage with the Inspector. Instead of using the endpoint that was returned (e.g. http://127.0.0.1:5000/mcp?sessionId=123) from /sse endpoint, it updates the endpoint with /messages (http://127.0.0.1:5000/mcp/messages?sessionId=123. This rule was not clearly specified in the mcp docs/specs (only showed in an example).
To Reproduce
Steps to reproduce the behavior:
MCP server with /sse endpoint for GET and / endpoint for POST.
Expected behavior
A clear and concise description of what you expected to happen.
Client should use the endpoint received from GET.
Logs
If applicable, add logs to help explain your problem.
n/a
Additional context
Add any other context about the problem here.
If this is expected, it will be great to include it within the docs/specifications.
The text was updated successfully, but these errors were encountered:
Describe the bug
A clear and concise description of what the bug is.
This PR (5a25fe3) was recently submitted and break our MCP server's usage with the Inspector. Instead of using the endpoint that was returned (e.g.
http://127.0.0.1:5000/mcp?sessionId=123
) from/sse
endpoint, it updates the endpoint with/messages
(http://127.0.0.1:5000/mcp/messages?sessionId=123
. This rule was not clearly specified in the mcp docs/specs (only showed in an example).To Reproduce
Steps to reproduce the behavior:
/sse
endpoint for GET and/
endpoint for POST.Expected behavior
A clear and concise description of what you expected to happen.
Client should use the endpoint received from GET.
Logs
If applicable, add logs to help explain your problem.
n/a
Additional context
Add any other context about the problem here.
If this is expected, it will be great to include it within the docs/specifications.
The text was updated successfully, but these errors were encountered: