Enterprise Google Drive connector customization needed

Preflight Checklist

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

Problem Statement

We have FedRAMP compliance requirements. This currently makes it impossible to use Claude's Google Drive connector, because there's no way to isolate connector access within a FedRAMP boundary or customize connector behavior per user/org policy. Our sales and customer success reps tell us there is no customization available with the current connector.

The practical result: we're routing work to competitors for tasks that involve documents stored in Google Drive. This is a retention and functionality concern that prevents us from migrating users.

What would help:

• Connector-level data residency controls for enterprise orgs
• Per-org or per-user connector policy configuration
• FedRAMP-compatible connector options

Proposed Solution

The MCP architecture you've already built actually solves this cleanly — enterprise customers can self-host or
configure MCP servers within their own security boundary, which means connector access never leaves the org's environment. Extending this to first-party connectors (Google Drive, etc.) with org-level policy controls would let customers like us use them without violating FedRAMP or other compliance/security requirements. You'd essentially be giving enterprise admins the same configurability that MCP already provides for custom integrations, applied to your native connectors.

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

MCP server integration

Use Case Example

Additional Context

_No response_