Google WorkspaceBLOCK

exec(`cmd /c start "" "${url}"`, onError);

redirectUri = `http://127.0.0.1:${addr.port}/callback`;

no-delete

.mcpbignore

const { stdout } = await exec(GWS, args, {

return createHash('sha1').update(message).digest('hex').slice(0, 12);

console.log(`token acquired for ${EMAIL} (not printed)\n`);

import { getAccessToken } from '../../build/accounts/token-service.js';

const { loadManifest } = await import('../../build/factory/generator.js');

import { getAccessToken } from '../../build/accounts/token-service.js';

import { getAccessToken } from '../../build/accounts/token-service.js';

import { loadManifest } from '../../../build/factory/generator.js';

const out = sanitizeHtmlForAgent('<p>visiblehidden</p>', { source: 'gmail' });

expect(out).not.toContain('');

const dirty = 'hello';

@modelcontextprotocol/sdk, sanitize-html, yaml, @types/node, @types/sanitize-html, @typescript-eslint/eslint-plugin, @typescript-eslint/parser, eslint

A `SERVICE_SCOPE_MAP` constant maps service names to OAuth scope URLs. `scopesForServices("gmail,drive,meet")` produces deduplicated scope URLs plus base scopes (`openid`, `userinfo.email`). Default a

- `drive` and `sheets` have GET methods with no read-only scope, so read access to those two allows less than full access but still slightly more than reading. The consent step must say so rather than

An in-memory `Map<email, {accessToken, expiresAt}>` caches short-lived access tokens for the MCP session lifetime. `getAccessToken(email)` returns a cached token if >60 seconds remain, otherwise excha

The policy **fails open** on every uncertainty: no credential, unreadable credential, no

Google is asked for the narrower scopes, so the token itself cannot send, edit or delete — not a rule this server enforces on top of a broad token. Where a service has no read-only scope, you're told

| `users.settings.cse.keypairs.create`<br>*POST* | Creates and uploads a client-side encryption S/MIME public key certificate chain and private key metadata for the authenticated user. For administrat

The GWS MCP server currently treats every content operation as a direct API call. `manage_docs write` appends text to a live document. `manage_email send` streams the full body in a single tool call.

An in-memory `Map<email, {accessToken, expiresAt}>` caches short-lived access tokens for the MCP session lifetime. `getAccessToken(email)` returns a cached token if >60 seconds remain, otherwise excha

**Wait for Google's official Workspace MCP server.** Announced, but reportedly single-user by design. Our multi-account model — an `email` parameter on every call rather than a session-bound identity