Memungkinkan AI client untuk melakukan sinkronisasi, pencarian, dan pengelolaan event Google Calendar melalui local store dan MCP server.
Juga dikenal sebagai WireCatLabs/gcal-cli, gcal-cli, @wirecat/gcal-cli
- Stars
- 3
- Tools
- —
- Unduhan, 30 hari
- —
- Versi terbaru
- 0.28.0
- Commit terakhir
- 14 Nov 2026
- Lisensi
- Apache-2.0
Apa itu WireCat Google Calendar MCP?
Memungkinkan AI client untuk melakukan sinkronisasi, pencarian, dan pengelolaan event Google Calendar melalui local store dan MCP server.
Ringkasan dibuat dari README proyek
Tentang WireCat Google Calendar MCP server
WireCat Google Calendar memungkinkan AI agent untuk berinteraksi dengan data Google Calendar Anda melalui local store. Dengan menyinkronkan kalender ke komputer Anda, tool ini memungkinkan agent untuk menampilkan, mencari, dan mengelola event tanpa memerlukan koneksi jaringan untuk setiap operasi pembacaan. Setup ini dirancang untuk developer yang menggunakan terminal-based agent seperti Claude Code dan Gemini CLI, atau client yang kompatibel dengan MCP seperti Claude Desktop dan Cursor.
Untuk menggunakan server ini, Anda harus membuat Google Cloud Console desktop app sendiri dan menyediakan file JSON client secret. Pengguna dapat memilih antara akses read-only atau izin tulis penuh untuk membuat, memindahkan, atau menghapus event. Sistem ini menyertakan fitur keamanan seperti meminta izin sebelum menghapus event dan mencegah pengiriman email otomatis ke peserta rapat kecuali diizinkan secara eksplisit. Sistem ini mendukung beberapa akun Google melalui sistem profil dan bahkan dapat melakukan pencarian semantik jika Anda mengunduh model lokal.
Apa yang bisa Anda lakukan dengannya
- 1Mencari ketersediaan waktu rapatMinta agent untuk mencari slot waktu kosong bagi beberapa orang dalam rentang waktu tertentu.
- 2Mencari event terdahuluMinta agent untuk menemukan rapat spesifik di masa lalu menggunakan kata kunci atau makna tertentu.
- 3Menjadwalkan janji temu baruInstruksikan agent untuk memesan waktu dan judul tertentu untuk event kalender baru.
- 4Mengidentifikasi konflik jadwalGunakan agent untuk memindai semua akun yang tersinkronisasi guna menemukan rapat yang bentrok.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Cara menginstal WireCat Google Calendar MCP
Format diverifikasi 10 Nov 2026Tambahkan ke CursorTambahkan ke GooseInstal WireCat Google Calendar MCP di Claude Code
$ claude mcp add gcal-cli -- npx -y @wirecat/gcal-cliInstal WireCat Google Calendar MCP di Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"gcal-cli": {
"command": "npx",
"args": [
"-y",
"@wirecat/gcal-cli"
]
}
}
}Instal WireCat Google Calendar MCP di VS Code
.vscode/mcp.json
{
"servers": {
"gcal-cli": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@wirecat/gcal-cli"
]
}
}
}Instal WireCat Google Calendar MCP di VS Code CLI
$ code --add-mcp '{"name":"gcal-cli","type":"stdio","command":"npx","args":["-y","@wirecat/gcal-cli"]}'Instal WireCat Google Calendar MCP di Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"gcal-cli": {
"command": "npx",
"args": [
"-y",
"@wirecat/gcal-cli"
]
}
}
}Instal WireCat Google Calendar MCP di Codex
$ codex mcp add gcal-cli -- npx -y @wirecat/gcal-cliInstal WireCat Google Calendar MCP di Codex config.toml
~/.codex/config.toml
[mcp_servers.gcal-cli] command = "npx" args = ["-y", "@wirecat/gcal-cli"]
Instal WireCat Google Calendar MCP di Gemini CLI
$ gemini mcp add -s user gcal-cli npx -- -y @wirecat/gcal-cliInstal WireCat Google Calendar MCP di Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"gcal-cli": {
"command": "npx",
"args": [
"-y",
"@wirecat/gcal-cli"
]
}
}
}Pengecekan otomatis
Berjalan 14 Nov 2026Laporan lengkap →Lolos checks otomatis kami. Ini bukan audit keamanan: baca kodenya dan berikan server akses paling terbatas yang dibutuhkannya. Cara kerja checks
- Source repository terhubung dan dapat dijangkauwirecatlabs/gcal-cli is public and reachablegithub.com/wirecatlabs/gcal-cli ↗Lolos
- Nama paket mencantumkan repositori ini sebagai sumbernya@wirecat/gcal-cli names wirecatlabs/gcal-cli as sourcenpmjs.com/package/@wirecat/gcal-cli ↗Lolos
- Provenance build (atestasi Sigstore)Sigstore attestation for @wirecat/gcal-clinpmjs.com/package/@wirecat/gcal-cli/v/0.26.0#provenance ↗Lolos
- Lisensi open source (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Lolos
- Ada commit atau release dalam satu tahun terakhirLast commit or release 2026-11-14github.com/wirecatlabs/gcal-cli ↗Lolos
- OpenSSF ScorecardTidak diperiksa
- Nama package tidak mirip dengan package populerNo popular package one edit away from @wirecat/gcal-cliLolos
- Tidak ada advisory kritis pada paket atau dependensinyathe package checked; no critical advisoryosv.dev ↗Lolos
- Tidak ada instruksi tersembunyi untuk model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersLolos
- Tools yang bersifat destruktif telah diberi labelTidak diperiksa
- Endpoint remote merespons handshake MCPTidak diperiksa
README
Lihat di GitHubgcal — Google Calendar CLI for AI agents
gcal copies the calendars you own into the local WireCat store. Then you list, show and search
events, the people in them and their Drive files, with no network. With write access it also creates, changes, moves
and deletes events and answers invitations. A delete asks first. Mailing other people is off until you allow it.
An example conversation (invented people and events, illustrative output):
You: Use gcal. When can I meet Ana for 30 minutes this week?
Agent: (runs gcal personal calendars busy person:ana@example.com --duration-minutes 30)
You both are free on Tuesday 10:00–10:30, Wednesday 14:00–15:00 and Thursday 10:00–12:00.
You: Book Tuesday, 30 minutes, "Example planning". Do not email her.
Agent: Draft: "Example planning", Tuesday 10:00–10:30, with ana@example.com, no email sent. Create it?
You: Yes.
Quick start
You need a Google sign-in client of your own for now. Make one
in Google Cloud Console, as a Desktop app, and save its JSON file as ~/client_secret.json with chmod 600.
npm install -g @wirecat/gcal-cli
gcal skill install # the agent skill, for Claude Code, Codex and Gemini CLI
gcal personal session start --client-file ~/client_secret.json # sign in to Google in the browser, read-only
gcal personal sync # copy the calendars you own, then only what changed
gcal personal events list # your events from today on, earliest first
personal is a profile: a name you choose for one Google account. It is the first word of every command that uses an
account. A first sync lists a year back and three months ahead. A big one goes on over several runs: run sync again
when it says partial.
You need Node.js 22.16 or a later 22.x, or Node.js 24 or later, on macOS, Linux or Windows. Bun also works. Try it
without installing: npx @wirecat/gcal-cli --help. If gcal is not found, run gcal doctor. It needs no network and
shows what is set up. gcal guide gives step-by-step scenarios.
More: installation (wirecat.dev).
What you can do
See what is coming. "Use gcal. What is on my calendar this week?"
gcal personal events list
Find an event. "When did we plan the roadmap review?" Search runs on the local copy. It matches words, and meaning too once you download a model.
gcal personal search events roadmap planning
Find a time for everyone. Ask Google when people are busy, and get the stretches free for all of them. Nothing is stored.
gcal personal calendars busy person:ana@example.com --duration-minutes 30 --hours 10:00-16:00
More:
- Show one event with its attendees, Drive files and history:
gcal personal events show event:42. - Link a person to the same person in Telegram, WhatsApp or MAX:
gcal personal people link email:ana@example.com telegram:12345. - Create, change and delete events, repeating ones included, and answer invitations. Sign in again with
session start --grant writefirst. - Call any Google Calendar API v3 method by name with
gcal api.
More: use it (wirecat.dev).
For AI agents
Your agent. Your calendar. Your rules.
- An agent with a terminal — Claude Code, Codex, Gemini CLI, OpenClaw or Hermes Agent. It runs
gcalitself. The skill is the agent's instruction sheet: it explains the commands and the limits.gcal skill installwrites it. - An app with no terminal — Claude Desktop, Cursor and other MCP clients. Connect the profile's MCP server,
gcal personal mcp serve.gcal personal mcp configprints the entry to paste. - ChatGPT or Claude in a browser or on your phone — through your own HTTPS tunnel:
gcal personal mcp serve --http. Step by step (wirecat.dev).
gcal skill install # for Claude Code, Codex, Gemini CLI and OpenClaw
gcal personal mcp add claude-code --allow-writes # or: codex
gcal personal mcp check # start the server once, as the agent will
The server offers writing tools, so mcp add stops until you pass --allow-writes. The profile's permissions decide
what an agent may change; gcal personal config set permissions.api readonly keeps it to reads. Text from an invitation
is marked untrusted: it is data for the agent, never instructions. Commands that set up the sign-in or the agent link,
api call and emptying a calendar are never offered to an agent.
With --json, every command prints one JSON value, and an error comes as JSON with a code to branch on.
More: agents (wirecat.dev), settings and permissions (wirecat.dev).
Why this tool
- Your calendar is on your computer. It sits in the same store as the messages, documents and meetings of the other WireCat tools. An agent can answer "what did we agree with Ana" across all of them.
- Reads need no network after a sync. A meeting's passcode or PIN is never stored or printed.
- Every write is guarded. It never overwrites a change made in Google since the last sync. A delete asks first. It never mails attendees unless you allow it.
- Built for agents. A skill, an MCP server, one JSON form and exit codes a script can branch on.
Main features
- Incremental sync. After the first sync,
syncasks Google only for what changed.gcal personal store statusshows how far each calendar is. - Repeating events. Each occurrence is stored one by one, cancelled ones included.
- What changed.
events list changed_at>=2026-10-25lists the events that are new, moved or cancelled since a date. - All accounts in one list.
events list --source alllists the events of every Google account you signed in to, and says which accounts it read. - Meetings that overlap.
events list overlapping:true --source allfinds the meetings that clash, also across accounts. - Search by meaning.
gcal models download e5-smallfetches a small model once.sync --embedthen indexes new events with it. - Search in Google.
search events --backend serverasks Google's own search. It also finds events outside the synced span.--backend bothasks the store and Google together. - One search over everything.
search all roadmapfinds your meetings beside the chats that other WireCat tools stored and your notes, and says which accounts it read. - Every Google Calendar method.
gcal apireaches each one, under its own permission key.
Sign-in and profiles
Each profile is one Google account. No command ever picks a profile for you; gcal session list lists them.
gcal personal session start --client-file ~/client_secret.json # read-only
gcal personal session start --grant write # also create, change and delete events
gcal personal session start --grant write,sharing # also see and change who can see a calendar
gcal personal session status --check # ask Google whether the sign-in still works
GCAL_PROFILE=personal names the profile for a whole shell session. The sign-in is kept in the system keyring. Where
the keyring fails, gcal uses a private file and says so once. It never asks.
More: sign in (wirecat.dev).
Settings and permissions
Settings live in one config.json; gcal personal config show lists them. Permissions say what each command may do:
allow, ask, readonly or deny.
| Permission | What it covers | Default |
|---|---|---|
events.create, update, move, respond |
the event writes that are easy to undo | allow |
events.delete |
deleting an event | ask |
events.notify |
Google mails the other attendees | deny |
events.delete.series |
deleting every occurrence of a repeating event | deny |
sharing.notify |
Google mails the person a calendar is shared with | deny |
Sharing a calendar asks first. Over MCP nobody can answer a question, so ask lets a command run. An agent can then
share a calendar without asking you. To stop it, run gcal personal config set permissions.api.calendar.acl deny.
gcal personal config set permissions.api readonly # reads only, every method
gcal personal config set permissions.events.create ask # ask before each new event
gcal personal events create 3 --title 'Example planning' --start-time 2026-11-02T10:00 --end-time 2026-11-02T10:30 --dry-run
--dry-run shows the permission a command needs and does nothing. GCAL_READ_ONLY=1 refuses every write.
More: settings (wirecat.dev).
Limits
- Only the calendars you own sync at first.
gcal personal calendars listshows the rest, andgcal personal calendars sync 3adds calendar 3. gcalhas no Google app of its own yet. Sign-in needs your own client.- A Google app in Testing mode ends sign-ins after seven days. Sign in again, or publish the app.
calendars busyshows a person's busy times only when their calendar is shared with you or your organization.- Google's change notifications (
watch) are not offered: they need a public web address.
What is planned is on the roadmap (wirecat.dev).
Security
- Your event data goes only to Google. The sign-in is kept in the system keyring, or in a file only you can read.
- No command, error, log or run record shows a token or the client secret.
- A meeting's passcode or PIN is never stored. A join link is kept without its query string.
- A write never mails attendees, and a delete never runs unasked, unless you allow it.
gcalrefuses an OAuth client file that other users of the computer can read.- Permissions guard against an agent that a message talked into a change. They do not stop an agent that wants to get around them: for that, use a sandbox or a separate user.
More: security (wirecat.dev). Report a vulnerability as SECURITY.md says.
When it does not work
gcal doctor # what is set up; no network, no keyring
gcal personal session status --check # does Google still accept the sign-in
gcal personal sync --trace # the connection log, never content
gcal personal runs list # failed runs are kept
More: when something goes wrong (wirecat.dev).
Documentation
Each page is also on wirecat.dev/en/docs/gcal. Below are the sources in this repository.
| Section | Pages |
|---|---|
| Start | overview · installation · use it · ChatGPT or Claude in the browser |
| Reference | all commands · settings and permissions |
| If something is wrong | when something goes wrong · security |
| Project | roadmap · comparison with other tools |
| Changes | CHANGELOG.md |
For developers: design, tests and the rules for agents in AGENTS.md.
Development
pnpm install
pnpm lint && pnpm typecheck && pnpm test
pnpm build && pnpm smoke:node # the built command: the bundle users install
pnpm build && pnpm smoke:bun # the same under Bun
pnpm generate # rewrite the generated files
pnpm release:check # every check CI runs
The shared part — output streams, error codes, the keyring, the store, search and MCP — lives in
@wirecat/cli-base and its sibling library cli-core.
Part of WireCat
gcal is part of WireCat, an open-source, local-first context layer for AI agents. tg-cli and max-cli bring Telegram and MAX into the same local store. Start with one tool. Add more context when you need it. Your context. Any agent.
Questions and setup help: join the WireCat Discord. Bugs go to this repository's issues.
Contributing and license
Pull requests, bug reports and ideas go to issues.
Apache License 2.0 — LICENSE.
Pertanyaan tentang WireCat Google Calendar MCP
Bagaimana cara menambahkan WireCat Google Calendar MCP ke Claude Code?
Jalankan claude mcp add gcal-cli -- npx -y @wirecat/gcal-cli di terminal Anda. Tambahkan --scope user agar tersedia di semua proyek.
Bagaimana cara menambahkan WireCat Google Calendar MCP ke Cursor?
Buka ~/.cursor/mcp.json dan tambahkan server di bawah mcpServers, menggunakan config Cursor yang ditunjukkan di bagian instalasi di atas.
Bagaimana cara menggunakan ini dengan Claude Desktop atau Cursor?
Hubungkan MCP server dari profil tersebut menggunakan command gcal personal mcp serve.
Apakah agent membutuhkan koneksi internet untuk mencari kalender saya?
Tidak, setelah kalender disinkronkan ke local WireCat store, pencarian akan berjalan secara lokal tanpa memerlukan jaringan.
Apakah AI agent bisa mengirim email ke peserta rapat saya?
Secara default, fitur mengirim email ke orang lain dinonaktifkan kecuali Anda mengizinkannya secara eksplisit di pengaturan.