MCP Google Spreadsheet

Created By
prudentmeana year ago
MCP Server for Google Spreadsheet
Overview

What is MCP Google Spreadsheet?

MCP Google Spreadsheet is a tool that allows AI assistants to operate Google Spreadsheet and Google Drive files through the Model Context Protocol (MCP) server.

How to use MCP Google Spreadsheet?

To use MCP Google Spreadsheet, install it via Go, set the required environment variables, and run the application. Initial authentication with your Google account is required.

Key features of MCP Google Spreadsheet?

  • List, copy, and rename files in Google Drive.
  • List, copy, rename sheets, and update cell data in Google Spreadsheet.
  • Batch update multiple ranges of cells.

Use cases of MCP Google Spreadsheet?

  1. Automating data entry in Google Sheets.
  2. Managing files in Google Drive through AI assistants.
  3. Integrating with AI tools like Claude or ChatGPT for enhanced productivity.

FAQ from MCP Google Spreadsheet?

  • What are the prerequisites for using MCP Google Spreadsheet?

You need Go 1.24 or higher and enabled Google Drive and Sheets APIs in your Google Cloud project.

  • Is there a security feature?

Yes! Access is restricted to files within the specified folder ID, and directory traversal attacks are prevented.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
prudentmean
Star
9
Language
Go
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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.

29 minutes ago