"Connecting MCP to Google Sheets for Editing and Modifications" matching MCP servers:

A locally running MCP server that provides cell-level and formatting-level control over Google Sheets via the Sheets API v4, enabling reading, writing, formatting, and managing spreadsheets through natural language.

A Model Context Protocol server that integrates with Google Drive and Google Sheets, enabling users to create, read, update, and manage spreadsheets through natural language commands.

A comprehensive Google Sheets MCP server offering 26 tools for read/write, structural updates, Drive search, and an escape hatch for executing arbitrary Node.js code with pre-authenticated Sheets and Drive clients.

A write-only MCP server for Google Sheets with safety features including whitelist, dry-run, snapshot, and audit logging.

Provides comprehensive Google Sheets integration for creating, reading, updating, and managing spreadsheets programmatically via tools like batch updates and range operations. It enables automated workflows for data analysis, project management, and synchronization within the Model Context Protocol.

Enables AI assistants to access, search, and analyze Google Spreadsheets through the Model Context Protocol. Supports both OAuth 2.0 for private sheets and API key authentication for public sheets, with tools for listing, reading, and searching spreadsheet data.

Provides a secure bridge for AI assistants to interact with the Google Sheets API via 31 tools for spreadsheet management, data manipulation, and table-level operations. It supports both Service Account and OAuth 2.0 authentication for tasks including batch updates, CSV imports, and conditional formatting.

Converts AI Skills (following Claude Skills format) into MCP server resources, enabling LLM applications to discover, access, and utilize self-contained skill directories through the Model Context Protocol. Provides tools to list available skills, retrieve skill details and content, and read supporting files with security protections.

Relays a result screenshot to Slack so you can review a coding agent's output without opening the app.

MCP server for AI agents to send notifications, copy to clipboard, request confirmations, and collect text input from users across their devices.

Routes one brief to the right image model across 60+ (gpt-image-1.5, Ideogram 3, Recraft V4, Flux), validates the output, and fans out to iOS/Android/PWA/favicon/visionOS/Flutter bundles. Works without an API key via Pollinations, HF Inference, Stable Horde, or host-LLM inline SVG.

Enables users to turn any API's documentation into a tested MCP server whose tools expose the API's own operations, with linting, contract tests, and live verification. It accepts OpenAPI/Swagger, Postman, RAML, WSDL, GraphQL, RSS, and HTML docs.

Enables turning requirements documents into RFCs, functional test scenarios, and a traceability matrix, with tools to parse, diff, and verify coverage.

Turn natural language into 3D models in Fusion 360. 64 CAD tools including sketches, extrudes, fillets,and JIS standard parts.

A Model Context Protocol server that converts Markdown content to HTML format.

Automatically crawls documentation websites, converts them to organized markdown files, and generates condensed cheat sheets. Intelligently categorizes content into tools/APIs and provides local-first access to downloaded documentation.

Enables an MCP-compatible AI client to author Blender Python, run Blender, import the resulting asset into Unity with materials and a prefab, place it in the active scene, verify the import, and revise the same asset using stable IDs.

Enables MCP clients to turn Make blueprints and Zapier exports into n8n workflow files, with a per-step report of what converted, what to review, and what must be finished by hand. Also lists zaps, explains how individual steps are handled, checks workflow files for broken links or placeholders, and can upload the result to an n8n instance as an inactive workflow.

Enables AI assistants to query PostgreSQL, MySQL, SQL Server, Oracle, and MongoDB databases through MCP with read-only, audited access.

Generates standalone, human-readable MCP servers from RAML 1.0 or OpenAPI 3.x specs, exposing one tool per resource and method that makes real HTTP calls. It understands Mule/Anypoint auth patterns such as Client ID enforcement and OAuth2, wiring the expected credentials from environment variables at call time.