Google MCP Remote MCP Server

Google MCP Remote MCP server exists for a simple reason — assistants are far more useful when they can act on Google MCP Remote directly instead of describing what you should do. Collection of Google-native tools (e.g., Gmail, Calendar) for the MCP.

What you get

For local testing: http://localhost:8788/callback ```

• Send emails with multiple recipients (to, cc, bcc) and HTML content
• List emails with custom queries, labels, and result limits
• Read specific emails by ID
• Manage labels (add, remove, list)
• Draft and delete emails
• List calendars and set a default calendar

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

What the assistant can call

Once Google MCP Remote is connected, these are the calls the assistant has available:

• Prerequisites — For local testing: http://localhost:8788/callback

Configuration and credentials

You will need 3 environment variables: GOOGLE_OAUTH_CLIENT_ID, GOOGLE_OAUTH_CLIENT_SECRET, COOKIE_ENCRYPTION_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

1. Google Cloud Project: - Create a project in the Google Cloud Console - Set up OAuth 2.0 credentials (Client ID and Client Secret) - Enable the APIs you need (Gmail, Calendar, Drive, Tasks, YouTube, People/Contacts) - Add authorized JavaScript origins and redirect URIs for your Cloudflare Worker - Redirect URI should be in the format: 2. **Cloudflare

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the google mcp remote mcp server does with a few real requests.

Choosing this one

This sits in the planning and project tracking group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Google MCP Remote's toolset — Prerequisites — is a fair guide to whether it matches your workflow. It is maintained by vakharwalad23; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Google MCP Remote's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.