Skip to main content
Glama
Santhosh-A-Git

Generic MCP Server for Google Workspace

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 Services MCP Server

Prerequisites

  1. Node.js (v18 or newer)

  2. 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

  1. Install Dependencies

    npm install
  2. Configure Environment Variables Copy .env.example to .env and add your Google credentials:

    GOOGLE_CLIENT_ID=your_client_id_here
    GOOGLE_CLIENT_SECRET=your_client_secret_here
    GOOGLE_REDIRECT_URI=http://localhost
  3. Generate 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.js

    Follow 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 start

Note: 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:

  1. Ensure the TOKEN_PATH environment variable is set to a persistent volume (e.g., /app/data/.tokens.json), as the local file system in most cloud providers is ephemeral.

  2. The server will automatically bind to the PORT environment 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).

Related MCP Connectors

  • Email infrastructure for AI agents — send, receive, search, and reply to email over MCP.

  • MCP server connecting AI agents to 100+ apps (Gmail, Slack, Notion, GitHub) via one-click OAuth.

  • Your agent needs a mailbox of its own — to receive, thread, draft and send, with attachments, without borrowing your personal inbox or your company's SMTP. **What you can ask for** • "Create an inbox for this agent and tell me its address." • "Read the new messages in this thread and draft a reply." • "Send this message with the attachment and wait for the response." • "Search this inbox for everything from that domain." • "Show delivery metrics and the events on this inbox." **How to use it** Point any MCP client at https://mcp.aisa.one/mail/mcp and sign in with OAuth — there is no key to create or paste. 49 tools: create and delete inboxes, list and read messages, raw message bodies, attachments, threads, drafts and draft attachments, send and reply, message search, inbox events, metrics, and list entries — reads and writes. **Why this rather than the source** A real inbox an agent owns, rather than an SMTP credential it borrows from a human. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Find the contact elsewhere in the catalogue, then write to them from here — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/sales/mcp finds the person to write to.

  • Multiple Gmail accounts, editable Google Sheets & Docs for AI agents. Deny-by-default access rules.

Related MCP Servers