Google MCP Remote

Created By
vakharwalad23a year ago
Overview

what is Google MCP Remote?

Google MCP Remote is a Cloudflare Workers-based implementation of the Model Context Protocol (MCP) that provides tools for accessing Google APIs such as Gmail, Calendar, Drive, and more, designed for seamless integration with AI clients like Claude or Cursor.

how to use Google MCP Remote?

To use Google MCP Remote, deploy your own instance on Cloudflare Workers, configure it with your Google Cloud Project credentials, and then connect it to your AI client to perform tasks using your Google account.

key features of Google MCP Remote?

  • Gmail: Send, read, and manage emails with custom queries and labels.
  • Calendar: Create and manage events, list calendars, and find free time slots.
  • Drive: Filter, view, and manage files, including creating and sharing documents.
  • Tasks: Create and manage task lists and individual tasks.
  • YouTube: Search for videos and get detailed information about them.
  • Contacts: List and search Google Contacts.

use cases of Google MCP Remote?

  1. Automating email management and scheduling through AI.
  2. Integrating Google Calendar events with AI-driven applications.
  3. Managing Google Drive files and tasks programmatically.
  4. Enhancing AI client capabilities with Google services.

FAQ from Google MCP Remote?

  • Can I use Google MCP Remote with any AI client?

Yes! It is designed to work with AI clients like Claude and Cursor.

  • Is it safe to use Google MCP Remote?

Always deploy your own instance to maintain control over your data and API access.

  • What are the prerequisites for deployment?

You need a Google Cloud Project with OAuth 2.0 credentials and a Cloudflare account.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
vakharwalad23
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago