{"version":"2.1.323","anchor":"mcp-server-release-hook-and-google-drivegmail-file-referenc","canonical_anchor":"mcp-server-release-hook-and-google-drivegmail-file-referenc","heading":"Google Drive and Gmail uploads can use file references instead of encoded file contents","tier":"notice","area":"Connectors","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/mcp-server-release-hook-and-google-drivegmail-file-referenc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Google Drive and Gmail uploads can use file references instead of encoded file contents\n\nClaude is now told to attach files to Google Drive and Gmail through a file reference rather than typing out the file's encoded contents\n\n**Unclear.** It is not clear which apps that run Claude Code supply the file references this depends on, so it may not apply in every setup.\n\n**What**\n\nClaude Code now gives Claude a note about uploading files through the Google Drive and Gmail connectors. A connector is an add-on that lets Claude act inside another service. When creating a file in Google Drive or adding a Gmail attachment, Claude must not type out the file as base64, a way of writing a file's raw contents as long runs of text. Instead it uses a file reference in the form `sha256:<hash>:<path>`. These references come from the app Claude Code is running inside, not from the connector.\n\nClaude Code can also now list and release MCP servers that a session is connected to. An MCP server is an outside program that gives Claude extra tools.\n\n**Why**\n\nEncoded file contents can be very large. Pointing at a file instead keeps uploads through these connectors small and avoids Claude having to reproduce a whole file as text.\n\n- Area: Connectors\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}