Google Workspace MCP Server

@KaranThink41

Repository

Basic information

About Google Workspace MCP Server

This is G_chat Mcp server written in Ts contain various tools fetch to post.

#google-chat#mcp-server#workspace-tools

Google Workspace MCP Server config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "Google_chat_mcp_server": {
      "command": "npx",
      "args": [
        "spinai-mcp",
        "install",
        "@KaranThink41/gsuite-mcp-server",
        "--provider",
        "smithery",
        "--config",
        "{\"googleClientId\":\"your_google_client_id\",\"googleClientSecret\":\"your_google_client_secret\",\"googleRefreshToken\":\"your_google_refresh_token\"}"
      ]
    }
  }
}

Google Workspace MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

Fetch the live tool list by running this server in a temporary sandbox using the button above.

Overview

What is Google Workspace MCP Server?

A Model Context Protocol (MCP) server that provides tools for interacting with Gmail and Google Calendar APIs. It enables programmatic management of emails and calendar events through the MCP interface.

How to use Google Workspace MCP Server?

Install via Smithery CLI or run locally. Requires Node.js 14+, Google Cloud Console project with Gmail and Calendar APIs enabled, and OAuth 2.0 credentials (client ID, client secret, refresh token). Run node build/index.js after building.

Key features of Google Workspace MCP Server

List, search, and send emails with CC/BCC support
Modify email labels (archive, trash, mark read/unread)
List, create, update, and delete calendar events with attendees
OAuth 2.0 based authentication
API quota and limit error handling

Use cases of Google Workspace MCP Server

Automate email sorting and labeling tasks
Send scheduled or template emails programmatically
Manage calendar events and meetings from MCP clients
Integrate with AI assistants to handle Gmail and Calendar

Frequently asked questions

What prerequisites are needed?

Node.js 14 or higher, a Google Cloud project with Gmail API and Calendar API enabled, and OAuth 2.0 credentials (client ID, client secret, refresh token).

How do I authenticate?

Set up OAuth 2.0 credentials in Google Cloud Console with `http://localhost:3000/auth/callback` as an authorized redirect URI. Provide the client ID, client secret, and refresh token to the server.

Where are my data and credentials stored?

Credentials are passed as configuration to the server (e.g., via Smithery CLI). No local storage is used; all API calls go directly to Google.

What known limits exist?

Google API quotas and rate limits apply. The server returns descriptive error messages for authentication failures, invalid parameters, and quota exceeded errors.

Which transport or authentication does the server use?

The server uses OAuth 2.0 with a refresh token for authentication. Transport is standard MCP over local subprocess (command line execution).

Comments

More AI & Agents MCP servers

Plainpaper

The AI marketing canvas for Claude and MCP agents. Your agent drafts campaigns as cards on a shared board, briefed by your brand rules, approved by you.

AON — Agent Offer Network

AON

AON MCP connects AI agents to real, buyable products and services with live pricing and tracked links—enabling builders to earn developer revenue share from attributed clicks and conversions.

Legion MCP

faulkj

MCP-native LLM councils for debates, juries, blind panels, voting, refinement, and custom multi-model deliberation.

OpenZiti MCP Gateway

openziti

NetFoundry MCP Gateway enables secure, isolated access to Model Context Protocol (MCP) tools across distributed systems without exposing public endpoints. Zero trust gateway for MCP servers. Aggregate, filter, and secure

Quest: Hire a Human

Quest (hireahuman.quest)

Hire a verified local human for small real-world tasks your AI agent can't do: errands, queues, pickups, in-person checks and on-site photos. Your agent posts a quest, local humans send offers, and your user picks one an