Barie Google Sheets MCP Server
Model Context Protocol (MCP) server for Google Sheets and Google Drive discovery.
It supports listing spreadsheet-like files from Drive, and full read/write operations on native Google Sheets.
Install
uvx barie-google-sheets-mcp --help
Run
barie-google-sheets-mcp \
--access-token "YOUR_ACCESS_TOKEN" \
--refresh-token "YOUR_REFRESH_TOKEN" \
--client-id "YOUR_CLIENT_ID" \
--client-secret "YOUR_CLIENT_SECRET"
Optional:
--expiry: token expiry timestamp in ISO format--scopes: JSON array string, for example:["https://www.googleapis.com/auth/drive","https://www.googleapis.com/auth/spreadsheets"]
MCP Client Config Example
{
"mcpServers": {
"google_sheets": {
"command": "uvx",
"args": [
"barie-google-sheets-mcp",
"--access-token",
"YOUR_ACCESS_TOKEN",
"--refresh-token",
"YOUR_REFRESH_TOKEN",
"--client-id",
"YOUR_CLIENT_ID",
"--client-secret",
"YOUR_CLIENT_SECRET"
]
}
}
}
If you need to force-refresh package resolution in long-lived environments, you can add --refresh and --reinstall before barie-google-sheets-mcp.
Tool Names
The server exposes these MCP tools:
list_spreadsheetsget_spreadsheetcreate_spreadsheetget_sheet_dataupdate_cellsappend_valuesadd_columnsadd_rowsbatch_updatebatch_update_cellscopy_sheetcreate_sheetfind_in_spreadsheetget_multiple_sheet_dataget_multiple_spreadsheet_summaryget_sheet_formulaslist_folderslist_sheetsrename_sheetsearch_spreadsheetsshare_spreadsheet
File Format Behavior
list_spreadsheetscan return Google Sheets and some spreadsheet-like Drive files.- Read/write tools (
get_sheet_data,update_cells,append_values, etc.) work only with native Google Sheets (application/vnd.google-apps.spreadsheet). - For
.xlsx,.xls, or.csv, convert to Google Sheets first, then use the converted file ID.
If a non-native spreadsheet is passed to a Sheets-only tool, the server returns a clear conversion-required error.
Publish
cd google_sheets
python -m build
python -m twine check dist/*
python -m twine upload dist/*
Metadata
Release files for barie-google-sheets-mcp 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| barie_google_sheets_mcp-0.1.2.tar.gz | 10.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| barie_google_sheets_mcp-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 21.6 kB
Release files / barie_google_sheets_mcp-0.1.2.tar.gz
| Download URL | barie_google_sheets_mcp-0.1.2.tar.gz |
|---|---|
| Size | 10.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f92e335dd6c9a0a228d64e4a9219fa735c8f383b4cbb08e9043519150379bd32
|
|
BLAKE2b-256 checksum How to use checksums |
c4a1177729d01ae24751b9aaedc0ae3f6de43f8ec42e6501ce123982f1f36632
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.9
|
Release files / barie_google_sheets_mcp-0.1.2-py3-none-any.whl
| Download URL | barie_google_sheets_mcp-0.1.2-py3-none-any.whl |
|---|---|
| Size | 11.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
dba4ef9a195f63c730fd3180f6167814669433912623ed50831cd51ca366d42e
|
|
BLAKE2b-256 checksum How to use checksums |
209a65f03f4968ee6f678b0b1393f8e52259e15aad83747bb0db76f4e0e7646a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.9
|
Security for barie-google-sheets-mcp 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.