{"version":"2.1.323","anchor":"mcp-headershelper-trust-message-handles-a-session-that-has-m","canonical_anchor":"mcp-headershelper-trust-message-handles-a-session-that-has-m","heading":"Clearer message when an MCP header helper is skipped for lack of trust","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/mcp-headershelper-trust-message-handles-a-session-that-has-m","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Clearer message when an MCP header helper is skipped for lack of trust\n\nWhen headersHelper does not run because a folder is not trusted, the message now says which folder and how to fix it\n\n**What**\n\nA `headersHelper` is a command that supplies headers for connecting to an MCP server (an outside tool server). Claude Code only runs it in a folder you have marked as trusted. When it skips the command, the message used to say only that the workspace had no saved trust. It now explains more:\n\n- If the session has moved but still reads the `.mcp.json` of the folder it was launched in, the message says that folder has no saved trust and suggests setting `projects[...].hasTrustDialogAccepted`.\n\n- For your home directory, it says that trust there lasts only for the current session.\n\nThe folder the helper command runs in now also depends on where the server was set up.\n\n**Why**\n\nIf an MCP server's headers stop working after a session changes folder, the message now tells you which folder needs trust and what to set.\n\n- Area: MCP\n- Names: `headersHelper`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}