Google Drive & Sheets MCP Server

Created By
distrihuba year ago
A Model Context Protocol (MCP) server built in Rust for interacting with Google Drive and Google Sheets.
Overview

What is Google Drive & Sheets MCP Server?

Google Drive & Sheets MCP Server is a Model Context Protocol (MCP) server built in Rust that allows users to interact with Google Drive and Google Sheets, providing a seamless integration for various workflows.

How to use Google Drive & Sheets MCP Server?

To use the server, install it via Cargo, configure your Google Cloud Project with the necessary APIs and OAuth credentials, and start the server for either Google Drive or Google Sheets using the provided commands.

Key features of Google Drive & Sheets MCP Server?

  • List and filter files in Google Drive with customizable parameters.
  • Read and write data to Google Sheets, including creating new spreadsheets and clearing values.
  • Implements MCP for compatibility with agent frameworks like Distri.

Use cases of Google Drive & Sheets MCP Server?

  1. Automating data entry and retrieval from Google Sheets.
  2. Integrating Google Drive file management into larger applications.
  3. Building custom workflows that utilize Google Workspace services.

FAQ from Google Drive & Sheets MCP Server?

  • What are the prerequisites for using this server?

You need Rust, a Google Cloud Project with Drive and Sheets APIs enabled, and OAuth 2.0 credentials configured.

  • Is there a license for this project?

Yes, it is licensed under the MIT License.

  • Can I contribute to this project?

Yes, contributions are welcome through Pull Requests.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
distrihub
Star
0
Language
Rust
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.

32 minutes ago