Google Spreadsheetを操作するためのMCPサーバー
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"spreadsheet-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Spreadsheet MCP An MCP server for operating Google Spreadsheets (Google Sheets) ## Features - Fetch data from Google Spreadsheets and display it in Markdown table format - Get a list of column names (header row) from Google Spreadsheet sheets - Identify the URL of a specified sheet name within a Google Spreadsheet - Retrieve a list of all sheet names existing in a Google Spreadsheet - Upload CSV files to Google Spreadsheets - Copy the contents of one sheet to another sheet in Google Spreadsheets This tool is designed for tabular sheets (with columns in the first row and no duplicate column names). ## Authentication https://docs.gspread.org/en/latest/oauth2.html ## Configuration ```json { "mcpServers": { "spreadsheet": { "command": "uvx", "args": [ "--from", "git+https://github.com/yamitzky/spreadsheet-mcp.git", "spreadsheet-mcp" ] } } } ``` ## Development ### Setting up the development environment ```bash # Clone the repository git clone https://github.com/yamitzky/spreadsheet-mcp.git cd spreadsheet-mcp # Install development dependencies uv sync ``` ### Testing and Linting ```bash # Run linting with ruff ruff check . # Run type checking with pyright pyright ```
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.