Skip to content
Back to search

google-mcp-server

Model Context Protocol server for Google Calendar and Google Tasks (read/write) using my published Google OAuth app; consumed by opencode

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/garretpatten--google-mcp-server/badge.svg)](/listings/garretpatten--google-mcp-server)

HTML

<a href="/listings/garretpatten--google-mcp-server"><img src="/api/listings/garretpatten--google-mcp-server/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

Prerequisites

- Node.js >= 24 - Google Cloud OAuth client (client ID and secret) — the same published app used by `system-scripts/backups`

Installation

1. **Clone and install**

   git clone https://github.com/garretpatten/google-mcp-server
   cd google-mcp-server
   npm install

2. **Configure OAuth** — copy `.env.example` to `.env` and set `GOOGLE_CLIENT_ID` and `GOOGLE_CLIENT_SECRET`.

3. **Authorize once** — run the interactive consent flow; the browser opens with the full read/write Calendar and Tasks scopes and the refresh token is written back to `.env`:

   npm run auth

4. **Build**

   npm run build

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 150 lines
  1. <!-- markdownlint-disable MD033 MD041 -->
  2. <p align="center">
  3. <img src="https://img.shields.io/badge/google%20mcp-server-4285F4?style=for-the-badge&logo=googlecalendar&logoColor=white" alt="Google MCP Server project badge" />
  4. </p>
  5. <h1 align="center">Google MCP Server</h1>
  6. <p align="center"><strong>Google Calendar and Google Tasks for <a href="https://opencode.ai">opencode</a>, over the Model Context Protocol.</strong></p>
  7. <p align="center">
  8. A stdio MCP server exposing <strong>read/write</strong> access to Google Calendar
  9. (personal, shared, and subscribed) and every Google Tasks list,<br />
  10. authenticating with a published Google OAuth app.
  11. </p>
  12. <p align="center">
  13. <a href="./LICENSE"><img src="https://img.shields.io/github/license/garretpatten/google-mcp-server?style=flat-square" alt="License" /></a>
  14. <img src="https://img.shields.io/badge/transport-stdio-34A853?style=flat-square&logo=modelcontextprotocol&logoColor=white" alt="stdio transport" />
  15. <img src="https://img.shields.io/badge/runtime-node%20%3E%3D%2024-339933?style=flat-square&logo=node.js&logoColor=white" alt="Node.js 24+" />
  16. </p>
  17. <p align="center">
  18. <a href="https://github.com/garretpatten/google-mcp-server/actions/workflows/tests.yaml"
  19. ><img src="https://img.shields.io/github/actions/workflow/status/garretpatten/google-mcp-server/tests.yaml?branch=master&label=tests&logo=github&style=flat-square" alt="Tests workflow status"
  20. /></a>
  21. <a href="https://github.com/garretpatten/google-mcp-server/actions/workflows/quality-checks.yaml"
  22. ><img src="https://img.shields.io/github/actions/workflow/status/garretpatten/google-mcp-server/quality-checks.yaml?branch=master&label=quality&logo=github&style=flat-square" alt="Quality checks workflow status"
  23. /></a>
  24. <a href="https://github.com/garretpatten/google-mcp-server/actions/workflows/security-guardrails.yaml"
  25. ><img src="https://img.shields.io/github/actions/workflow/status/garretpatten/google-mcp-server/security-guardrails.yaml?branch=master&label=security&logo=github&style=flat-square" alt="Security guardrails workflow status"
  26. /></a>
  27. </p>
  28. <!-- markdownlint-enable MD033 MD041 -->
  29. ---
  30. ## Overview
  31. [garretpatten/google-mcp-server](https://github.com/garretpatten/google-mcp-server) is a
  32. [Model Context Protocol](https://modelcontextprotocol.io) server that lets an AI agent
  33. read and organize Google Calendar and Google Tasks. It is consumed by the opencode
  34. configuration on this machine and reuses the same OAuth app as
  35. [system-scripts/backups](https://github.com/garretpatten/system-scripts).
  36. ## Features
  37. - **Calendars** — personal, shared, and subscribed calendars all surface through the
  38. Google Calendar `calendarList`.
  39. - List calendars and events (time ranges, text search), read single events.
  40. - Create, update, delete events; respond to invitations (RSVP).
  41. - **Tasks** — every task list is supported.
  42. - List task lists and tasks (completed/deleted/hidden filters), read tasks.
  43. - Create, update, complete, move, and delete tasks.
  44. - **Safe by default** — reads run without prompting; opencode asks before any write
  45. tool (create, update, delete, RSVP, move).
  46. - **Lightweight** — plain REST calls via `fetch` over stdio; no heavy Google client SDK.
  47. ## Quick start
  48. ### Prerequisites
  49. - Node.js >= 24
  50. - Google Cloud OAuth client (client ID and secret) — the same published app used by
  51. `system-scripts/backups`
  52. ### Installation
  53. 1. **Clone and install**
  54. ```sh
  55. git clone https://github.com/garretpatten/google-mcp-server
  56. cd google-mcp-server
  57. npm install
  58. ```
  59. 2. **Configure OAuth** — copy `.env.example` to `.env` and set `GOOGLE_CLIENT_ID` and
  60. `GOOGLE_CLIENT_SECRET`.
  61. 3. **Authorize once** — run the interactive consent flow; the browser opens with the
  62. full read/write Calendar and Tasks scopes and the refresh token is written back to
  63. `.env`:
  64. ```sh
  65. npm run auth
  66. ```
  67. 4. **Build**
  68. ```sh
  69. npm run build
  70. ```
  71. ## opencode integration
  72. Add the server to `opencode.jsonc`:
  73. ```jsonc
  74. "mcp": {
  75. "google": {
  76. "type": "local",
  77. "command": ["node", "/home/garret/Projects/google-mcp-server/dist/index.js"],
  78. "enabled": true
  79. }
  80. }
  81. ```
  82. Read tools are allowed without prompting; write tools are configured to ask in the
  83. opencode permission settings.
  84. ## Tools
  85. | Tool | Type | Description |
  86. | ----------------------- | ----- | -------------------------------------------------------- |
  87. | `calendar_list` | read | List accessible calendars (personal, shared, subscribed) |
  88. | `calendar_events` | read | List events in a calendar with time range/search |
  89. | `calendar_event` | read | Get a single event |
  90. | `calendar_create_event` | write | Create an event |
  91. | `calendar_update_event` | write | Update an event |
  92. | `calendar_delete_event` | write | Delete an event |
  93. | `calendar_respond` | write | Accept/decline an invitation (RSVP) |
  94. | `tasks_lists` | read | List task lists |
  95. | `tasks_list_tasks` | read | List tasks in a task list |
  96. | `tasks_create` | write | Create a task |
  97. | `tasks_update` | write | Update a task |
  98. | `tasks_complete` | write | Mark a task completed |
  99. | `tasks_move` | write | Move a task to another list/position |
  100. | `tasks_delete` | write | Delete a task |
  101. ## Security
  102. OAuth credentials live in the git-ignored `.env`. The server refreshes access tokens
  103. automatically and never logs secrets. `npm run auth` writes `.env` with owner-only
  104. (0600) permissions; if you create the file by hand, run `chmod 600 .env`. If the
  105. refresh token is revoked, run `npm run auth` again.
  106. See [SECURITY.md](SECURITY.md) for reporting a vulnerability.
  107. ## Development
  108. ```sh
  109. npm test
  110. npm run typecheck
  111. npm run lint:eslint
  112. ```
  113. ## License
  114. [MIT](LICENSE)

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.