Agent-Native Calendar
Agent-Native Google Calendar - manage events, sync, and public booking
作者提供的说明(英文原文)
Calendar API for AI agents: events, availability, Google/Microsoft setup, scheduling, and iCal.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
CHRONARY_API_KEY, Authorization标为机密的值是你账户的钥匙。千万不要分享给别人,也不要粘贴到聊天里。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"chronary": {
"command": "npx",
"args": [
"-y",
"@chronary/mcp"
],
"env": {
"CHRONARY_API_KEY": "your-value"
}
}
}
}在终端中运行这条命令
claude mcp add --transport http chronary https://api.chronary.ai/mcp --header 'Authorization: your-value'claude mcp add chronary --env CHRONARY_API_KEY=your-value -- npx -y @chronary/mcp运行前请先填写空着的值。
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"chronary": {
"url": "https://api.chronary.ai/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"chronary": {
"command": "npx",
"args": [
"-y",
"@chronary/mcp"
],
"env": {
"CHRONARY_API_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"chronary": {
"type": "http",
"url": "https://api.chronary.ai/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"chronary": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@chronary/mcp"
],
"env": {
"CHRONARY_API_KEY": "your-value"
}
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个地址需要在请求的 header 中放入密钥,而添加连接器的菜单无法设置。请改用 Claude Code、Cursor 或 VS Code。
你的选择通过 Cookie 保存在这台设备上,无需账户。
Authorization 机密 必填 HTTP header这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日
注册名称已通过域名 chronary.ai 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
你需要填写:CHRONARY_API_KEY, Authorization
两种方式都可以:安装在你的电脑上,或者连接云端版本。
GitHub 仓库最后更新于–,最新版本(1.5.2)于4个月前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Agent-Native Calendar, Excel MCP Server, MCP Server for Excel
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况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、图片和脚本已被移除。链接会离开本站。
MCP server for Chronary — calendar tools for AI assistants.
Drops 50 calendar tools (manage agents, calendars, and events, request human Google/Microsoft setup, find meeting times, run scheduling proposals, configure availability rules, manage webhooks, iCal subscriptions, scoped keys, audit log, and usage) into any MCP-compatible client: Claude Desktop, Cursor, VS Code Copilot, Claude Code, Windsurf.
One-click install via [Smithery](https://smithery.ai/server/chronary/agent-calendar): npx -y @smithery/cli mcp add chronary/agent-calendar --client claude (swap --client for cursor, vscode, claude-code, windsurf, …).
chr_sk_).All examples use npx -y @chronary/mcp, which downloads and runs the latest version on demand. No install step required.
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
macOS / Linux:
{
"mcpServers": { "chronary": { "command": "npx", "args": ["-y", "@chronary/mcp"], "env": { "CHRONARY_API_KEY": "chr_sk_..." } } } }
Windows (uses cmd /c because spawn can't resolve npx.cmd directly):
{
"mcpServers": { "chronary": { "command": "cmd", "args": ["/c", "npx", "-y", "@chronary/mcp"], "env": { "CHRONARY_API_KEY": "chr_sk_..." } } } }
Restart Claude Desktop after saving.
Edit .cursor/mcp.json (project-level) or ~/.cursor/mcp.json (user-level):
macOS / Linux:
{
"mcpServers": { "chronary": { "command": "npx", "args": ["-y", "@chronary/mcp"], "env": { "CHRONARY_API_KEY": "chr_sk_..." } } } }
Windows:
{
"mcpServers": { "chronary": { "command": "cmd", "args": ["/c", "npx", "-y", "@chronary/mcp"], "env": { "CHRONARY_API_KEY": "chr_sk_..." } } } }
Edit .vscode/mcp.json (workspace) or run the MCP: Open User Configuration command for a user-level config. VS Code uses a different top-level key (servers) and requires an explicit type:
macOS / Linux:
{
"servers": { "chronary": { "type": "stdio", "command": "npx", "args": ["-y", "@chronary/mcp"], "env": { "CHRONARY_API_KEY": "chr_sk_..." } } } }
Windows:
{
"servers": { "chronary": { "type": "stdio", "command": "cmd", "args": ["/c", "npx", "-y", "@chronary/mcp"], "env": { "CHRONARY_API_KEY": "chr_sk_..." } } } }
Edit .mcp.json at the project root, or ~/.claude.json for user-level:
macOS / Linux:
{
"mcpServers": { "chronary": { "command": "npx", "args": ["-y", "@chronary/mcp"], "env": { "CHRONARY_API_KEY": "chr_sk_..." } } } }
Windows:
{
"mcpServers": { "chronary": { "command": "cmd", "args": ["/c", "npx", "-y", "@chronary/mcp"], "env": { "CHRONARY_API_KEY": "chr_sk_..." } } } }
Edit ~/.codeium/windsurf/mcp_config.json (%USERPROFILE%\.codeium\windsurf\mcp_config.json on Windows):
macOS / Linux:
{
"mcpServers": { "chronary": { "command": "npx", "args": ["-y", "@chronary/mcp"], "env": { "CHRONARY_API_KEY": "chr_sk_..." } } } }
Windows:
{
"mcpServers": { "chronary": { "command": "cmd", "args": ["/c", "npx", "-y", "@chronary/mcp"], "env": { "CHRONARY_API_KEY": "chr_sk_..." } } } }
Windsurf limit: Cascade enforces a hard cap of 100 total tools across all MCP servers and 20 tool calls per prompt. Chronary exposes 50; consider
--toolsfiltering if you stack multiple servers.
--toolsExposing all 50 tools uses LLM tokens on every request. For focused workflows, whitelist only what you need:
{
"mcpServers": { "chronary": { "command": "npx", "args": [ "-y", "@chronary/mcp", "--tools", "list_events,find_meeting_time,create_event" ], "env": { "CHRONARY_API_KEY": "chr_sk_..." } } } }
For self-hosted Chronary instances or development against a local API:
{
"args": ["-y", "@chronary/mcp", "--base-url", "http://localhost:8787"] }
| Tool | Read-only | Destructive |
|---|---|---|
list_calendars, get_calendar | ✓ | |
create_calendar, update_calendar | ||
delete_calendar | ✓ | |
list_events, get_event | ✓ | |
create_event, update_event, confirm_event | ||
cancel_event, release_event | ✓ | |
list_agents, get_agent | ✓ | |
create_agent, update_agent | ||
delete_agent | ✓ | |
get_availability, find_meeting_time | ✓ | |
get_calendar_context | ✓ | |
list_proposals, get_proposal | ✓ | |
create_proposal, respond_to_proposal, resolve_proposal | ||
cancel_proposal | ✓ | |
get_availability_rules | ✓ | |
set_availability_rules | ||
clear_availability_rules | ✓ | |
list_webhooks, get_webhook, list_webhook_deliveries | ✓ | |
create_webhook, update_webhook | ||
delete_webhook | ✓ | |
list_ical_subscriptions, get_ical_subscription | ✓ | |
subscribe_ical, update_ical_subscription, sync_ical_subscription | ||
delete_ical_subscription | ✓ | |
list_scoped_keys | ✓ | |
create_scoped_key | ||
revoke_scoped_key | ✓ | |
get_audit_log | ✓ | |
accept_terms | ||
get_usage | ✓ |
Tool annotations (readOnlyHint, destructiveHint, idempotentHint) are surfaced to MCP clients so hosts can decide whether to require user confirmation.
"spawn npx ENOENT" on Windows — use the cmd /c npx ... form shown above.
"CHRONARY_API_KEY is required" — the env block must be nested under the server entry, not at the top of the config file.
Tools aren't showing up — restart the MCP client after editing the config. Most clients only read the config on startup.
Verify the binary runs locally:
CHRONARY_API_KEY=test npx -y @chronary/mcp --help
Apache-2.0