Google Sheets
Let your agent read and write Google Sheets for lightweight CRMs, pricing tables, content calendars, and ops trackers without custom spreadsheet UI.
Overview
com.mcparmory/google-sheets is a MCP server for the Build phase that creates, reads, and modifies Google Sheets data and formatting through your agent.
What is this MCP server?
- Create, read, and update spreadsheet cells, ranges, and sheet structure
- Apply formatting and manage multiple sheets within a workbook
- Version 1.0.3 stdio MCP via uvx (mcparmory-google-sheets) or Docker OCI
- Fits solo-builder stacks that already run on Sheets for validation and growth lists
- Google API-backed MCP—not CSV import skills or manual copy-paste
- Server version 1.0.3 on MCP schema 2025-12-11
- PyPI identifier mcparmory-google-sheets and OCI ghcr.io/mcparmory/google-sheets:1.0.3
- Stdio transport for both published packages
Community signal: 25 GitHub stars.
What problem does it solve?
Your roadmap lives in Google Sheets but every update means context-switching away from the agent that is implementing the product.
Who is it for?
Indie hackers who already use Sheets as a system of record and want MCP-driven reads and writes from Claude Code or Cursor.
Skip if: Production workloads needing relational queries, strong consistency, or Sheets-as-database at high write volume without a proper backend.
What do I get? / Deliverables
Your agent can synchronize spreadsheet rows, tabs, and formatting as part of build, validate, or grow automation flows.
- Updated sheet ranges, new tabs, or formatting applied via agent tool calls
- Repeatable spreadsheet sync patterns you can embed in scripts or agent instructions
Recommended MCP Servers
Journey fit
Spreadsheet automation is a Build-phase integration pattern—wiring product or ops data to a API your agent can call while you ship features. Integrations is the shelf for third-party SaaS connectors (Google Sheets) that extend your app or agent workflow beyond the repo.
How it compares
Google Sheets API MCP connector, not a spreadsheet agent skill or offline CSV toolchain.
Common Questions / FAQ
Who is com.mcparmory/google-sheets for?
Solo builders and small teams who rely on Google Sheets for ops or validation data and use MCP-enabled coding agents to automate updates.
When should I use com.mcparmory/google-sheets?
Use it while building integrations or running lightweight growth workflows—when you need the agent to read or write live spreadsheet data alongside code changes.
How do I add com.mcparmory/google-sheets to my agent?
Add a stdio MCP server pointing at uvx mcparmory-google-sheets 1.0.3 or Docker ghcr.io/mcparmory/google-sheets:1.0.3, then configure Google API credentials and sheet sharing per the server documentation.