Google Tasks vs Google Drive MCP Server
A side-by-side look at the Google Tasks and Google Drive MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
G
Google Drive MCP ServerWorkplace & Productivity · Local subprocess (stdio)Read and write Google Drive, Docs, Sheets, Slides and Calendar with markdown-to-Docs formatting and OAuth2. Local stdio server.56GoodAuth: oauth 2.0Verdict: choose Google Tasks for workplace & productivity work as a local process; choose Google Drive MCP Server for workplace & productivity as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Google Tasks when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
GOOGLE_TASKS_CLIENT_SECRET, GOOGLE_TASKS_TOKEN_PATH, GOOGLE_TASKS_OAUTH_PORT. - You want tools like
google_tasks_list_tasklists, google_tasks_get_tasklist, google_tasks_create_tasklist.
GChoose Google Drive MCP Server when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You have the keys it needs:
GDRIVE_MCP_OAUTH_PATH, GDRIVE_MCP_CUSTOM_THEMES_PATH. - You want tools like
drive_list_files, drive_search, drive_read_file.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | G Google Drive MCP Server | |
|---|---|---|
| Category | Workplace & Productivity | Workplace & Productivity |
| Quality signal | 55/100 · Good | 56/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Not declared |
| Required env vars | GOOGLE_TASKS_CLIENT_SECRETGOOGLE_TASKS_TOKEN_PATHGOOGLE_TASKS_OAUTH_PORT | GDRIVE_MCP_OAUTH_PATHGDRIVE_MCP_CUSTOM_THEMES_PATH |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 14 | 20 |
| Full listing | View Google Tasks | View Google Drive MCP Server |
Tools & capabilities
Google Tasks tools 14
google_tasks_list_tasklistsgoogle_tasks_get_tasklistgoogle_tasks_create_tasklistgoogle_tasks_update_tasklistgoogle_tasks_delete_tasklistgoogle_tasks_list_tasksgoogle_tasks_get_taskgoogle_tasks_create_taskgoogle_tasks_update_taskgoogle_tasks_complete_taskgoogle_tasks_reopen_taskgoogle_tasks_delete_task- +2 more on the listing page
Google Drive MCP Server tools 20
drive_list_filesList files/folders with filtering, pagination, and sortingdrive_searchSearch by name or content (full-text search)drive_read_fileRead file content by byte ranges. Auto-exports Workspace files, converts Office files to textdrive_get_file_infoMetadata for an ID: name, size, parent folder (resolved to its name), shared drive, capabilitiesdrive_create_fileCreate a new file with optional contentdrive_create_folderCreate a new folderdrive_update_fileUpdate file content or renamedrive_delete_fileDelete a file or folder (falls back to trash in shared drives when permanent delete is not permitted)drive_move_fileMove to a different folderdrive_copy_fileCopy a file, optionally to a different folderdrive_shareShare a file with a user (reader/writer/commenter)drive_list_permissionsList who has access to a file- +8 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Google Tasks
{
"mcpServers": {
"google-tasks": {
"command": "npx",
"args": [
"-y",
"-p",
"@girmmy/google-tasks-mcp-server",
"google-tasks-mcp-auth"
],
"env": {
"GOOGLE_TASKS_CLIENT_SECRET": "YOUR_GOOGLE_TASKS_CLIENT_SECRET_HERE",
"GOOGLE_TASKS_TOKEN_PATH": "YOUR_GOOGLE_TASKS_TOKEN_PATH_HERE",
"GOOGLE_TASKS_OAUTH_PORT": "YOUR_GOOGLE_TASKS_OAUTH_PORT_HERE"
}
}
}
}
Google Drive MCP Server
{
"mcpServers": {
"ibarcarty-mcp-server-google-drive": {
"command": "npx",
"args": [
"-y",
"@ibarcarty/mcp-server-google-drive"
],
"env": {
"GDRIVE_MCP_OAUTH_PATH": "YOUR_GDRIVE_MCP_OAUTH_PATH_HERE",
"GDRIVE_MCP_CUSTOM_THEMES_PATH": "YOUR_GDRIVE_MCP_CUSTOM_THEMES_PATH_HERE"
}
}
}
}
Frequently asked questions
Google Tasks is categorized under Workplace & Productivity and uses a local stdio subprocess. Google Drive MCP Server belongs to Workplace & Productivity and uses a local stdio subprocess. Pick Google Tasks for workplace & productivity work and Google Drive MCP Server for workplace & productivity.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Google Tasks has no declared pricing — check the project's own site. Google Drive MCP Server has no declared pricing — check the project's own site. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add google-tasks and ibarcarty-mcp-server-google-drive as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Google Tasks has a quality signal of 55/100 (Good) with 2 views, 0 installs and 1 GitHub stars. Google Drive MCP Server has 56/100 (Good) with 0 views, 0 installs and 0 GitHub stars.