drive_search_filesLABSCO SUMMARY
Three Workspace apps behind one authorisation.
Drive, Docs and Sheets usually arrive as three connectors with three sets of credentials. One OAuth pass covers all three here, so a request that finds a file, reads it, and writes the summary into a spreadsheet stays a single conversation.
What it is
A Python MCP server over three Google Workspace services — Drive, Docs and Sheets. It runs on stdio by default and can also be served over SSE or WebSocket, and installs in one line with uvx.
What you get
- Drive searched by query, with the number of results per page under your control
- Folders created in Drive
- Documents created, read back as content, and updated in place
- Spreadsheets created, cell ranges read, and values written back
- Stdio, SSE or WebSocket transport, so the same server fits a desktop client or a remote setup
Requirements
uvx mcp-google-suite, or pip install mcp-google-suite. On the Google side: enable the Drive, Docs and Sheets APIs, create OAuth credentials, save them as ~/.google/oauth.keys.json and sign in once with uvx mcp-google-suite auth (the README writes mcp-google auth, but the command the package installs is mcp-google-suite). GOOGLE_APPLICATION_CREDENTIALS and GOOGLE_OAUTH_CREDENTIALS point the server at those files.
Setup effort
One command plus credentials — uvx mcp-google-suite, then supply credentials
USE CASES
01
Finding the file someone mentioned in passing
Search Drive by query and page through the matches, instead of guessing which folder it went into.
02
Writing notes up as a real document
Create the Doc, put the text in it, and update the same document as the draft changes.
03
Reading a document you were sent
Pull the content into the conversation so it can be summarised or checked against something else.
04
Filing a new set of numbers
Create the spreadsheet and write values into the range you name.
05
Answering a question from a sheet you already keep
Read the values for a range and work from them, rather than exporting the sheet first.
06
Keeping a project's files together
Create the folder the new material belongs in before anything is written to Drive.
8 tools
Listed in project docs. Your client may show a different list.
drive_create_folderdocs_createdocs_get_contentdocs_update_contentsheets_createsheets_get_valuessheets_update_valuesBEFORE YOU INSTALL
What to know first
Tools you get
8 tools named in the project's documentation.
Requires
- uvx on PATH
- GOOGLE_APPLICATION_CREDENTIALS in your environment
- GOOGLE_OAUTH_CREDENTIALS in your environment
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
In the Google Cloud Console, enable the Drive, Docs and Sheets APIs
Create OAuth 2.0 credentials and save them as ~/.google/oauth.keys.json
Sign in once with uvx mcp-google-suite auth (the README writes mcp-google auth; the command the package installs is mcp-google-suite, and auth is its sign-in subcommand)
TERMINAL
mcp-google-suiteMCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"mcp-google-suite": {
"command": "uvx",
"args": [
"mcp-google-suite"
],
"env": {
"GOOGLE_APPLICATION_CREDENTIALS": "~/.google/server-creds.json",
"GOOGLE_OAUTH_CREDENTIALS": "~/.google/oauth.keys.json"
}
}
}
}Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"mcp-google-suite": {
"command": "python",
"args": [
"-m",
"mcp_google_suite"
],
"env": {
"GOOGLE_APPLICATION_CREDENTIALS": "~/.google/server-creds.json",
"GOOGLE_OAUTH_CREDENTIALS": "~/.google/oauth.keys.json"
}
}
}
}This form runs the pip-installed package, so run pip install mcp-google-suite first; with uvx, use the Cursor configuration instead.
