{"version":"2.1.227","anchor":"mcp-credential-and-cache-locations-are-now-parameters","canonical_anchor":"mcp-credential-and-cache-locations-are-now-parameters","heading":"MCP credential and cache locations are now parameters","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/mcp-credential-and-cache-locations-are-now-parameters","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### MCP credential and cache locations are now parameters\n\nMCP credentials and the discovery cache are now passed in rather than read from globals.\n\n**What**\n\nBoth MCP OAuth providers read credentials through an injectable store rather than a global, and the MCP discovery cache is described by a location record naming the user config directory and a `mcp-discovery-cache` folder instead of an in-process map. Behaviour is unchanged.\n\n**Evidence**\n\n`mcp-discovery-cache`\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}