Google Calendar, Gmail, Tasks, Drive, Contacts, Forms, Docs & Sheets MCP server for Pi.
36 tools, single binary, zero runtime deps. Login once, manage everything from your agent.
Requirements
pi-mcp-adapter — provides the command that Pi's core doesn't ship.
Install it first:
Google Calendar, Gmail, Tasks, Drive & Contacts MCP server for Pi. 26 tools, single binary, OAuth login.
ดาว
6
เครื่องมือ
—
อัปไทม์
—
/mcp
pi install npm:pi-mcp-adapter
Quick Install
pi install npm:pi-google-services
pi-google-services setup
# Restart Pi session, then:
# "show my events", "read my inbox", "create a meeting with Meet"
If npm's allowScripts blocked the postinstall (Pi's default), the binary is
installed automatically on your next Pi session start — the extension
self-heals. You can also run it manually at any time:
Pass "withMeet": true to create-event to auto-generate a Google Meet link.
Forms (5)
Tool
Description
create-form
Create empty form (then add sections/questions)
add-form-section
Add section header (title + description)
add-form-question
Add free-text or choice (RADIO/CHECKBOX/DROP_DOWN) question
get-form
Show form structure + responder link
list-responses
List submitted responses
The Forms API creates/reads forms and reads responses — it cannot submit
responses as a user. Adding Forms introduced new OAuth scopes (forms.body,
forms.responses.readonly): re-run pi-google-services login after updating.
Docs (3)
Tool
Description
get-doc
Read Doc as plain text (paragraphs + tables)
create-doc
Create empty Doc
append-to-doc
Append text at end of Doc
Scope: documents. Re-login required after updating.
Sheets (2, read-only)
Tool
Description
list-sheets
List tab names
read-sheet
Read values (A1 notation, default A1:Z100)
Scope: spreadsheets.readonly. Write access deliberately excluded. Re-login required after updating.
No secrets live in this repository. The OAuth client ID is baked into the
release binary by CI (via ldflags, see internal/auth/embedded.go) from
the GOOGLE_OAUTH_CREDENTIALS_JSON secret. install.js only installs the
binary and wires the Pi MCP config — it downloads no credentials.
Transparency & Security
Open Source, Auditable Code
This entire project is open source. Every line of code can be reviewed,
audited, and verified. The Go binary is built from this source in
GitHub Actions with provenance attestation — you can verify the build
matches the published source.
How OAuth Works
pi-google-services uses OAuth 2.0 with PKCE (Proof Key for Code
Exchange), the industry standard for desktop applications:
You run login or setup
Your browser opens to Google's consent screen
You see exactly what permissions are being requested (calendar,
email, tasks, drive, contacts, forms, docs, sheets)
You authorize with your Google account
A token is saved locally on your machine (~/.config/pi-google-services/)
The token never leaves your machine — all API calls go directly
from your binary to Google
About the Client ID
The release binary ships with a pre-registered Google Cloud OAuth client ID
baked in at build time by CI. This is not a secret — it's the same
mechanism used by every app that offers "Sign in with Google" (Todoist,
Notion, Fantastical, gcalcli, rclone, gh, etc.).
The client ID is publicly visible in the authorization URL and only
serves to identify which app is requesting access. The actual security
is in the OAuth consent screen where you decide what to share.
Why shared instead of "create your own project"? Registering a Google Cloud
project means enabling 8 APIs, configuring the consent screen, and creating
a Desktop OAuth client — ~10 minutes of friction before the first login.
The shared client removes that entirely: install, setup, authorize, done.
No Google Cloud account, no billing, no JSON files to juggle.
Prefer your own project? Set GOOGLE_OAUTH_CREDENTIALS to the path of your
credentials.json (or place it at ~/.config/pi-google-services/). Your
own credentials always take precedence over the baked-in client.
Known limits of the shared client (by design, not bugs):
The app is unverified, so Google shows a one-time warning screen.
Click "Continue" to authorize.
Unverified apps are capped at 100 users total.
API quota is shared across all users of the client.
If Google ever suspends the project, auth breaks for everyone at once —
with your own client ID that risk is yours alone.
Use Your Own Google Cloud Project
If setup fails with "This app requested access to sensitive information
and is blocked" (the shared client hit its 100-user cap or was suspended),
or you simply prefer not to depend on the shared client, create your own
OAuth client. It is free and takes ~10 minutes:
APIs & Services → Library: enable these 8 APIs:
Google Calendar, Gmail, Google Tasks, Google Drive, People (contacts),
Google Forms, Google Docs and Google Sheets.
APIs & Services → OAuth consent screen: choose External, fill in
the app name and your email, and leave it in Testing mode.
Under Test users, add your own Google account — without this, Google
blocks the login.
APIs & Services → Credentials → Create credentials → OAuth client ID:
choose application type Desktop app, then Download JSON.
Save the file as ~/.config/pi-google-services/credentials.json, or point
to it explicitly:
Run pi-google-services setup (or login) again and authorize.
Your credentials take precedence over the baked-in client. In Testing mode
Google expires refresh tokens after 7 days; to avoid re-logging weekly, set
the consent screen's publishing status to In production (it stays
unverified, which is fine for personal use).
Why Google Shows "This app is not verified"
When you run login or setup, Google shows a warning screen saying
the app is not verified. This is normal and safe.
Google's verification process requires a registered domain, a formal
brand review, and proof of ownership — it's designed for public web
apps with a business behind them, not open-source CLI tools.
The warning appears once per user. Click "Continue" to authorize.
Your data goes directly from your machine to Google — no intermediate
servers, no tracking, no telemetry.
This is an open-source project built for utility, not monetization.
Domain registration and Google verification are not a priority.
Many popular CLI tools for Google services (like gcalcli) are also
unverified. This does not affect security.
Credential Storage
What
Where
OAuth client ID
Baked into the release binary by CI (public by design); overridable via GOOGLE_OAUTH_CREDENTIALS or local credentials.json
Local builds without credentials.json in the repo root (and without the
release ldflags) require your own client: set GOOGLE_OAUTH_CREDENTIALS
to your credentials.json path. Release CI bakes the shared public client
in via -X github.com/sombi/pi-google-services/internal/auth.embeddedClientID=...
so end users never touch this.