{"version":"2.1.257","anchor":"mcp-clientserver-errors-now-attributed-to-originating-confi","canonical_anchor":"mcp-clientserver-errors-now-attributed-to-originating-confi","heading":"MCP client\/server errors now attributed to originating config","tier":"notice","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/mcp-clientserver-errors-now-attributed-to-originating-confi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### MCP client\/server errors now attributed to originating config\n\nMCP connect, tool-call and reconnect errors now name the server config they came from, useful with several servers running.\n\nMCP connect, tool-call, reconnect, and get-prompt failure paths now format errors with a new `Ii(error, config)` helper that includes the server config in the resulting message, improving error attribution (for example in \"Error during reconnection:\" and \"Error running command\") when running multiple MCP servers.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}