2 ms·
Up to you, but there's actually a formal logging pathway[1] in MCP that has the potential to put this message somewhere that either of the two consumers[2] of y
by mdaniel 2y ago
Up to you, but there's actually a formal logging pathway[1] in MCP that has the potential to put this message somewhere that either of the two consumers[2] of your service could see it https://github.com/hyperdrive-eng/mcp-nodejs-debugger/blob/v0.2.1/src/mcp-server.js#L73 https://github.com/hyperdrive-eng/mcp-nodejs-debugger/blob/v...
1: https://spec.modelcontextprotocol.io/specification/2024-11-05/server/utilities/logging/ https://spec.modelcontextprotocol.io/specification/2024-11-0...
2: the person, and (while I don't have evidence of it) I also can't think why the LLM couldn't see the message, either
- arthurgousset 2y agoOh neat, thanks so much for sharing. I was getting MCP client errors when simply using `console.error`. Sending log message from the MCP server to the MCP client via the logging capability makes a ton of sense! ``` { "capabilities": { "logging": {} } } ```