MT mcp 连接不了

mkcs · 发表在 2026-7-26 09:12:03

本帖最后由 mkcs 于 2026-7-26 09:13 编辑

用本地llama.cpp离线模型加了mcp server地址，但连接不了mt管理器，该怎样解决?

09:06:54
Creating transport for http://192.168.1.2:8787/mcp
09:06:54
Transport ready (streamable_http)
09:06:54
Sending initialize request...
09:06:54
HTTP POST http://192.168.1.2:8787/mcp
details
{
  "serverName": "bcf37bf6-be5e-4cfa-93f3-6df7e67e7d4b",
  "request": {
"url": "http://192.168.1.2:8787/mcp",
"method": "POST",
"headers": {
   "accept": "application/json, text/event-stream",
   "content-type": "application/json"
},
"body": {
   "kind": "string",
   "size": 189
},
"jsonRpcMethods": [
   "initialize"
]
  }
}
09:06:54
HTTP POST http://192.168.1.2:8787/mcp failed: Failed to fetch (check CORS?)
details
{
  "serverName": "bcf37bf6-be5e-4cfa-93f3-6df7e67e7d4b",
  "request": {
"url": "http://192.168.1.2:8787/mcp",
"method": "POST",
"headers": {
   "accept": "application/json, text/event-stream",
   "content-type": "application/json"
},
"body": {
   "kind": "string",
   "size": 189
},
"jsonRpcMethods": [
   "initialize"
]
  },
  "error": {
"name": "TypeError",
"message": "Failed to fetch",
"stack": "TypeError: Failed to fetch\n at window.fetch (http://127.0.0.1:8080/_app/immutable/bundle.Cv7hLaBr.js:3:13157)\n at window.fetch (chrome-extension://odphnbhiddhdpoccbialllejaajemdio/scripts/inspector.js:7:3144)\n at fetch (http://127.0.0.1:8080/_app/immutable/bundle.Cv7hLaBr.js:155:2661)\n at cEe.send (http://127.0.0.1:8080/_app/immutable/bundle.Cv7hLaBr.js:153:5791)"
  },
  "browser": {
"location": "http://127.0.0.1:8080/#/mcp-servers",
"origin": "http://127.0.0.1:8080",
"protocol": "http:",
"isSecureContext": true,
"targetOrigin": "http://192.168.1.2:8787",
"targetProtocol": "http:",
"sameOrigin": false,
"useProxy": false
  },
  "hints": [
"This is a cross-origin browser request. If the server is reachable from curl or Node but not from the browser, missing CORS headers are the most likely cause.",
"\"Failed to fetch\" is a browser-level network failure. Common causes are CORS rejection, mixed-content blocking, certificate/TLS errors, DNS failures, or nothing listening on the target port."
  ],
  "durationMs": 134
}
09:06:54
Protocol error: Failed to fetch
details
09:06:54
Connection failed during initialize: Failed to fetch
details
{
  "error": {
"name": "TypeError",
"message": "Failed to fetch",
"stack": "TypeError: Failed to fetch\n at window.fetch (http://127.0.0.1:8080/_app/immutable/bundle.Cv7hLaBr.js:3:13157)\n at window.fetch (chrome-extension://odphnbhiddhdpoccbialllejaajemdio/scripts/inspector.js:7:3144)\n at fetch (http://127.0.0.1:8080/_app/immutable/bundle.Cv7hLaBr.js:155:2661)\n at cEe.send (http://127.0.0.1:8080/_app/immutable/bundle.Cv7hLaBr.js:153:5791)"
  },
  "config": {
"serverName": "bcf37bf6-be5e-4cfa-93f3-6df7e67e7d4b",
"configuredUrl": "http://192.168.1.2:8787/mcp",
"effectiveUrl": "http://192.168.1.2:8787/mcp",
"transportType": "streamable_http",
"useProxy": false,
"headers": {}
  },
  "browser": {
"location": "http://127.0.0.1:8080/#/mcp-servers",
"origin": "http://127.0.0.1:8080",
"protocol": "http:",
"isSecureContext": true,
"targetOrigin": "http://192.168.1.2:8787",
"targetProtocol": "http:",
"sameOrigin": false,
"useProxy": false
  },
  "hints": [
"This is a cross-origin browser request. If the server is reachable from curl or Node but not from the browser, missing CORS headers are the most likely cause.",
"\"Failed to fetch\" is a browser-level network failure. Common causes are CORS rejection, mixed-content blocking, certificate/TLS errors, DNS failures, or nothing listening on the target port."
  ]
}