Google Sheets MCP Server

Created By
Meerkats-Aia year ago
google-sheet-mcp-server
Overview

What is Google Sheets MCP Server?

Google Sheets MCP Server is a powerful Model Context Protocol (MCP) server implementation designed for seamless integration with the Google Sheets API, allowing AI assistants to create, read, update, and manage Google Sheets.

How to use Google Sheets MCP Server?

To use the Google Sheets MCP Server, clone the repository, install the dependencies, set up authentication, and start the server. You can then interact with Google Sheets using various commands.

Key features of Google Sheets MCP Server?

  • Create, read, update, and delete Google Sheets
  • Manage sheet data with cell-level operations
  • Format cells and ranges
  • Share spreadsheets with other users
  • Search for spreadsheets
  • Comprehensive authentication options including Service Account, API Key, and OAuth2.

Use cases of Google Sheets MCP Server?

  1. Automating the creation of monthly budget spreadsheets.
  2. Updating sales data in real-time.
  3. Sharing project plans with team members.
  4. Formatting reports for better readability.

FAQ from Google Sheets MCP Server?

  • What authentication methods are supported?

The server supports Service Account, API Key, and OAuth2 authentication methods.

  • Is there a specific Node.js version required?

Yes, Node.js version 16 or higher is required.

  • Can I share spreadsheets with other users?

Yes, you can share spreadsheets with specific users using the server's sharing capabilities.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Meerkats-Ai
Star
0
Language
JavaScript
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