Agent-Native Calendar
Agent-Native Google Calendar - manage events, sync, and public booking
作者提供的说明(英文原文)
Meeting programmes for AI: drafted by your assistant, approved by a person, published as PDF and web
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://timely.publifye.com/mcp在终端中运行这条命令
claude mcp add --transport http timely https://timely.publifye.com/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"timely": {
"url": "https://timely.publifye.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"timely": {
"type": "http",
"url": "https://timely.publifye.com/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://timely.publifye.com/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过域名 publifye.pro 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.0)于上个月进入注册中心。
支持 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、图片和脚本已被移除。链接会离开本站。
Timely builds a meeting programme — a fixed number of meetings, or everything inside a calendar period — keeps every revision, and renders the approved version to a PDF through Doksi. An assistant may publish only the exact revision and PDF the user has just confirmed. It runs as a hosted MCP server over HTTPS.
| Endpoint | https://timely.publifye.com/mcp |
| Transport | Streamable HTTP |
| Auth | OAuth 2.1 + PKCE (S256), DCR open |
| Registry | pro.publifye/timely (server.json) |
| Product site | https://timely.publifye.com |
| What it solves | https://publifye.com/timely |
| Capability tools | 31 (full schemas) |
| Surface described | generated from source 354ee8b; the same tool surface was live in production as version 0.1.198 (9ce28e3, released 2026-09-23). On 2026-10-09, with 0.1.225 the latest release, production listed the same 31 customer tool names; the schemas were not recaptured |
{ "mcpServers": { "timely": { "type": "http", "url": "https://timely.publifye.com/mcp" } } }
Claude Code: claude mcp add --transport http timely https://timely.publifye.com/mcp, then /mcp to sign in. The discovery chain is the same as for the other servers: [../../docs/connect.md](../../docs/connect.md).
An assistant can publish a programme with draft_approve; no browser step or signed confirmation page is involved. What it cannot do is publish on its own initiative. The tool's own description tells the assistant to show the user the exact revision, the PDF download link and the public address, to flag open assumptions, and to ask — a general request to edit is not consent. The server then enforces the part it can check:
user_confirmed must be true; otherwise the call is refused with *"ask the user explicitly before publishing; user_confirmed must be true only after their affirmative answer"*;revision, content_hash and pdf_hash must name the exact preview that was shown; if the programme or its PDF has changed since, the approval does not match and nothing is published;user_confirmed is the assistant's statement that the user said yes; the server records it in the programme's audit trail (mcp_user_confirmed_publication) but cannot see the conversation. The hashes are what make a yes apply to one revision and one PDF only.
timely_edit applies explicit operations against a base_hash. If the programme moved since the agent last read it, the edit is refused rather than merged — so two assistants, or an assistant and a person, cannot silently overwrite one another. Every commit becomes an immutable revision, and timely_history returns those revisions with their changes and the PDF each one produced.
timely_render sends the current draft to [Doksi](../doksi) and retains the exact preview PDF that was produced — the same artifact a person then approves. The two servers are separate products and can be used separately; Timely simply does not re-implement document rendering.
Every tool is documented with its exact description, annotations and input schema — 31 in all, generated from the service's own registry, never written by hand.
| Area | The question it answers | Tools |
|---|---|---|
| [Read a programme](tools/read.md) | What is published, what is drafted, and what changed? | 6 |
| [Build and render](tools/build.md) | Create, edit, restyle, preview — and where approval stops. | 7 |
| [Websites and widgets](tools/websites.md) | Where may the programme appear, and how does it look there? | 3 |
| [Organisation and homepage](tools/organisation.md) | What does the shared organisation page say, and how does it become a homepage? | 8 |
| [Export, import and the bin](tools/lifecycle.md) | How is a programme backed up, restored, or taken down? | 7 |
Machine-readable: [tools.json](tools.json) carries all 31 with full JSON Schema, plus every excluded bucket listed by name so the count is auditable. Fifteen staff-only admin_* tools, ten log and operations tools, and the operator_guide/instance_status pair are excluded from the customer surface.
timely_delete moves a programme — or the organisation page — to a bin: it leaves every public address at once and can be brought back with timely_restore until the purge date that timely_trash_list shows. timely_export returns a lossless, schema-versioned JSON backup with a SHA-256 over its exact bytes, and timely_import only ever creates a new programme from a file that validates against timely_export_schema — it never overwrites an existing one.
Plans and prices can change; the current ones are always on [https://timely.publifye.com](https://timely.publifye.com), and where this page and the site differ, the site is right.