Google Workspace runs on your own machine — the client starts it, so there is no endpoint to ping. 388 installs a week from npm. Last commit 31 Oct 2026.
Search and work in Gmail, Calendar, Drive, Docs, Sheets and Slides across several Google accounts.
What the code does
We read the source, 1 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const child = spawn(cmd, args, {
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add google -e 'GOOGLE_OAUTH_CLIENT_FILE=<GOOGLE_OAUTH_CLIENT_FILE>' -e 'GMAIL_ADDRESSES=<GMAIL_ADDRESSES>' -e 'GMAIL_MODIFY_ACCOUNTS=<GMAIL_MODIFY_ACCOUNTS>' -- npx -y @foreverworks/mcp-google{
"mcpServers": {
"google": {
"command": "npx",
"args": [
"-y",
"@foreverworks/mcp-google"
],
"env": {
"GMAIL_ADDRESSES": "<GMAIL_ADDRESSES>",
"GMAIL_MODIFY_ACCOUNTS": "<GMAIL_MODIFY_ACCOUNTS>",
"GOOGLE_OAUTH_CLIENT_FILE": "<GOOGLE_OAUTH_CLIENT_FILE>"
}
}
}
}[mcp_servers.google]
command = "npx"
args = ["-y", "@foreverworks/mcp-google"]
env = { GOOGLE_OAUTH_CLIENT_FILE = "<GOOGLE_OAUTH_CLIENT_FILE>", GMAIL_ADDRESSES = "<GMAIL_ADDRESSES>", GMAIL_MODIFY_ACCOUNTS = "<GMAIL_MODIFY_ACCOUNTS>" }{
"mcpServers": {
"google": {
"command": "npx",
"args": [
"-y",
"@foreverworks/mcp-google"
],
"env": {
"GMAIL_ADDRESSES": "<GMAIL_ADDRESSES>",
"GMAIL_MODIFY_ACCOUNTS": "<GMAIL_MODIFY_ACCOUNTS>",
"GOOGLE_OAUTH_CLIENT_FILE": "<GOOGLE_OAUTH_CLIENT_FILE>"
}
}
}
}{
"servers": {
"google": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@foreverworks/mcp-google"
],
"env": {
"GMAIL_ADDRESSES": "<GMAIL_ADDRESSES>",
"GMAIL_MODIFY_ACCOUNTS": "<GMAIL_MODIFY_ACCOUNTS>",
"GOOGLE_OAUTH_CLIENT_FILE": "<GOOGLE_OAUTH_CLIENT_FILE>"
}
}
}
}Put your own values in place of
<GOOGLE_OAUTH_CLIENT_FILE> (Path of your OAuth client's JSON (a Desktop app client from the Google Cloud console)), <GMAIL_ADDRESSES> (Each account's label and address, e.g. [email protected],[email protected]), <GMAIL_MODIFY_ACCOUNTS> (Where each mailbox's Gmail grant is kept, e.g. personal=/path/to/grants/gmail-personal.json; consent writes it there. Without it the other products work, but no mailbox does).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
CALENDAR_TIME_ZONE (The time zone a time without an offset is read in, e.g. Europe/Paris), GOOGLE_TOOLSETS (The products whose tools the server loads, separated by commas, e.g. gmail,calendar. Empty loads every product).
Alternatives to Google Workspace
same job, measured the same wayGoogle Workspace MCP server for Gmail, Calendar, Drive, Docs, Sheets, Slides, Contacts, and more
Google Workspace MCP server for Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Tasks, Chat.
Multi-account Google Workspace MCP — Gmail, Calendar, Drive, Sheets, Docs with smart routing.
Google Workspace MCP — Docs, Drive, Calendar, Gmail, Sheets, Slides, Tasks, Chat, People, Forms
MCP server for Google Workspace — Sheets, Drive, Docs (HTML or Markdown), Calendar, and Gmail.
67 curated MCP tools for Google Workspace: Gmail, Calendar, Drive, Sheets, Docs, Slides, Tasks.
Secure access to Google Drive, Docs, Sheets, Slides, and Calendar through MCP.
Give AI agents access to Gmail, Calendar, Drive, and more — multi-account, manifest-driven
Google Workspace — questions
Answers built from our own checks of this server.