WireCat Google Calendar

Name: WireCat Google Calendar
Author: WireCatLabs

作者：WireCatLabs版本 0.20.0i★ –i在你的电脑上运行

注册名称dev.wirecat/gcal-cli

安装

概览

作者提供的说明（英文原文）

Your Google Calendar for agents: sync, search and change events. Sign in with the gcal CLI first.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 文档、表格与办公

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
注册中心没有列出需要填写的密钥。

你需要

npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 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 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "gcal-cli": {
      "command": "npx",
      "args": [
        "-y",
        "@wirecat/gcal-cli",
        "mcp",
        "serve",
        "--profiles",
        "all"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "gcal-cli": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@wirecat/gcal-cli",
        "mcp",
        "serve",
        "--profiles",
        "all"
      ]
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

✓ 通过
作者与仓库一致
注册名称已通过域名 wirecat.dev 验证（注册中心会核实域名所有权）
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“文档、表格与办公”中的其他服务器比较i

星标数多于此分类中其他 2168 个服务器的 0%
发布到注册中心的时间比此分类中其他 2168 个服务器的 94% 更新
基础检查结果等于或优于此分类中其他 2168 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

WireCat Google Calendar 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.20.0）于昨天进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。

有什么可以替代它？

同一分类中有：Agent-Native Calendar, Excel MCP Server, MCP Server for Excel

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Agent-Native Calendar

作者：BuilderIO

Agent-Native Google Calendar - manage events, sync, and public booking

在云端运行★ 7,620MIT2个月前更新

安装

Excel MCP Server

作者：haris-musa

Create and edit Excel files with AI: charts, PivotTables, formulas. No Excel needed.

在你的电脑上运行★ 4,276MIT5天前更新

安装

MCP Server for Excel

作者：sbroenne

Excel automation for AI - Sheets, Power Query, DAX, VBA, Tables, Ranges and more. Windows only.

在你的电脑上运行★ 847MIT3天前更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

gcal — Google Calendar CLI for AI agents

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.

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

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 write first.
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 gcal itself. The skill is the agent's instruction sheet: it explains the commands and the limits. gcal skill install writes 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 config prints 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, sync asks Google only for what changed. gcal personal store status shows 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-25 lists the events that are new, moved or cancelled since a date.
All accounts in one list. events list --source all lists the events of every Google account you signed in to, and says which accounts it read.
Meetings that overlap. events list overlapping:true --source all finds the meetings that clash, also across accounts.
Search by meaning. gcal models download e5-small fetches a small model once. sync --embed then indexes new events with it.
Search in Google. 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.
One search over everything. search all roadmap finds your meetings beside the chats that other WireCat tools stored and your notes, and says which accounts it read.
Every Google Calendar method. gcal api reaches 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 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.
A Google app in Testing mode ends sign-ins after seven days. Sign in again, or publish the app.
calendars busy shows 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 P

只显示了开头部分；其余内容请在仓库中阅读