mcp-error-formatter

Hey thanks for the comment, the work from https://github.com/bjoaquinc/mcp-error-formatter is great. I will definitely put some version of this into one of the next releases. Just opened an issue mentioning this thread. The problem with the package above is that it is server side, and I think it should be. Server is the one that knows (has responsibility to know) if a tool is retryable and has informations about the error, and fairly so. I see though how some sort of improved error formatting could be introduced in the client as well, but it shouldn't contain any logic about the error, rather format the error in the best way possible (in the direction in which it is best understandable by LLMs).

Hi HN! Author here. When an LLM-powered tool call blows up, the model usually sees an opaque stack trace. It can’t tell whether to retry, give up, or suggest a fix, so users get “Something went wrong” or infinite retry loops. Cursor’s editor solved this by wrapping errors in a small, structured JSON envelope: ``` Request ID: c90e… {"error":"ERROR_USER_ABORTED_REQUEST", "details":{"title":"User aborted request.", "isRetryable":false}, "isExpected":true} ``` That single structure lets the agent reason correctly (“don’t retry; the user cancelled”). I wanted the same behavior in standalone MCP servers and LangChain tools, so I extracted it into a tiny package: ``` npm i @bjoaquinc/mcp-error-formatter ``` ```ts import { formatMCPError } from "@bjoaquinc/mcp-error-formatter"; export async function githubTool(args) { try { co