{"version":"2.1.314","anchor":"mcp-drive-file-references-can-cover-multiple-files-with-new","canonical_anchor":"mcp-drive-file-references-can-cover-multiple-files-with-new","heading":"Drive file references through MCP can cover several files and remember approvals","tier":"notice","area":"Google Drive","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/mcp-drive-file-references-can-cover-multiple-files-with-new","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Drive file references through MCP can cover several files and remember approvals\n\nDrive file references through MCP now handle several files at once, remember which uploads you approved, and refuse clearly when no one can approve\n\n**Unclear.** Which setting turns this on, and so whether it is available to you, is not stated.\n\n**What**\n\nMCP (Model Context Protocol) is the way Claude Code connects to outside tools and services. When an MCP tool refers to files in Drive, Claude Code now handles a list of file references in one call. Before, it handled one reference per call.\n\nIt also changes how uploads are approved:\n\n- Approved uploads are recorded per account, so an approval is remembered.\n\n- A new refusal covers the case where there is nobody available to approve the upload.\n\nClaude Code also records whether file references are available. The whole behaviour sits behind a setting that is off unless it is switched on remotely.\n\n**Why**\n\nUploading Drive files through MCP needs fewer repeated approvals and fails with a clearer reason when approval is impossible.\n\n- Area: Google Drive\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}