mcp修复

docs/project/integrations/superagent-mcp-client.example.json

@@ -3,13 +3,12 @@
   "mcpServers": {
     "fire-safety-ymd-spatial-readonly": {
       "transport": "http",
-      "protocolVersion": "2025-06-18",
       "url": "https://<fire-safety-server-domain>/mcp",
       "method": "POST",
       "headers": {
         "Authorization": "Bearer ${FIRE_SAFETY_MCP_AUTH_TOKEN}",
         "Content-Type": "application/json",
-        "Accept": "application/json"
+        "Accept": "application/json, text/event-stream"
       },
       "tools": {
         "allow": [
@@ -25,6 +24,7 @@
       },
       "runtimeNotes": {
         "authTokenSource": "Use a separate per-environment high-entropy secret; never reuse the SuperAgent Open API Key.",
+        "protocolCompatibility": "SuperAgent cannot configure protocolVersion here. The fire-safety-ymd server follows the proven th-hotel-simple-superagent compatibility profile: it does not use initialize.params.protocolVersion or MCP-Protocol-Version as version refusal gates and always returns protocolVersion 2025-06-18. This is a compatibility response, not support for arbitrary client versions or a latest-version target. Do not add a protocol-version or protocol-header setting.",
         "scopeSource": "The all or town-allowlist data scope is configured on the fire-safety-ymd server and is never supplied by tool arguments.",
         "safety": "Results are planning evidence only. Invalid source geometries are excluded, so results may be incomplete. Availability, passability, command-post suitability, live team positions and assembly sites require field confirmation."
       }