Google MCP Remote

Created By
vakharwalad23a year ago
Collection of Google-native tools (e.g., Gmail, Calendar) for the MCP
Overview

What is Google MCP Remote?

Google MCP Remote is a Cloudflare Workers-based server that provides access to various Google API tools (like Gmail, Calendar, Drive) for the Model Context Protocol (MCP), enabling seamless integration with AI clients such as 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 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, find free time slots, and list calendars.
  • Drive: Manage files, read content, and share files with specific permissions.
  • Tasks: Create and manage task lists and 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 through AI.
  2. Scheduling events and managing calendars via voice commands.
  3. Accessing and managing Google Drive files programmatically.
  4. Creating and managing tasks using AI clients.
  5. Searching for YouTube videos based on user queries.

FAQ from Google MCP Remote?

  • Is it safe to use Google MCP Remote?

Yes, but ensure you deploy your own instance to maintain control over your data and API access.

  • What APIs do I need to enable?

You need to enable Gmail, Calendar, Drive, Tasks, YouTube, and People/Contacts APIs in your Google Cloud Project.

  • Can I test it without deploying?

Yes, you can run a local development server for testing purposes.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
vakharwalad23
Star
2
Language
TypeScript
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

7 hours ago
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