Google Workspace MCP Server

Created By
aaronsba year ago
A Model Context Protocol (MCP) server that provides authenticated access to Google Workspace APIs, offering integrated Authentication, Gmail, Calendar, and Drive functionality
Overview

What is Google Workspace MCP Server?

Google Workspace MCP Server is a Model Context Protocol (MCP) server that provides authenticated access to Google Workspace APIs, integrating functionalities for Gmail, Calendar, and Drive.

How to use Google Workspace MCP Server?

To use the server, create a Google Cloud Project, enable the necessary APIs, and configure OAuth credentials. Then, run the server using Docker and authenticate your Google account through a conversational interface.

Key features of Google Workspace MCP Server?

  • Integrated access to Gmail, Calendar, and Drive APIs.
  • Automated email sorting and management.
  • Smart calendar scheduling to avoid conflicts.
  • Organized file management in Google Drive.
  • Supports multiple Google accounts with easy authentication.

Use cases of Google Workspace MCP Server?

  1. Automating email organization and retrieval.
  2. Streamlining calendar management and scheduling.
  3. Efficient file management and sharing in Google Drive.
  4. Integrating AI assistants for enhanced productivity.

FAQ from Google Workspace MCP Server?

  • Can I use this server with multiple Google accounts?

Yes! The server supports multiple accounts and allows easy switching between them.

  • Is there a cost associated with using Google Workspace MCP Server?

The server itself is free to use, but you may incur costs from Google Cloud services depending on your usage.

  • What if I encounter authentication issues?

Ensure your Google Cloud project is properly configured and that you have the correct OAuth credentials.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
aaronsb
Star
42
Language
TypeScript
License
MIT license
Tags

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