{"version":"2.1.265","anchor":"ambient-credential-detection-updated-for-a-new-apiartifact","canonical_anchor":"ambient-credential-detection-updated-for-a-new-apiartifact","heading":"Ambient-credential detection updated for a new \/api\/artifacts\/mcp endpoint","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/ambient-credential-detection-updated-for-a-new-apiartifact","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Ambient-credential detection updated for a new \/api\/artifacts\/mcp endpoint\n\nAmbient-credential detection for MCP now special-cases a new \/api\/artifacts\/mcp endpoint\n\n**What**\n\nThe internal helper that detects ambient credentials and OAuth needs for MCP server connections (replacing an older helper) now treats URLs under the `\/api\/artifacts\/mcp` path differently from other MCP URLs. Related plumbing (`artifactsMcpEntries`, `artifactsMcpEdgeEntries`) and new OAuth scope constants for the artifacts MCP server were added, split into management, data, endpoints, and comments scopes.\n\n**Why**\n\nThis lays groundwork for an artifacts-specific MCP server to be authenticated and scoped separately from other MCP connections, with finer-grained permission scopes.\n\n- Area: MCP\n- Names: `\/api\/artifacts\/mcp`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}