Google Workspace MCP Server

Created By
Tarunkumarchelumallaa year ago
Overview

what is Google Workspace MCP Server?

Google Workspace MCP Server is a Model Context Protocol (MCP) server that provides tools for programmatically interacting with Gmail and Calendar APIs, allowing users to manage their emails and calendar events efficiently.

how to use Google Workspace MCP Server?

To use the server, clone the repository, install the necessary dependencies, set up Google Cloud Console with the required APIs, and configure OAuth credentials. After setup, you can perform various operations through the MCP interface.

key features of Google Workspace MCP Server?

  • Gmail Tools: List, search, send, and modify emails.
  • Calendar Tools: List, create, update, and delete calendar events.
  • OAuth 2.0 Authentication: Secure access to Gmail and Calendar APIs.

use cases of Google Workspace MCP Server?

  1. Automating email management tasks such as filtering and sending emails.
  2. Scheduling and managing calendar events programmatically.
  3. Integrating Gmail and Calendar functionalities into other applications.

FAQ from Google Workspace MCP Server?

  • What are the prerequisites for using this server?

You need Node.js version 14 or higher and a Google Cloud project with the Gmail and Calendar APIs enabled.

  • Is there a license for this project?

Yes, this project is licensed under the MIT License.

  • What programming language is used?

The server is built using JavaScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Tarunkumarchelumalla
Star
0
Language
JavaScript
License
MIT 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)

a day ago