Agent-Native Calendar
by BuilderIO
Agent-Native Google Calendar - manage events, sync, and public booking
Runs in the cloud★ 7,620MITUpdated 2 months ago
Install
Google Sheets MCP
Overview
Description from the maker (original English)
Google Sheets as MCP tools: read ranges, write without destroying formulas, format and validate.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Docs, sheets & office work
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account mmedum, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Docs, sheets & office worki
- More stars than 0% of the other 2204 servers in this category
- Published to the registry more recently than 89% of the other 2204 servers in this category
- Basic checks equal to or better than 100% of the other 2204 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Google Sheets MCP safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (4.2.1) reached the registry 3 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
What can I use instead?
In the same category: Agent-Native Calendar, Excel MCP Server, MCP Server for Excel
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Excel MCP Server
by haris-musa
Lets AI create and edit Excel files itself, including formulas, charts and PivotTables, without Excel installed.
Runs on your computer★ 4,276MITUpdated 7 days ago
Install
MCP Server for Excel
by sbroenne
Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.
Runs on your computer★ 847MITUpdated 4 days ago
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
google-sheets-mcp
Google Sheets as MCP tools. Read and write ranges without destroying the formulas underneath. One Go binary over stdio, signed in as you, with your own OAuth client and the refresh token in your OS keyring.
It is for a person with a Google account who wants an assistant to read, write and reshape the spreadsheets they can already open, as them. It works inside a spreadsheet: values, formulas, formatting, sheets, charts, pivot tables, Connected Sheets, cell comments and notes. Finding, sharing, moving and trashing files, and their revisions, belong to a server built on the Drive API.
Goals and non-goals
Goals:
- A write never destroys what it did not see. The target is read first. Overwriting anything non-empty, a formula above all, is refused until the call says so, naming the cells, and carries the checkpoint of what it replaces.
- What Google changes is said. Every write reports each value Google stored differently from how it was sent, and every delete names what it takes, including what Google removes without saying so.
- The model never guesses an address. Ranges are A1 throughout, sheet titles are read and quoted, and every read is a grid with its column letters and row numbers.
- Nothing irreversible or outward-reaching runs unless you turn it on. Deletes are not registered by default and need
confirm, and a formula that makes Google fetch a URL needs a setting no argument can lift. - Reads are bounded. Every read has a budget in cells and characters, resolved before the call, and says where to continue.
- Act as you, and log nothing about your spreadsheets. Every call runs as the signed-in account, and the logs never carry cell values, formulas, titles, ranges or search terms.
Non-goals:
- Files, folders, sharing and revisions. Drive is read only to find a spreadsheet by title, show its owner and modified time, and name the signed-in account.
- Spreadsheet settings. No tool changes a spreadsheet's title, locale or recalculation setting.
- Changes pushed to it. The Sheets API has no push channel or change feed.
- Apps Script, add-ons or a calculation engine. Formulas are written and read as text, and Google computes them.
- A hosted service. It speaks stdio only, so Claude on the web and on mobile cannot reach it.
- Asking you before a call. Your client approves each call; the server asks nothing.
What makes this one different
- Guarded writes. A spreadsheet has no undo behind an API call, and the value you can see is rarely the whole cell: underneath it there may be a formula, a different stored type, or a note.
write_valuesreads the target first and refuses to overwrite anything non-empty withoutoverwrite, or a formula withoutoverwrite_formulasas well. - It does the index arithmetic. Google names the first sheet in the account's language, so it is often not an English word. Titles are read from the spreadsheet and quoted for you, and the model never sees a
GridRange. - Coercion is reported.
input: typedparses as a person typing, so007becomes7; every value Google changed comes back named. - A curated surface, gated by registration. A tool that is switched off is not registered, so it cannot be called at all.
- Verifiable releases. Signed checksums, build provenance, SBOMs and reproducible builds.
Tools
The Scope column names what each tool needs. A spreadsheet named by its title is found through Drive, under drive.readonly. In read-only mode, spreadsheets.readonly takes the place of spreadsheets.
| Tool | What it does | Scope |
|---|---|---|
get_spreadsheet | The spreadsheet card: title, link, locale, and every sheet's exact title, id, size, frozen rows, hidden state and what it holds, plus named ranges, tables, protected ranges and filter views. No cell data, so it costs the same on a spreadsheet of ten cells and one of ten million. Call it first | spreadsheets |
read_range | An addressed grid of a range: column letters across the top, row numbers down the side. show=both prints each formula under the value it produced. Budgeted in cells and characters, with a continuation, and every read returns a checkpoint | spreadsheets |
read_formatting | What a range looks like — number formats, fonts, colors, borders, alignment — per block of identically formatted cells rather than per cell, with the merges, conditional rules, banding, validation and notes that decide how a cell looks without being on the cell | spreadsheets |
search_spreadsheets | Find a spreadsheet by part of its title, by text inside it, by owner or by when it changed | drive.readonly |
find_in_spreadsheet | Search one spreadsheet for text or an RE2 pattern and get back A1 addresses, saying whether each match was in a value, in the formula under it, or in a note beside it | spreadsheets |
create_spreadsheet | A new spreadsheet, optionally with extra sheets and seed values. Returns its card, including the id every later call needs | spreadsheets |
write_values | Write a rectangle, refusing first anything the write would destroy that you cannot see, then reporting every value Google stored differently from how it was sent. An overwrite carries the checkpoint of what it replaces | spreadsheets |
append_rows | Add rows after a block of data and report where they actually landed — Google decides the destination, and the same sheet given different ranges appends in different places. It inserts, so it never writes over a row | spreadsheets |
format_cells | Number format, font, colors, borders, alignment, wrapping, merges and notes, applied in one atomic batch. A merge, a clear and a note are the three that take something away, and each is refused until acknowledged | spreadsheets |
manage_range | Add, update or delete what is attached to a range: a named range, a protected range, a validation rule, a table and the types of its columns, banding, or a conditional format rule or color scale. Existing ones are named by the range they cover, not by an id | spreadsheets |
transform_range | Sort, replace, trim, de-duplicate, split, shuffle, fill, copy or move a range — the operations that move data without you naming its new address, so each reads what it would land on first | spreadsheets |
manage_anchor | Label a row, column or sheet so it can be found again after the spreadsheet has been edited around it. An anchor follows its row through inserts, deletes, moves and sorts, where an A1 address goes stale the moment somebody inserts a row. Pass anchor: anywhere a range or band is taken, except in delete_dimensions and clear_values, which take the rows or range itself so the call shows what goes | spreadsheets |
manage_chart | Add, update, move, delete or list charts and slicers. A chart floats above the grid, so adding one overwrites nothing, and its data is named in A1, one range per series. A listing reports which charts have lost their series — what deleting a charted column does, and what nothing in Sheets tells you | spreadsheets |
manage_pivot_table | Add, update, delete or list pivot tables, with groups by date or number ranges, filters and calculated values. Columns are named in A1 or by their heading, never by counting, and every result reports the rectangle the table covers right now: the size is computed from the data rather than chosen. A listing reads every rule back in the spelling the tool takes | spreadsheets |
connect_data_source | Off by default: connect a BigQuery query or table through Connected Sheets. Google makes a sheet for it and runs the query, charged to the Cloud project you name, now and on every refresh | spreadsheets, bigquery.readonly |
manage_data_source | Off by default: refresh one Connected Sheets data source, cancel a refresh, or list what is connected. get_spreadsheet already says whether a spreadsheet has one, with no extra scope | spreadsheets, bigquery.readonly |
read_cell_comments | The comment threads on a spreadsheet's cells: the cell each is on now, open or resolved, who it is assigned to, and every post. A thread follows its cell as rows move, and one whose row was deleted is still listed, without a cell | spreadsheets |
manage_cell_comment | Comment on a cell, reply, edit a post, resolve or reopen. Google emails an assignee, and may notify an address the text names, which is how this server reaches someone outside the spreadsheet | spreadsheets |
manage_sheet | Add, rename, duplicate, copy to another spreadsheet, hide, unhide, reorder, resize, freeze or color a sheet | spreadsheets |
edit_dimensions | Insert, move, resize, auto-size, group, ungroup, hide or unhide rows and columns | spreadsheets |
delete_dimensions | Destructive, off by default: remove rows or columns and the data on them, having counted what that is | spreadsheets |
clear_values | Destructive, off by default: clear a range's values and keep its formatting, notes and validation rules | spreadsheets |
delete_sheet | Destructive, off by default: delete a sheet and everything on it, having counted what that is | spreadsheets |
delete_cell_comment | Destructive, off by default: delete a comment thread with its replies, or one reply. Resolving keeps it, and is usually what is wanted | spreadsheets |
delete_data_source | Destructive, off by default: delete a Connected Sheets data source, the sheet Google made for it, and everything on that sheet; Google unlinks what was built on the source. The call names that sheet's title. Needs no BigQuery scope, so it reaches a source somebody else connected | spreadsheets |
The destructive tools are not registered at all unless GSHEETS_ENABLE_DESTRUCTIVE=true, and each still needs confirm: true on the call. connect_data_source and manage_data_source are not registered unless GSHEETS_ENABLE_DATA_SOURCES=true, which is also what makes login ask for the BigQuery scope. Connected Sheets needs a Cloud project with BigQuery and billing before it does anything, so asking everyone for that scope would be the wrong default.
Resources
For a client that attaches a spreadsheet rather than calling a tool. There is no static list, since listing a person's spreadsheets is a Drive listing, and no subscriptions, since the Sheets API has no push.
| URI | What it is |
|---|---|
gsheets://{spreadsheet} | The card: every sheet with its exact title, id and size, plus named ranges, tables and protected ranges. Reads no cells |
gsheets://{spreadsheet}/{sheet} | That sheet's used range as CSV — the rows and columns holding something, not the sheet's allocated size. The sheet title is percent-encoded |
Install
go install github.com/mmedum/google-sheets-mcp/v4/cmd/google-sheets-mcp@latestOr take an archive for Linux, macOS or Windows, on amd64 or arm64, from the latest release, and verify it before you run it.
Claude Desktop users can open the .mcpb bundle from the same release. It installs the server and asks for the settings a client's configuration would carry: your OAuth client JSON, the profile, read-only, the destruct
Only the beginning is shown; read the rest in the repo