Mcp Google Sheets

Created By
xing5a year ago
This MCP server integrates with your Google Drive and Google Sheets, to enable creating and modifying spreadsheets.
Overview

what is mcp-google-sheets?

mcp-google-sheets is a Model Context Protocol (MCP) server that integrates with Google Drive and Google Sheets, allowing users to create, read, update, and manage spreadsheets through the Google Sheets API.

how to use mcp-google-sheets?

To use mcp-google-sheets, set up a Google Cloud Platform project, choose an authentication method (Service Account or OAuth 2.0), and run the server using the provided commands. You can interact with the server to manage your spreadsheets.

key features of mcp-google-sheets?

  • Create, read, update, and manage Google Sheets
  • Support for batch updates and multiple operations
  • Integration with Google Drive for spreadsheet management
  • Easy setup with Google Cloud Platform

use cases of mcp-google-sheets?

  1. Automating spreadsheet updates for financial reports
  2. Creating and managing project tracking sheets
  3. Integrating spreadsheet data with other applications

FAQ from mcp-google-sheets?

  • What authentication methods are supported?

mcp-google-sheets supports Service Account authentication for automated environments and OAuth 2.0 for interactive use.

  • Is there a license for mcp-google-sheets?

Yes, mcp-google-sheets is licensed under the MIT License, allowing free use, modification, and distribution.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
xing5
Star
149
Language
Python
License
MIT 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