getting error when connecting MCP tool?
{
"id": "log-155",
"level": 50,
"time": 1755993059136,
"timestamp": 1755993059136000000,
"severityText": "ERROR",
"severityNumber": 17,
"body": "MCP tool call failed",
"attributes": {
"category": "tool",
"callId": "8a15ff37-d0d0-4a75-ac86-c71bd0bb5aaf",
"orgId": "177d5905-5175-47fd-bc67-4e8d47b9ca38",
"error": "Failed to connect to MCP server"
}
}
This is the respones I found in the logs when trying to connect to my MCP endpoint using Streamable HTTP. I'm trying to decipher if by "failed to connect" they mean that there was some auth issue / issue when trying to use one of the endpoints on that server
or if it just failed to even connect at all altogether.
my server is running on port 3005 and has an endpoint for shttp at 3005/mcp, but I tried both and still got the error. No logs in my ec2 where it's hosted either which make me wonder if it even connected at all.
Anybody encounter this and know the correct setup or fix?
"id": "log-155",
"level": 50,
"time": 1755993059136,
"timestamp": 1755993059136000000,
"severityText": "ERROR",
"severityNumber": 17,
"body": "MCP tool call failed",
"attributes": {
"category": "tool",
"callId": "8a15ff37-d0d0-4a75-ac86-c71bd0bb5aaf",
"orgId": "177d5905-5175-47fd-bc67-4e8d47b9ca38",
"error": "Failed to connect to MCP server"
}
}
This is the respones I found in the logs when trying to connect to my MCP endpoint using Streamable HTTP. I'm trying to decipher if by "failed to connect" they mean that there was some auth issue / issue when trying to use one of the endpoints on that server
or if it just failed to even connect at all altogether.
my server is running on port 3005 and has an endpoint for shttp at 3005/mcp, but I tried both and still got the error. No logs in my ec2 where it's hosted either which make me wonder if it even connected at all.
Anybody encounter this and know the correct setup or fix?
