hermes - 💡(How to fix) Fix MCP Servers amap (http) — SSE discovery mechanism not supported [1 comments, 2 participants]

• 500 Internal Server Error for https://mcp.amap.com/mcp

TL;DR

Modify the hermes-agent MCP implementation to use the SSE-based discovery mechanism before connecting to the amap MCP server.

Guidance

• Update the tools/mcp_tool.py to first connect to the SSE endpoint (https://mcp.amap.com/sse?key=...) and retrieve the session endpoint.
• Use the returned session endpoint (/mcp/message?sessionId=xxx) for subsequent MCP communication.
• Verify the SSE endpoint returns the correct session information using a tool like curl.
• Consider implementing a fallback or retry mechanism in case of SSE connection failures.

Example

import requests

# Replace with your actual API key
key = "YOUR_KEY"

# Connect to SSE endpoint and retrieve session endpoint
sse_url = f"https://mcp.amap.com/sse?key={key}"
response = requests.get(sse_url, headers={"Accept": "text/event-stream"})

# Parse the session endpoint from the SSE response
session_endpoint = None
for line in response.text.splitlines():
    if line.startswith("data:"):
        session_endpoint = line.split(":")[1].strip()
        break

# Use the session endpoint for MCP communication
if session_endpoint:
    mcp_url = f"https://mcp.amap.com{session_endpoint}"
    # Proceed with MCP communication using the mcp_url

Notes

The provided example is a basic illustration and may require modifications to fit the actual implementation. Additionally, error handling and potential edge cases should be considered when integrating the SSE-based discovery mechanism.

Recommendation

Apply workaround by modifying the hermes-agent MCP implementation to use the SSE-based discovery mechanism, as the current implementation does not support this required feature.