Gws MCP Server
Google Tasks, Calendar, and Drive management with enforced human-in-the-loop write approval.
Data last scanned today · Reviewed today
Overview
Gws MCP Server is a local, self-contained tool set for managing Google Tasks, Calendar, and Drive through the Model Context Protocol. Unlike remote-hosted alternatives, this server operates locally via stdio, ensuring your prompts remain private and your data access is managed through your own OAuth credentials stored securely in your OS keyring. The server emphasizes safety through a rigorous write-approval invariant. Any operation that mutates data—such as creating tasks, updating calendar events, or moving Drive files—requires explicit human confirmation before execution. This process is enforced through MCP elicitation or a two-step fallback mechanism, ensuring the AI model cannot trigger changes without your direct, real-time consent.
Our verdict
With a security score of 35/100, this project is classified as high-risk. This rating reflects the fact that it is a community-maintained project that has not yet been editorially reviewed, and it lacks the maturity of a long-standing repository with significant community engagement. While the server is designed with safety features like mandatory human-in-the-loop approvals for write actions, it is currently in alpha status (v0.1.0) and should be used cautiously by those comfortable with experimental, locally-run software.
- Requires manual human approval for all write operations.
- Uses local OS keyring for secure token storage.
- Zero direct dependencies minimize supply-chain risk.
- Runs locally via stdio with no external hosting.
- High risk profile due to alpha status and limited review.
- Authentication and read-only modes lack third-party verification.
- Zero GitHub stars indicate limited community usage and testing.
Tools
| Tool | Description | Risk |
|---|---|---|
| list_task_lists | Lists all task lists for the user. | low |
| list_tasks | Lists tasks within a specific task list. | low |
| get_task | Retrieves the details of a specific task. | low |
| create_task | Creates a new task in a specified task list. | medium |
| update_task | Updates the details of an existing task. | medium |
| complete_task | Marks a task as completed. | medium |
| move_task | Moves a task to a different position or list. | medium |
| delete_task | Deletes an existing task. | high |
| list_calendars | Lists the user's calendars. | low |
| list_events | Lists events from a calendar. | low |
Compatibility
| Client | Local | Docker | Remote | Read-only |
|---|---|---|---|---|
| ChatGPT | ||||
| Claude Desktop | ||||
| Cursor | ||||
| VS Code | ||||
| Windsurf |
Frequently asked questions
›How does the server handle write operations safely?
All mutating tools require explicit human approval via a UI prompt or a two-step confirmation process, ensuring the AI cannot execute writes autonomously.
›Does this server store my Google credentials in plain text?
No, your OAuth tokens are securely stored in your operating system's keyring, such as macOS Keychain, KDE Wallet, or Secret Service.
›Is it possible to restrict the server to specific Google services?
Yes, you can set the GWS_MCP_SERVICES environment variable to a comma-separated list of services like tasks, calendar, or drive to limit the exposed tools and requested OAuth scopes.
›Are my prompts shared with this server?
No, the server operates as a local stdio process and only processes tool calls; it never receives or sees the actual prompts you send to your MCP client.
›What happens if I try to delete a file in Google Drive?
The server treats delete operations as a 'trash' command rather than a hard delete to prevent accidental permanent data loss.
›What are the setup prerequisites for using this server?
You must create your own Google Cloud OAuth 2.0 Desktop app client, enable the Tasks, Calendar, and Drive APIs, and store the credentials JSON file at ~/.config/gws-mcp/credentials.json.
Badge
Maintain this server? Add the live badge to your README.