Skip to content

MCP services are divided into long-term and short-term when they are added #399

@SharkByte-Pray

Description

@SharkByte-Pray

I have an mcp service mcp/pdf-reader, docker runs, but this service does not support long-term running, it is one-time, and it will give an error when running:
Failed to connect: McpError: MCP error -32000: Connection closed
at Client._onclose (file:///app/node_modules/.pnpm/@modelcontextprotocol+sdk@1.20.2/node_modules/@modelcontextprotocol/sdk/dist/esm/shared/protocol.js:109:23)
at _transport.onclose (file:///app/node_modules/.pnpm/@modelcontextprotocol+sdk@1.20.2/node_modules/@modelcontextprotocol/sdk/dist/esm/shared/protocol.js:76:18)
at ChildProcess. (file:///app/node_modules/.pnpm/@modelcontextprotocol+sdk@1.20.2/node_modules/@modelcontextprotocol/sdk/dist/esm/client/stdio.js:95:77)
at ChildProcess.emit (node:events:519:28)
at maybeClose (node:internal/child_process:1101:16)
at ChildProcess._handle.onexit (node:internal/child_process:304:5)

In principle, the popularity of this feature request is not that high, but it is only a situation that I have encountered when I use it personally. Hope there is this feature, but it is not necessary, thanks

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions