{"version":"2.1.299","anchor":"mcp-oauth-and-artifact-traffic-use-a-shared-fetch-wrapper","canonical_anchor":"mcp-oauth-and-artifact-traffic-use-a-shared-fetch-wrapper","heading":"MCP sign-in uses a network connection for each server","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/mcp-oauth-and-artifact-traffic-use-a-shared-fetch-wrapper","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### MCP sign-in uses a network connection for each server\n\nMCP sign-in steps now use a separate network function per server, and artifact requests record which route they took\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools, and some require you to sign in. Finding the server's sign-in details, refreshing a sign-in and completing one now use a network function set up for each server, instead of one shared for all.\n\nSeparately, requests for artifacts now record which route they took in usage data: MCP, HTTP fallback, HTTP or relay.\n\n**Why**\n\nArtifact requests can now travel through MCP with a fallback to plain HTTP.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}