Google Workspace MCP Server

Created By
mattcoatswortha year ago
Overview

what is Google Workspace MCP Server?

Google Workspace MCP Server is a Model Context Protocol (MCP) server designed for seamless interaction with various Google Workspace APIs, including Gmail, Drive, Calendar, Docs, Sheets, and Slides.

how to use Google Workspace MCP Server?

To use the server, install the necessary dependencies, configure your Google API credentials in the .env file, and start the server using the provided commands.

key features of Google Workspace MCP Server?

  • Gmail API: Send emails, manage labels, and list messages.
  • Drive API: Create folders and upload files.
  • Docs API: Create and edit Google Docs.
  • Sheets API: Read and write spreadsheet data.
  • Slides API: Create presentations and slides.
  • Calendar API: Manage calendar events.
  • Authentication: OAuth2 authentication flow helpers.

use cases of Google Workspace MCP Server?

  1. Automating email management through the Gmail API.
  2. Creating and managing Google Docs and Sheets programmatically.
  3. Integrating calendar events into applications.
  4. Building tools that require file storage and management in Google Drive.

FAQ from Google Workspace MCP Server?

  • What are the prerequisites for using the server?

You need Node.js 16+, a Google Cloud project with the necessary APIs enabled, and OAuth 2.0 client credentials.

  • How do I authenticate with Google APIs?

Use the provided tools to generate an authorization URL, authorize the application, and obtain a refresh token to be added to your .env file.

  • Is there a license for this project?

Yes, the project is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mattcoatsworth
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago