Skip to content

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.

View the repository Read the setup guide

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.

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.

  1. AssistantAllowlisted client with an exact callback URL
  2. MCP gatewayIts own OAuth grant; access tokens last five minutes at most
  3. Drive serviceOnly the drive.file scope; ancestry verified on the server
  4. 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.

  1. 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 setup
  2. Deploy 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 setup
  3. Connect, 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 dev

The Drive API, assistant grants and uploads need a deployment with Cloudflare Access and your own Google OAuth application.