Hi, I'm Rhea.
In development · Open source · MIT
Your Drive, within reach of your assistants.And no further.
RHEA connects Google Drive to MCP-compatible assistants through one dedicated folder. You run the instance, you approve each assistant, and every request is checked against the only folder it is allowed to reach.
01 · Overview
Four parts, one boundary.
The repository provides the workspace and the gateway source code. Each part can be read, run and audited on its own.
Web workspace
Browse, preview, download and organize the files inside the workspace folder, and review what each assistant has asked to change.
Source for Web workspaceRemote MCP gateway
A dedicated HTTPS endpoint where external assistants connect with OAuth. Every connection can be reviewed and revoked from the workspace.
Source for Remote MCP gatewayLocal MCP server
Reads allowlisted project documentation over stdio, for assistants that run next to the code.
Source for Local MCP serverAndroid prototype
An early look at local file intake and browsing, built and tested with sample files.
Source for Android prototype
02 · How a request travels
Every hop asks a question.
An assistant never talks to Google directly. Its request passes through checks it cannot skip, and the answer can only come from inside the RHEA folder.
- AssistantAllowlisted client with an exact callback URL
- MCP gatewayIts own OAuth grant; access tokens last five minutes at most
- Drive serviceOnly the drive.file scope; ancestry verified on the server
- RHEA folderThe one folder the app created in My Drive
03 · Boundaries
Access is narrow by design.
- One folder
- RHEA asks Google only for the drive.file scope and checks, for every file and folder it returns, that it really lives under the app-created RHEA folder.
- Separate permissions
- Reading is the default. Proposing changes and organizing files are separate permissions, and each must be approved explicitly for each assistant.
- Reviewed changes
- An assistant may propose a new folder, a rename, a move, a reversible trash or an upload destination. Nothing happens until you confirm it in the workspace.
- Revocable grants
- Each assistant has its own grant, which you can revoke at any time. Google tokens and workspace cookies are never handed to an assistant.
- Untrusted content
- Text read from files is treated as untrusted input, and every tool response is bounded in size.
- Your own instance
- You run the website, the hosting, the Google OAuth application and the MCP endpoint. The guides use Cloudflare Pages, Access, Workers and D1.
04 · Get started
Run your own instance.
Clients such as Claude, ChatGPT and Gemini CLI can connect over remote MCP, subject to each client's own plans and eligibility.
Deploy the workspace
Publish the web workspace to your own Pages project behind Cloudflare Access, and register your own Google OAuth client.
Web and Drive setupDeploy the gateway
Run the MCP gateway on its own HTTPS Worker, bind the same D1 database to both services and apply the migrations in order.
MCP gateway setupConnect, then authorize
Connect your Google account in the workspace, then register and authorize each assistant against your /mcp endpoint.
Assistant onboarding
Preview the interface locally · Node.js 24
git clone https://github.com/indiolibanes/RHEA.git
cd RHEA/apps/web
npm ci
npm test
npm run devThe Drive API, assistant grants and uploads need a deployment with Cloudflare Access and your own Google OAuth application.