HAWKXDEV WORKSPACE MCP

OWNER-OPERATED INFRASTRUCTURE

Five services.
Five trust boundaries.

Hawkx Workspace MCP is a self-hosted bridge between an owner's MCP clients and one Google Workspace account. Each service keeps its own scopes, credentials, OAuth state, and runtime boundary.

View the boundary map Read the privacy policy
  1. 01GmailMail workflows
  2. 02CalendarEvents and availability
  3. 03DriveFiles and exports
  4. 04SheetsRanges and structure
  5. 05DocsTabs and structured text

SECURITY MODEL

Access is separated before a request reaches Google.

PROCESS

Independent runtimes

A failure in one service does not make the other four part of the same process or credential boundary.

AUTHORIZATION

Minimum service scopes

Each Google grant contains only the scopes required by that service. A Gmail token is not a Drive token.

CONTROL

Owner-directed operations

Google data is accessed only when the owner invokes a tool through an authorized MCP client.

PLAIN LANGUAGE

No advertising profile. No data resale. No shared master credential.

Tool results are returned to the MCP client that requested them. Google tokens remain inside the owner-controlled service environment.