Generic MCP Server for Google Workspace
Enables sending emails and creating drafts via the Gmail API.
Allows appending content to Google Documents.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Generic MCP Server for Google WorkspaceSend an email to jane@example.com with subject 'Meeting' and body 'Let's talk tomorrow.'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Generic MCP Server for Google Workspace
A Model Context Protocol (MCP) server that securely exposes Google Workspace capabilities to AI Agents (like Claude Desktop, OpenAI, or Cursor) through standardized MCP tools.
This server acts as a bridge, allowing any MCP-compatible AI client to interact with Google APIs without requiring custom integrations inside the agent itself.
Features & Tools
Currently, the server exposes the following tools:
gmail_send_email: Sends an email (supports To, Cc, Bcc, Subject, and Text/HTML bodies).gmail_create_draft: Creates an email draft in the authenticated user's account.gdocs_append_content: Appends text to the end of a specific Google Document (requires the Document ID).
Related MCP server: Google Workspace MCP Server
Prerequisites
Node.js (v18 or newer)
Google Cloud Console Project:
Enable the Gmail API and Google Docs API.
Create an OAuth 2.0 Client ID (Web application).
Set the Authorized Redirect URI to
http://localhost(or your domain).
Setup & Local Authentication
Install Dependencies
npm installConfigure Environment Variables Copy
.env.exampleto.envand add your Google credentials:GOOGLE_CLIENT_ID=your_client_id_here GOOGLE_CLIENT_SECRET=your_client_secret_here GOOGLE_REDIRECT_URI=http://localhostGenerate OAuth Tokens To grant the server access to your Google account, you must complete the OAuth flow once. Run the token generation script:
npm run build node dist/auth/generate_token.jsFollow the on-screen instructions. The script will save your access and refresh tokens locally in
.tokens.json.
Running the Server
Local Development
To run the server locally, you can use the standard build and start scripts:
npm run build
npm startNote: The server is configured to run over HTTP using Server-Sent Events (SSE) by default on http://localhost:3000/sse.
Cloud Deployment (Railway)
This server is pre-configured to be easily deployable to cloud services like Railway.
When deploying to a remote host:
Ensure the
TOKEN_PATHenvironment variable is set to a persistent volume (e.g.,/app/data/.tokens.json), as the local file system in most cloud providers is ephemeral.The server will automatically bind to the
PORTenvironment variable provided by your cloud host.
For full instructions, see the Deployment Plan.
Connecting an AI Agent
To connect an AI Agent to this MCP Server, add the HTTP URL to your agent's MCP configuration file (e.g., in Claude Desktop).
{
"mcpServers": {
"google-workspace": {
"url": "http://localhost:3000/sse"
}
}
}(If deployed remotely, replace the URL with your remote domain, e.g., https://my-server.up.railway.app/sse).
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Santhosh-A-Git/MCP-Server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server