{"version":"2.1.317","anchor":"gmail-entry-not-filled-refusal-reason-added-to-mcp-file-refe","canonical_anchor":"gmail-entry-not-filled-refusal-reason-added-to-mcp-file-refe","heading":"A new Gmail reason for refusing to fill in a file reference","tier":"internal","area":"Connectors","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/gmail-entry-not-filled-refusal-reason-added-to-mcp-file-refe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### A new Gmail reason for refusing to fill in a file reference\n\nWhen an MCP file reference is refused, one possible reason is now that a Gmail entry was not filled in at that point\n\n**Unclear.** Whether the Gmail check is active for anyone is not shown.\n\n**What**\n\nMCP servers are add-ons that give Claude extra tools. When Claude Code refuses to fill in a file reference for one of them, there is now a third possible reason: a Gmail entry was not filled in at that point. Before, the only reasons were about Drive files in the desktop app.\n\n**Why**\n\nIt shows the check on file references reaching Gmail as well as Drive.\n\n- Area: Connectors\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}