Skip to content

[Bug] MCP server 中有多个 tool的是 clientId 获取的是 tool name,但是 clientMap 存的是 severname,到时多 tool 不可用 #6388

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

Open
ty1919 opened this issue Mar 18, 2025 · 2 comments
Labels
bug Something isn't working planned planned feature, will support in the future

Comments

@ty1919
Copy link

ty1919 commented Mar 18, 2025

📦 Deployment Method

Other

📌 Version

main

💻 Operating System

Ubuntu

📌 System Version

main branch

🌐 Browser

Chrome

📌 Browser Version

chome

🐛 Bug Description

MCP Actions] Failed to execute request for [get_device_users]: Error: Client xxx not found
Error: Client get_device_users not found
at E (/home/ubuntu/NextChat/.next/server/app/page.js:312:19387)
at i (/home/ubuntu/NextChat/.next/server/app/page.js:1:29687)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async /home/ubuntu/NextChat/node_modules/next/dist/compiled/next-server/app-page

📷 Recurrence Steps

No response

🚦 Expected Behavior

No response

📝 Additional Information

No response

@ty1919 ty1919 added the bug Something isn't working label Mar 18, 2025
@Issues-translate-bot
Copy link

Bot detected the issue body's language is not English, translate it automatically.


Title: [Bug] There are multiple tools in MCP server clientId. The tool name is obtained, but the clientMap stores severname. Many tools are not available at that time.

@Leizhenpeng Leizhenpeng added the planned planned feature, will support in the future label Apr 7, 2025
@lemonrains
Copy link

Same issue here, will get below error
[MCP Actions] Failed to execute request for [clientId]: Error: Client clientId not found Error: Client clientId not found at E (/app/.next/server/app/page.js:306:19284) at i (/app/.next/server/app/page.js:1:29631) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async /app/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:16:406 at async rm (/app/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:15:6342) at async rq (/app/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:18:1249) at async doRender (/app/node_modules/next/dist/server/base-server.js:1395:30) at async cacheEntry.responseCache.get.routeKind (/app/node_modules/next/dist/server/base-server.js:1556:28) at async NextNodeServer.renderToResponseWithComponentsImpl (/app/node_modules/next/dist/server/base-server.js:1464:28) at async NextNodeServer.renderPageComponent (/app/node_modules/next/dist/server/base-server.js:1861:24)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working planned planned feature, will support in the future
Projects
None yet
Development

No branches or pull requests

4 participants