Agent-Native Calendar
Agent-Native Google Calendar - manage events, sync, and public booking
作者による説明(英語の原文)
Your Google Calendar for agents: sync, search and change events. Sign in with the gcal CLI first.
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。
使っているAIアプリを選んで、設定をコピーしてください。
必要なもの
どのアプリを使っていますか?
上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。
Claude Desktop → Settings → Developer → Edit Config を開き、claude_desktop_config.json にこれを貼り付けます
{
"mcpServers": {
"gcal-cli": {
"command": "npx",
"args": [
"-y",
"@wirecat/gcal-cli",
"mcp",
"serve",
"--profiles",
"all"
]
}
}
}ターミナルでこれを実行します
claude mcp add gcal-cli -- npx -y @wirecat/gcal-cli mcp serve --profiles allプロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます
{
"mcpServers": {
"gcal-cli": {
"command": "npx",
"args": [
"-y",
"@wirecat/gcal-cli",
"mcp",
"serve",
"--profiles",
"all"
]
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
プロジェクトの .vscode/mcp.json に貼り付けます
{
"servers": {
"gcal-cli": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@wirecat/gcal-cli",
"mcp",
"serve",
"--profiles",
"all"
]
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
これはパソコンで動くサーバーですが、ChatGPTがつなげるのはインターネット上のサーバーだけです。ほかのアプリを選んでください。
選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。
この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
パソコンで動くサーバーです。インストールすると、ツール一覧がAIアプリに表示されます。
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月6日にチェック
レジストリ名はドメイン wirecat.dev で確認済みです(レジストリがドメインの所有を確認しています)
このリポジトリはまだGitHubから読み取っていません
このリポジトリはまだGitHubから読み取っていません
これはパソコンで動くため、インターネット上のエンドポイントはありません
パソコンで動き、代わりにローカルの設定を使います
パソコンで動くサーバーです。ツール一覧を読み取れるのは、インターネット上のエンドポイントがある場合だけです
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック1項目のうち1項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
レジストリには必須のキーは載っていません。ただし、最初に使うときにサインインを求めるサーバーもあります。
あなたのパソコンで動きます。必要なときにAIアプリが起動し、データは作者のサーバーを通りません(サーバー自体がオンラインサービスを呼び出す場合を除きます)。
GitHubリポジトリの最終更新は–、最新バージョン(0.20.0)がレジストリに届いたのは昨日です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。パソコンにNode.jsも必要です。
同じカテゴリには:Agent-Native Calendar, Excel MCP Server, MCP Server for Excel
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
Agent-Native Google Calendar - manage events, sync, and public booking
Create and edit Excel files with AI: charts, PivotTables, formulas. No Excel needed.
Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
Your Google Calendar in the terminal, searchable on your computer, and ready for Claude Code, Codex, Gemini CLI or any agent — within limits you set.
Docs · Use it · WireCat
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.
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).
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:
gcal personal events show event:42.gcal personal people link email:ana@example.com telegram:12345.session start --grant write first.gcal api.More: use it (wirecat.dev).
Your agent. Your calendar. Your rules.
gcal itself. The skill is the agent's instruction sheet: it explains the commands and the limits. gcal skill install writes it.gcal personal mcp serve. gcal personal mcp config prints the entry to paste.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).
sync asks Google only for what changed. gcal personal store status shows how far each calendar is.events list changed_at>=2026-10-25 lists the events that are new, moved or cancelled since a date.events list --source all lists the events of every Google account you signed in to, and says which accounts it read.events list overlapping:true --source all finds the meetings that clash, also across accounts.gcal models download e5-small fetches a small model once. sync --embed then indexes new events with it.search events --backend server asks Google's own search. It also finds events outside the synced span. --backend both asks the store and Google together.search all roadmap finds your meetings beside the chats that other WireCat tools stored and your notes, and says which accounts it read.gcal api reaches each one, under its own permission key.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 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).
gcal personal calendars list shows the rest, and gcal personal calendars sync 3 adds calendar 3.gcal has no Google app of its own yet. Sign-in needs your own client.calendars busy shows a person's busy times only when their calendar is shared with you or your organization.watch) are not offered: they need a public web address.What is planned is on the roadmap (wirecat.dev).
冒頭だけを表示しています。続きはリポジトリで読めます