-
Notifications
You must be signed in to change notification settings - Fork 366
java mcp message endpoint error #103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi, do you know if there is a workaround? Is this due to a misconfiguration on my part? (seeing this error on a call that worked yesterday) |
fixes java mcp message endpoint error modelcontextprotocol#103
|
I wonder if the InterruptedException is overly broad. Is it possible that a simple misconfiguration (like a port conflict) could be caught by this exception? Line 406 in 0069c97
|
Expected Behavior
The implementation should properly handle cases where
messageEndpoint
already contains a protocol and host to avoid incorrect concatenation.Current Behavior
Currently, the Java MCP SDK does not correctly handle
messageEndpoint
. Instead of properly resolving the full URL, it simply concatenatesmessageEndpoint
with the base URL as a raw string. This results in malformed URLs, such as: http://localhost/mcphttp://localhost/mcp/messageContext
mark3labs/mcp-go#76 (comment)
Here are the references:
https://github.com/modelcontextprotocol/java-sdk/releases/tag/v0.8.1
The text was updated successfully, but these errors were encountered: