Googleworkspace Mcp

Created By
orvicea year ago
Overview

What is Google Workspace MCP?

Google Workspace MCP is a Model Context Protocol server designed for managing Google Workspace resources through the Admin SDK, enabling administrators to automate and manage their Google Workspace environment effectively.

How to use Google Workspace MCP?

To use Google Workspace MCP, set up a Google Cloud Platform project with the Admin SDK API enabled, configure a service account with the necessary permissions, and run the server with the required environment variables.

Key features of Google Workspace MCP?

  • Manage Google Workspace resources programmatically through the Admin SDK.
  • List users, read Gmail messages, and access calendar events.
  • Supports domain-wide delegation for service accounts.

Use cases of Google Workspace MCP?

  1. Automating user management in Google Workspace.
  2. Integrating Gmail and Calendar functionalities into applications.
  3. Streamlining administrative tasks for Google Workspace admins.

FAQ from Google Workspace MCP?

  • What prerequisites are needed to use Google Workspace MCP?

You need a Google Cloud Platform project with the Admin SDK API enabled, a service account with appropriate permissions, and a Google Workspace admin user to impersonate.

  • How do I configure the service account?

Create a service account in the Google Cloud Console, grant it the necessary permissions, and enable domain-wide delegation.

  • What tools are available with Google Workspace MCP?

Available tools include directory_users for listing users, list_gmail for accessing Gmail messages, and list_calendar_events for retrieving calendar events.

Server Config

{
  "mcpServers": {
    "googleworkspace-mcp": {
      "command": "/go/bin/google-workspace-mcp",
      "args": [],
      "env": {
        "GOOGLE_SERVICE_ACCOUNT": "test.json",
        "GOOGLE_ADMIN_EMAIL": "admin@yourdomain.com"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
orvice
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago