Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Built-in Google Drive MCP feels like forced opt-in / Microsoft-style assumption [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#45413•Fetched 2026-04-09 08:06:00
View on GitHub
Comments
2
Participants
2
Timeline
5
Reactions
0
Author
rriley23rriley23
Participants
github-actions[bot]github-actions[bot]rriley23rriley23
Timeline (top)
commented ×2labeled ×2closed ×1
RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • This is a single feature request (not multiple features)

Problem Statement

Claude Code ships with a Google Drive MCP (claude.ai Google Drive -> https://drivemcp.googleapis.com/mcp/v1) pre-registered with no user consent and no way to remove it via claude mcp remove. It shows up in claude mcp list as "Needs authentication" on a fresh install.

While it's technically dormant until authenticated, discovering an unknown MCP server pointed at a Google endpoint — that you never asked for — reads as malware-adjacent. It's the kind of "we assumed you'd want this" behavior that erodes trust. Microsoft got a lot of grief for exactly this pattern.

Proposed Solution

Suggestion: either don't pre-register it at all (true opt-in), or at minimum make claude mcp remove work on built-ins so users have agency over their own MCP surface area.

Alternative Solutions

Suggestion: either don't pre-register it at all (true opt-in), or at minimum make claude mcp remove work on built-ins so users have agency over their own MCP surface area.

Priority

Low - Nice to have

Feature Category

MCP server integration

Use Case Example

No response

Additional Context

No response

extent analysis

TL;DR

Modify the claude mcp remove command to allow removal of pre-registered MCP servers, including the Google Drive MCP, to give users control over their MCP surface area.

Guidance

  • Review the implementation of claude mcp remove to identify why it currently fails to remove built-in MCP servers like the Google Drive MCP.
  • Consider adding a flag or option to claude mcp remove to specifically target built-in or pre-registered MCP servers.
  • Evaluate the feasibility of implementing a true opt-in approach, where the Google Drive MCP is not pre-registered by default.
  • Assess the potential impact on user experience and trust if the current behavior is not changed.

Example

No code snippet is provided due to lack of specific implementation details in the issue.

Notes

The solution may require changes to the claude command-line tool and its underlying architecture. The priority of the issue is marked as "Low - Nice to have", which may influence the timing and resources allocated to addressing this issue.

Recommendation

Apply a workaround by modifying the claude mcp remove command to allow removal of pre-registered MCP servers, as this approach balances user agency with the potential complexity of implementing a true opt-in model.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#api#serialization error#model compatibility#GPU setup#container setup

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING