remote-mcp-server

What is remote-mcp-server?

remote-mcp-server is a simple Cloudflare Worker that fetches unread emails from Gmail using the Gmail API and OAuth 2.0 refresh tokens. It is intended for developers who need to programmatically retrieve unread email summaries, for example as a backend for a WhatsApp agent.

How to use remote-mcp-server?

Deploy with Cloudflare’s wrangler CLI, set the required environment variables (GMAIL_CLIENT_ID, GMAIL_CLIENT_SECRET, GMAIL_REFRESH_TOKEN with at least gmail.readonly scope), then send a GET request to the worker’s URL. The response is a JSON array of email summaries (id, from, date, subject, snippet).

Key features of remote-mcp-server

• Fetches unread Gmail emails via OAuth 2.0 refresh tokens
• Returns JSON array of email summaries (id, from, date, subject, snippet)
• Deployed as a Cloudflare Worker for serverless edge execution
• Requires only three environment variables for credentials
• Can be integrated as a backend for messaging agents (e.g., WhatsApp)

Use cases of remote-mcp-server

• Build a WhatsApp agent that checks unread emails on user command
• Automate periodic email checking from a serverless function
• Integrate Gmail inbox data into custom dashboard or notification system
• Prototype email-driven workflows without a dedicated backend server

FAQ from remote-mcp-server

What dependencies or runtime does remote-mcp-server require?

It requires a Cloudflare account, the wrangler CLI for deployment, and a Gmail OAuth 2.0 refresh token with at least the https://www.googleapis.com/auth/gmail.readonly scope.

How are email credentials handled?

Credentials are stored as Cloudflare Worker secrets (environment variables) — GMAIL_CLIENT_ID, GMAIL_CLIENT_SECRET, and GMAIL_REFRESH_TOKEN. The worker uses the refresh token to obtain short-lived access tokens automatically.

Where does email data live?

Email data is fetched on‑demand from the Gmail API when a GET request is made. The worker does not store emails; it only returns a summary of unread messages in the HTTP response.

What transport and authentication are used?

The worker communicates with the Gmail API over HTTPS using OAuth 2.0. The endpoint itself is public by default; optional enhancement with a custom API key header is described in the README.

Are there any known limits?

The worker depends on Gmail API rate limits and the refresh token’s scope. It only returns unread emails; no support for sending, searching, or modifying emails is provided.