MCP Google Suite
# MCP Google Workspace Server
[](https://github.com/adexltd/mcp-google-suite/actions/workflows/ci.yml)
[](https://codecov.io/gh/adexltd/mcp-google-suite)
[](https://badge.fury.io/py/mcp-google-suite)
[](https://opensource.org/licenses/MIT)
[](https://github.com/psf/black)
A Model Context Protocol (MCP) server enabling AI agents to interact with Google Workspace (Drive, Docs, and Sheets) services.
## 🌟 Features
- Google Drive: Search files, create folders
- Google Docs: Create, read, update documents
- Google Sheets: Create spreadsheets, read/write cell values
- Multiple transport modes: stdio (default), SSE, WebSocket
- MCP-compatible client support (Cursor, etc.)
## 📋 Installation
### Using uv (recommended)
```bash
uvx mcp-google-suite
```
### Using pip
```bash
pip install mcp-google-suite
```
### Development setup
```bash
# Clone and install
git clone git@github.com:adexltd/mcp-google-suite.git && cd mcp-google-suite
uv venv && source .venv/bin/activate # or .venv\Scripts\activate on Windows
uv pip install -e .
```
## 🔧 Configuration
### Configure for MCP Clients
Add to your client settings (e.g. Cursor, Claude):
Using uvx (recommended):
```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"
}
}
}
}
```
Using pip installation:
```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"
}
}
}
}
```
### Google OAuth Setup
1. Visit [Google Cloud Console](https://console.cloud.google.com)
2. Enable Drive, Docs, and Sheets APIs
3. Create OAuth 2.0 credentials
4. Save as `~/.google/oauth.keys.json`
5. Run `mcp-google auth` to authenticate
### Available Tools
#### Drive Operations
- `drive_search_files`: Search files in Google Drive
- `query` (string, required): Search query
- `page_size` (integer, optional): Number of results to return
- `drive_create_folder`: Create a new folder
- `name` (string, required): Folder name
- `parent_id` (string, optional): Parent folder ID
#### Docs Operations
- `docs_create`: Create a new document
- `title` (string, required): Document title
- `content` (string, optional): Initial content
- `docs_get_content`: Get document content
- `document_id` (string, required): Document ID
- `docs_update_content`: Update document content
- `document_id` (string, required): Document ID
- `content` (string, required): New content
#### Sheets Operations
- `sheets_create`: Create a new spreadsheet
- `title` (string, required): Spreadsheet title
- `sheets` (array, optional): Sheet names
- `sheets_get_values`: Get cell values
- `spreadsheet_id` (string, required): Spreadsheet ID
- `range` (string, required): A1 notation range
- `sheets_update_values`: Update cell values
- `spreadsheet_id` (string, required): Spreadsheet ID
- `range` (string, required): A1 notation range
- `values` (array, required): 2D array of values
## 🛠️ Development
```bash
# Install dev dependencies
uv pip install -e ".[dev]"
# Setup pre-commit hooks
pre-commit install
# Run tests
pytest
# Format code
black . && ruff check --fix .
```
## 🔍 Debugging
Use the MCP Inspector for interactive testing:
```bash
# Using uvx
npx @modelcontextprotocol/inspector uvx mcp-google
# For development
cd path/to/mcp-google-suite
npx @modelcontextprotocol/inspector uv run mcp-google
```
## 📚 Resources
- [Documentation](https://github.com/adexltd/mcp-google-suite/wiki)
- [MCP Inspector](https://github.com/modelcontextprotocol/inspector)
- [Pre-commit Hooks](https://pre-commit.com)
- [Google Cloud Console](https://console.cloud.google.com)
## 🤝 Contributing
Please read [CONTRIBUTING.md](CONTRIBUTING.md) for details on our code of conduct and the process for submitting pull requests.
## 🔒 Security
See [SECURITY.md](SECURITY.md) for reporting vulnerabilities and best practices.
## 📄 License
MIT License - See [LICENSE](LICENSE) file for details.
TDQS
Scored across 8 tools
Every tool has a clearly distinct purpose with no ambiguity. The tools are organized by service (Docs, Drive, Sheets) and specific actions (create, get, update, search), making it easy for an agent to select the correct tool without confusion.
Tool names follow a consistent verb_noun pattern with service prefixes (e.g., docs_create, drive_search_files). All tools use snake_case uniformly, and the naming convention is predictable and readable throughout the set.
With 8 tools, the count is well-scoped for the Google Suite domain. Each tool earns its place by covering essential operations across multiple services (Docs, Drive, Sheets), avoiding both bloat and thin coverage.
The tool set provides good CRUD/lifecycle coverage for Docs and Sheets (create, get, update) and basic Drive operations (create folder, search). Minor gaps exist, such as missing delete operations or more advanced features like sharing permissions, but agents can work around these for core workflows.