{"version":"2.1.317","anchor":"mcp-oauth-callback-url-errors-are-logged-instead-of-returned","canonical_anchor":"mcp-oauth-callback-url-errors-are-logged-instead-of-returned","heading":"MCP sign-in failures after a pasted callback link are logged in full","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/mcp-oauth-callback-url-errors-are-logged-instead-of-returned","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### MCP sign-in failures after a pasted callback link are logged in full\n\nA failed MCP sign-in from a callback link now logs the full error, and the program that asked gets either a generic message or the full text\n\n**What**\n\nSome MCP servers, separate programs that give Claude Code extra tools, ask you to sign in through OAuth, a standard way of granting access through a web page. That page ends by sending you to a callback link, which can be pasted back so sign-in can finish.\n\nWhen sign-in fails at that point, Claude Code now writes the full error to its log. What it sends back to the program that asked, such as an app built on the Claude Agent SDK, now depends on a check:\n\n- When the check applies, the reply is only \"OAuth authentication failed\".\n\n- Otherwise, the reply is the full error text.\n\nBefore, the error always went through a step that removed sensitive parts before it was sent.\n\n**Why**\n\nPrograms that drive Claude Code may now see either a short generic message or the full error, and the full detail is always in the log.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}