Google Workspace MCP Server
@KaranThink41
About Google Workspace MCP Server
This is G_chat Mcp server written in Ts contain various tools fetch to post.
Basic information
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\"}"
]
}
}
}Tools
No tools detected
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
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
FAQ from Google Workspace MCP Server
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).
More AI & Agents MCP servers
Shell and Coding agent for Claude and other mcp clients
rusiaamanShell and coding agent on mcp clients
1Panel
1Panel-dev🔥 1Panel is a modern, open-source VPS control panel — and the only one with native AI agent support. Run Ollama models, deploy OpenClaw agents, and manage your entire server stack from one clean web interface.
MCP-NixOS - Because Your AI Assistant Shouldn't Hallucinate About Packages
utensilsMCP-NixOS - Model Context Protocol Server for NixOS resources
Model Context Protocol for Unreal Engine
chongdashuEnable AI assistant clients like Cursor, Windsurf and Claude Desktop to control Unreal Engine through natural language using the Model Context Protocol (MCP).
Hass-MCP
voskaControl and query Home Assistant from Claude and other LLMs — a Model Context Protocol (MCP) server.
Comments