AIクライアントがローカルストアとMCP serverを介して、Google Calendarの予定を同期、検索、管理できるようにします。
別名 WireCatLabs/gcal-cli, gcal-cli, @wirecat/gcal-cli
- スター
- 3
- ツール
- —
- ダウンロード数(30日間)
- —
- 最新バージョン
- 0.28.0
- 最終コミット
- 2026年11月14日
- ライセンス
- Apache-2.0
WireCat Google Calendar MCPとは
AIクライアントがローカルストアとMCP serverを介して、Google Calendarの予定を同期、検索、管理できるようにします。
プロジェクトのREADMEから生成された概要
WireCat Google Calendar MCP server について
WireCat Google Calendarを使用すると、AIエージェントがローカルストアを介してGoogle Calendarのデータとやり取りできるようになります。カレンダーをコンピュータに同期することで、読み取り操作のたびにネットワーク接続を必要とせずに、エージェントが予定の一覧表示、検索、管理を行うことが可能になります。このセットアップは、Claude CodeやGemini CLIのようなターミナルベースのエージェント、またはClaude DesktopやCursorなどのMCP対応クライアントを使用する開発者向けに設計されています。
このserverを使用するには、独自のGoogle Cloud Consoleデスクトップアプリを作成し、JSON形式のクライアントシークレットファイルを提供する必要があります。ユーザーは、読み取り専用アクセスか、予定の作成、移動、削除ができるフル書き込み権限かを選択できます。システムには、予定を削除する前に許可を求めたり、明示的に許可されない限り出席者への自動メール送信を防いだりするなどの安全機能が含まれています。プロファイルシステムを通じて複数のGoogleアカウントをサポートしており、ローカルモデルをダウンロードすればセマンティック検索を実行することも可能です。
できること
- 1会議の空き時間を探す特定の時間枠内で、複数の人の空き時間をエージェントに探させます。
- 2過去の予定を検索するキーワードや意味に基づいて、過去の特定の会議をエージェントに特定させます。
- 3新しい予定をスケジュールする新しいカレンダー予定の時間とタイトルを指定して、エージェントに予約させます。
- 4スケジュールの競合を特定する同期されたすべてのアカウントをエージェントにスキャンさせ、重複している会議を見つけさせます。
プロジェクトの README から作成されています。すべてのユースケースは、その引用と照らし合わせて確認されています。
WireCat Google Calendar MCPのインストール方法
フォーマット検証日 2026年11月10日Cursor に追加Gooseに追加Claude CodeにWireCat Google Calendar MCPをインストール
$ claude mcp add gcal-cli -- npx -y @wirecat/gcal-cliCursorにWireCat Google Calendar MCPをインストール
~/.cursor/mcp.json
{
"mcpServers": {
"gcal-cli": {
"command": "npx",
"args": [
"-y",
"@wirecat/gcal-cli"
]
}
}
}VS CodeにWireCat Google Calendar MCPをインストール
.vscode/mcp.json
{
"servers": {
"gcal-cli": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@wirecat/gcal-cli"
]
}
}
}VS Code CLIにWireCat Google Calendar MCPをインストール
$ code --add-mcp '{"name":"gcal-cli","type":"stdio","command":"npx","args":["-y","@wirecat/gcal-cli"]}'Claude DesktopにWireCat Google Calendar MCPをインストール
claude_desktop_config.json
{
"mcpServers": {
"gcal-cli": {
"command": "npx",
"args": [
"-y",
"@wirecat/gcal-cli"
]
}
}
}CodexにWireCat Google Calendar MCPをインストール
$ codex mcp add gcal-cli -- npx -y @wirecat/gcal-cliCodex config.tomlにWireCat Google Calendar MCPをインストール
~/.codex/config.toml
[mcp_servers.gcal-cli] command = "npx" args = ["-y", "@wirecat/gcal-cli"]
Gemini CLIにWireCat Google Calendar MCPをインストール
$ gemini mcp add -s user gcal-cli npx -- -y @wirecat/gcal-cliGemini settings.jsonにWireCat Google Calendar MCPをインストール
~/.gemini/settings.json
{
"mcpServers": {
"gcal-cli": {
"command": "npx",
"args": [
"-y",
"@wirecat/gcal-cli"
]
}
}
}自動チェック
実行日 2026年11月14日完全なレポート →自動チェックに合格しました。これはセキュリティ監査ではありません。コードを読み、サーバーに必要最小限のアクセス権を与えてください。 チェックの仕組み
- ソースリポジトリがリンクされており、アクセス可能wirecatlabs/gcal-cli is public and reachablegithub.com/wirecatlabs/gcal-cli ↗合格
- パッケージがこのリポジトリをソースとして指定@wirecat/gcal-cli names wirecatlabs/gcal-cli as sourcenpmjs.com/package/@wirecat/gcal-cli ↗合格
- ビルドの来歴 (Sigstore 証明)Sigstore attestation for @wirecat/gcal-clinpmjs.com/package/@wirecat/gcal-cli/v/0.26.0#provenance ↗合格
- オープンソースライセンス (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗合格
- 過去1年以内にコミットまたはリリースありLast commit or release 2026-11-14github.com/wirecatlabs/gcal-cli ↗合格
- OpenSSF Scorecard未チェック
- パッケージ名が有名なパッケージに酷似していないNo popular package one edit away from @wirecat/gcal-cli合格
- パッケージおよびその依存関係に重大な勧告なしthe package checked; no critical advisoryosv.dev ↗合格
- モデルへの隠れた指示がない0 tool descriptions and the README read; no override phrases, credential paths or hidden characters合格
- 破壊的なツールがラベル付けされている未チェック
- リモートエンドポイントが MCP ハンドシェイクに応答未チェック
README
GitHubで見るgcal — 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.
WireCat Google Calendar MCPのよくある質問
WireCat Google Calendar MCPをClaude Codeに追加するには
ターミナルでclaude mcp add gcal-cli -- npx -y @wirecat/gcal-cliを実行します。すべてのプロジェクトで利用するには--scope userを追加します。
WireCat Google Calendar MCPをCursorに追加するには
~/.cursor/mcp.jsonを開き、上記のインストールセクションに示すCursor設定を使ってmcpServersの下にサーバーを追加します。
Claude DesktopやCursorでどのように使用しますか?
コマンド gcal personal mcp serve を使用して、プロファイルのMCP serverに接続してください。
カレンダーを検索するために、エージェントはインターネット接続が必要ですか?
いいえ、カレンダーがローカルのWireCatストアに同期されていれば、検索はネットワークを介さずローカルで実行されます。
AIエージェントは会議の出席者にメールを送信できますか?
設定で明示的に許可しない限り、デフォルトでは他の人へのメール送信は無効になっています。