Personal Workspace Connector
A self-hosted tool that lets one person use several of their own Google accounts from a local AI assistant, without swapping between them.
What this application does
Personal Workspace Connector is a small program that runs on its owner's own computer. It starts one local server for each Google account the owner wants to use, and exposes those accounts to a locally installed AI assistant through the Model Context Protocol (MCP).
The problem it solves is mundane: most assistant integrations handle one Google account at a time, and connecting a second one disconnects the first. Running a separate local server per account lets the owner keep a personal mailbox and a work mailbox connected at the same time and refer to each one distinctly.
In practice the application lets its owner:
- read, search, draft, send and label email in their own Gmail accounts;
- read and manage events in their own Google Calendar;
- optionally read or create files in their own Google Drive, and use other Google Workspace APIs, if the owner enables those tools;
- read the basic profile (name, email address) of the connected account, so that each local server can show which mailbox it is attached to.
Who it is for
This is a personal-use application. It is installed and operated by a single individual — the owner of the Google Cloud project behind it — to access accounts that belong to that same individual. It is not a product, it is not distributed or sold, it has no user accounts, no sign-up, and no shared installation.
There is nothing to download here. This website exists to describe the application and publish its privacy policy, as required for an OAuth client that requests access to Google user data. The application itself is a local installation on the owner's machine.
How it works
- The owner creates an OAuth client in their own Google Cloud project and enables the Google APIs they intend to use.
- They configure one local server instance per Google account, each with its own credentials directory and its own port, on their own computer.
- The first time an account is used, Google's standard consent screen opens in the browser. The owner signs in with that account and grants access.
- Google returns an access token and a refresh token. Those tokens are written to a directory on the owner's computer and used from there.
- From then on, the local server calls Google's APIs directly on the owner's behalf. No intermediate service is involved.
Where the data goes
The application has no backend of its own. There is no server operated by the developer, no database, no analytics, no logging service and no third party that receives Google user data. The local server talks to Google's APIs, and to the locally installed AI assistant that requested the data. Full detail, including the exact OAuth scopes involved and the Limited Use commitment, is in the privacy policy.
Built on open source
The connector is an installation of google_workspace_mcp, an independent open-source project released under the MIT licence, run in its self-hosted single-user mode. The OAuth client, the Google Cloud project and this website belong to the individual operating the installation.
Contact
Questions about this application or about the handling of data can be raised at github.com/fed3c3sa/fed3c3sa.github.io/issues.
- Application name Personal Workspace Connector
- Type Desktop / installed application, self-hosted
- Distribution None — single-operator personal use
- Home page fed3c3sa.github.io
- Privacy policy fed3c3sa.github.io/privacy.html
- Terms of service fed3c3sa.github.io/terms.html