google-extras-mcp
Provides read-only access to Blogger, allowing agents to list blogs accessible to the account and list recent posts of a specific blog.
Provides read-only access to Google Classroom, allowing agents to list courses, announcements, and coursework (assignments and questions) within a course.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
google-extras-mcp
A read-only Model Context Protocol (MCP) server that extends the official Google Workspace MCP (gws) with three free APIs: Blogger, Google Books (My Library), and Google Classroom.
Why this exists
The official Google Workspace MCP (gws) covers 119 tools across Gmail, Google Drive, Calendar, Docs, Sheets, Slides, Forms, Tasks, Chat, Contacts, and Apps Script. However, it does not cover Blogger, Books, or Classroom.
Rather than widening the scope of the main gws credential — which would mix broad Workspace permissions into a single long-lived token — google-extras-mcp runs as an independent local stdio server with its own minimal, disposable credential.
Coverage at a glance
Ecosystem area | Official |
|
Email, Drive, Docs, Calendar, Chat, Tasks, Contacts, Script | ✅ Yes (119 tools) | — |
Blogger (blogs & posts) | — | ✅ Yes |
Google Books (My Library & public search) | — | ✅ Yes |
Google Classroom (courses, announcements, coursework) | — | ✅ Yes |
Related MCP server: gphotos-mcp
Design Principles
Strictly Read-Only: The Blogger and Books OAuth scopes also permit writes, but this server exposes zero write tools. An agent holding this server can only execute HTTP
GETrequests.Independent Failure Domain: Runs as a separate process with its own credential file (
credentials.json), ensuringgwsremains untouched and untestable-by-accident.Mtime Auto-Reload: Re-reads the token file from disk whenever its modification time changes, so re-consents or scope updates take effect without restarting the MCP client.
Upstream Fallback: For Books catalogue search, it attempts an unauthenticated public query with an optional API key first, falling back transparently to the user's OAuth token if Google's frontend blocks the key with a
503.
Installation
Two plain steps: put the code somewhere durable, then register it with the client.
Where the code lives: $HOME/.local/share/google-extras-mcp.
Downloads and Desktop folders are disposable — assume they get rm -rf-ed. A server the client spawns at every startup must live somewhere that survives that. Clone with git (full history), so updates are a git pull in place.
Scripted (recommended):
bash install.sh # clones from GitHub to ~/.local/share/google-extras-mcp
bash /old/location/google-extras-mcp/install.sh # or: move an existing checkout there (git clone, full)The script installs dependencies, registers the server with OpenCode, and prints the remaining (human) auth step. It is safe to re-run.
Manual equivalent:
git clone https://github.com/Manamama-Deepseek-AI-01/google-extras-mcp.git ~/.local/share/google-extras-mcp
python3 -m pip install -r ~/.local/share/google-extras-mcp/requirements.txt
# registration: next sectionTermux / Android works too, with no extra system packages — python3 plus those three wheels is the whole requirement. Nothing here needs gcloud, a JDK, or root; the auth script is stdlib-only. (If your Python refuses system-wide installs, add --user to the pip line.)
Credentials & Authentication
Because Google's gcloud command-line OAuth client is allowlisted narrowly and refuses sensitive scopes like Blogger or Classroom, you authenticate using your own Desktop / Installed Application OAuth client from the Google Cloud Console.
1. Obtain an OAuth Client
Go to the Google Cloud Console.
Create or select a project where you have enabled:
Blogger API (
blogger.googleapis.com)Google Books API (
books.googleapis.com)Google Classroom API (
classroom.googleapis.com)
Configure the OAuth consent screen (Internal or External / Testing).
Create Credentials → OAuth client ID → Application type: Desktop app.
Download the client secret JSON file.
Already have a Desktop-type client_secret_*.json on this machine — e.g. the one another local MCP uses (~/.config/gws/client_secret.json)? Reuse it: the OAuth client is only an app identity; this flow mints its own independent token. The APIs from step 2 must be enabled in that client's project.
2. Run the Auth Flow — who does what
python3 ~/.local/share/google-extras-mcp/auth_flow.py --client <your-oauth-client.json>The division of labour, so nobody improvises:
The command (you, or your agent) prints
AUTH_URL: https://accounts.google.com/..., binds loopback (listening on 127.0.0.1:PORT, ::1:PORT) and waits — nothing proceeds until a browser comes back.A human opens
AUTH_URLand approves the consent screens — account choice, scope list, and in Testing mode the "Google hasn't verified this app → Continue" dance. This part cannot be scripted: the browser must run on the same device as the flow, because Google redirects back to127.0.0.1:PORT.On a phone:
termux-open "$AUTH_URL"pops the default browser (Cromite, Chrome, …) for the human. It engages from the Termux app; from an ssh session into Termux it may silently not fire — then copy the URL into the browser by hand.On success the script writes
~/.config/google-extras-mcp/credentials.json(0600) and printsACCOUNT: <address>.Verify with the Self-Check (last section): expect
failures: 0.
Note on Testing Mode: If your OAuth consent screen is in Testing publishing mode, Google expires refresh tokens after 7 days. When that happens, simply re-run
auth_flow.py.
3. No client_secret_*.json to hand? Build it from your environment
Some setups never keep the JSON file: the id and secret live in exported environment variables — a shared aliases.sh sourced on every machine, a container image, a CI secret store. client_from_env.py turns that into the file auth_flow.py expects:
python3 client_from_env.py --out ~/.config/google-extras-mcp/client.jsonIt reads GOOGLE_OAUTH_CLIENT_ID/GOOGLE_OAUTH_CLIENT_SECRET, falling back to GOOGLE_CLIENT_ID/GOOGLE_CLIENT_SECRET (override with --pair client). The file is written 0600 inside a 0700 directory and the secret is never printed — only the project number, so you can tell two clients apart.
4. Web clients, phones, and the ::1 trap
A Desktop/installed client accepts any loopback port, so the default flow just works. A web client does not: Google compares its redirect URI as an exact string, and a mismatch is answered with Error 400: redirect_uri_mismatch before an account is even chosen. Pass the registered URI verbatim:
python3 auth_flow.py --client ~/.config/google-extras-mcp/client.json \
--redirect-uri http://localhost:8000/oauth2callbackTwo details that cost real time to diagnose, so they are handled in the script:
Both loopback families are bound.
localhostmay resolve to127.0.0.1or::1. On hosts where a connection to an unpublished loopback port hangs instead of being refused — Android/Termux does this — a browser that picks::1waits until it reports "The connection timed out", never falls back to IPv4, and the callback never arrives. The script prints what it bound, e.g.listening on 127.0.0.1:8000, ::1:8000. If that line shows only IPv4, expect exactly that timeout.Stray requests do not end the wait. Browsers fire
/favicon.icoand speculative connections at the same origin; only the registered path (or a request carryingcode/error) counts as the callback. Everything else gets a404.
--login-hint user@example.com prefills the account when the browser has several Google sessions open, and the final ACCOUNT: line reports which account the token actually belongs to — the token file itself records no address.
Why not gcloud auth login?
Because it cannot ask for these scopes, and on a phone it cannot run at all:
gcloudships with Google's own OAuth client, which is allowlisted to Cloud scopes. Requesting…/auth/bloggeror…/auth/classroom.*through it fails withinvalid_scope. The allowlist lives on Google's side; no flag changes it. This is the whole reason this repo has its own auth script.The Cloud SDK is glibc-linked, so it does not run under Termux's bionic libc (no official arm64 Termux package exists).
The PyPI package named
gcloudis the long-retired API client library (GoogleCloudPlatform/gcloud-python), not the CLI: it installs nogcloudexecutable.
Troubleshooting
Symptom | Cause | Fix |
| Web client, redirect compared exactly | Pass the client's registered URI with |
Browser: "The connection timed out" on | Only IPv4 bound, browser tried | Update to this version; check the |
| The API is not enabled in the client's own project | Enable Blogger / Books / Classroom in that project |
Token works, then fails after ~7 days | Consent screen in Testing | Re-run the flow, or publish the app (unverified is fine) |
| Google substituted a neighbouring scope set — e.g. | Expected; the script stores what was actually granted |
Account authorised is not the one you wanted | Several Google sessions in the browser |
|
| Flow was started over an ssh session into Termux; no app context to engage the browser | Run the flow from the Termux app itself, or paste |
Server absent from | OpenCode reads MCP config only at startup — no hot reload | Restart OpenCode, or start a new session |
Tool Catalogue (8 Read-Only Tools)
Tool Name | Description | Key Parameters |
| List Blogger blogs accessible to the account | — |
| List recent posts of a specific blog |
|
| List My Library shelves (Favorites, Reading Now, etc.) | — |
| List volumes on a specific shelf |
|
| Search the public Google Books catalogue |
|
| List Google Classroom courses | — |
| List announcements in a course |
|
| List coursework (assignments/questions) in a course |
|
Registration in OpenCode (or any MCP Client)
One command — the CLI edits the config itself (and honours JSONC comments):
opencode mcp add google-extras --global -- python3 "$HOME/.local/share/google-extras-mcp/server.py"Or by hand, in the global config (~/.config/opencode/opencode.jsonc), under "mcp" → "servers":
"mcp": {
"servers": {
"google-extras": {
"type": "local",
"command": [
"python3",
"/home/you/.local/share/google-extras-mcp/server.py"
],
"enabled": true
}
}
}python3stays bare — the client resolves it on the PATH of the user running it. Do not hard-code/usr/bin/python3; that is one machine's path, not a universal one.The server path must be absolute: JSONC does not expand
~.No hot reload. OpenCode reads MCP config at startup only. Restart the client (or start a new session) after registering;
/mcpsthen showsgoogle-extrasconnected, andopencode mcp listlists it.
Self-Check
You can verify the entire server and its credentials without starting an MCP client — run it after install and after every re-auth:
python3 ~/.local/share/google-extras-mcp/server.py --check # expect: failures: 0And the rule that saves the most time: the check's failure text is the manual. When a tool line reads
FAIL blogger_blogs No usable OAuth token. Run: python3 auth_flow.py --client <oauth-client.json> and open the printed URL. …that line is the next step — run exactly that command, hand the printed AUTH_URL to a human, and let the browser consent. Don't improvise around it.
Roadmap & Upstream PR Plan
The mid-term goal is to fold these capabilities upstream into the official Google Workspace MCP (gws). That has been deferred because:
Upstream maintainers maintain strict tool boundaries and scope discipline.
Classroom and Blogger require distinct consent screen configurations that not all Workspace users want or need in a default toolset.
Once edge cases and scope substitution behaviours (such as Google returning student-submissions scopes when asked for coursework scopes) are fully characterised, a modular PR or extension mechanism will be proposed upstream.
License
MIT License — see LICENSE for details.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Read-only Search Console analytics, URL inspection, indexing diagnostics, and sitemaps.
Read-only Google Search Console and Google Analytics for AI agents.
Read and edit GA4, Search Console and Google Tag Manager from any MCP client. 29 tools.
Read-only access to InfluSense influencer discovery, ratings, watchlists, and reports via MCP.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables read-only inspection of Google Ads accounts through MCP, including account inventory, reporting, metadata, change history, and safe GAQL queries.Apache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables read-only access to a personal Google Photos library, allowing listing, searching, inspecting, and viewing photos and albums via MCP tools.-
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to perform web search, extract page content, crawl sites, and map URLs through read-only tools.3MIT
- AlicenseAqualityBmaintenanceGives MCP-capable agents read-only access to a Google Classroom account, exposing courses, coursework, due dates, announcements, rosters and student submissions as callable tools. Nothing can be created, edited or deleted through it.8MIT