MinerU
Transforms complex documents like PDFs and Office docs into LLM-ready markdown/JSON for your Agentic workflows.
Read and manage To-do Calendar todos, schedules and tags from an AI agent.
教 AI 做这类工作的 Skill,可与本项一起使用
Transforms complex documents like PDFs and Office docs into LLM-ready markdown/JSON for your Agentic workflows.
Agent skills for Obsidian. Teach your agent to use Obsidian CLI and open formats including Markdown, Bases, JSON Canvas.
此项在“连接 AI 的应用”标签中,该标签不使用星标,按以下顺序排列
| 1. 在 Claude 连接器目录中 | 否 | |
|---|---|---|
| 2. 团队实测过 | 否 | |
| 3. 适合泰国用户 | 否 | |
| 4. 不计星标的使用量 | 20/100 | 热度 0 · 新鲜度 12 · 仍在响应 8 · 用户喜欢 +0 |
| 5. 登记日期 | 2026-11-15 |
用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。
质量: 基础检查通过 4/4 项(仅展示,不用于排序)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 To-do Calendar。按照 https://mcp.popnx.com/i/todo-calendar.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 4/4 项检查 · 你的提问会经过开发者的服务器(mcp.todo-calendar.com) · ✓ 命令已检查 2026年11月15日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
To-do Calendarhttps://mcp.todo-calendar.com/mcp在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsTo-do Calendar
用 To-do Calendar 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 To-do Calendar,或回答中出现 To-do Calendar 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
To-do Calendarhttps://mcp.todo-calendar.com/mcp开启新聊天,输入前先从插件列表中选择 To-do Calendar
用 To-do Calendar 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 To-do Calendar,或回答中出现 To-do Calendar 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user todo-calendar https://mcp.todo-calendar.com/mcp应能看到 To-do Calendar 在列表中并显示已连接
用 To-do Calendar 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 To-do Calendar,或回答中出现 To-do Calendar 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 To-do Calendar 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 To-do Calendar,或回答中出现 To-do Calendar 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 To-do Calendar 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 To-do Calendar,或回答中出现 To-do Calendar 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://mcp.todo-calendar.com/mcpJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user todo-calendar https://mcp.todo-calendar.com/mcpCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"todo-calendar": {
"url": "https://mcp.todo-calendar.com/mcp"
}
}
}VS Code (mcp.json)
{
"servers": {
"todo-calendar": {
"type": "http",
"url": "https://mcp.todo-calendar.com/mcp"
}
}
}这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
服务器要求先登录,才会列出它的工具。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过域名 todo-calendar.com 验证(注册中心会核实域名所有权)
代码最后更新于3天前
不适用:由 todo-calendar.com 的所有者自己运行的云端服务器,你不会运行仓库里的代码
在 268 毫秒内响应(HTTP 401)
声明支持 OAuth 登录,你的 AI 应用可以带你去登录
尚未检查;我们会在检查端点时读取工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/todo-calendar)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 4 项适用的基础检查中通过了 4 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于3天前,最新版本(1.0.2)于4天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:Puter MCP, XcodeBuildMCP, Vexa, Atlassian Rovo MCP Server, Anki MCP Server
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Puter MCP enables AI tools to interact with Puter: manage files, websites, workers, and more
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
Meeting bot and transcripts for Google Meet, Teams and Zoom. Live or after, speakers labelled.
Connect to Atlassian Jira, Confluence, Loom, and more to search, create, and manage your work.
MCP server for Anki flashcards: adaptive review, notes, media, and deck management via AnkiConnect.
| 本项 To-do Calendar | Puter MCP | XcodeBuildMCP | Vexa | Atlassian Rovo MCP Server | Anki MCP Server | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 在云端运行,无需安装 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 需要安装在电脑上 |
| 需要密钥 | 否 | 否 | 否 | 是 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 是 | 否 |
| 基础检查 | 4/4 | 4/4 | 3/3 | 2/4 | 4/4 | 3/3 |
| 许可证 | – | AGPL-3.0 | MIT | Apache-2.0 | Apache-2.0 | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
An MCP server and npm tool library that let AI agents work with To-do Calendar todos, schedules and tags.
Two entry points, one tool layer:
*For anyone connecting the hosted server from Claude, and for directory reviewers. Everything below this section is developer documentation, in Korean.*
1. Add the connector. In Claude, open Settings → Connectors → Add custom connector and enter:
https://mcp.todo-calendar.com/mcp
2. Sign in. Claude redirects you to the To-do Calendar sign-in page. The consent screen lists the two scopes being requested — read:calendar and write:calendar. The connector only ever acts on the account that approved it: the user identity is read from the verified access token, never from a tool argument.
3. Ask for something. A few prompts that exercise the main paths:
| Prompt | Tool |
|---|---|
| "What's on my calendar this week?" | get_expanded_schedules |
| "What to-dos do I have open?" | get_todos |
| "Add a to-do: buy coffee beans, tomorrow 9am" | create_todo |
| "Move it to 10am" | update_todo |
| "Mark it done" | complete_todo |
| "Add a weekly team meeting, Mondays 10am" | create_schedule |
| "Skip next Monday's team meeting" | exclude_schedule_occurrence |
| "Delete the team meeting" | delete_schedule (two steps — see below) |
Deleting takes two steps. delete_todo and delete_schedule do not delete on the first call. The first call changes nothing and returns a confirmation message with a token; the deletion happens only when the assistant calls again with the same arguments plus that token. Tokens expire after 5 minutes and are bound to the user, the tool and the arguments, so they cannot be replayed elsewhere.
Disconnecting. End the connection from Claude's connector settings, which drops the tokens it holds. Access tokens are short-lived (2 hours), and the refresh token can be revoked at the authorization server's RFC 7009 revocation endpoint.
30 tools. Repeating events are expanded on the server, so you get the dates each occurrence actually falls on — weekday accrual, month-end skips, leap years and lunar rules included.
| To-dos | list, create, edit, complete, restore, replace, delete |
| Schedules | list, create, edit, delete; edit or skip a single occurrence; split a repeating series |
| Tags | list, create, edit, delete |
| Event details | place, link, memo |
| Pinned event | read, set, clear |
Every tool carries a title and the applicable readOnlyHint / destructiveHint in tools/list. describe_tool({name}) returns the full guide and the input/output JSON Schemas for any tool.
Privacy policy (Korean: /privacy/ko). The "Connected external apps" section covers what a connected app can reach, which tokens are stored and for how long, and how to end a connection.
This server keeps no store of its own — it forwards requests to the To-do Calendar API and passes responses straight back.
todocalendar.help@gmail.com
https://mcp.todo-calendar.com/mcp
Streamable HTTP transport (compatible with MCP spec 2025-06-18).
OAuth 2.1 Resource Server. The Authorization Server is a separate service hosted by TodoCalendar Functions. Clients get a token there, then send:
Authorization: Bearer <RS256 JWT>
The token must carry the required scopes:
read:calendar — get_* toolswrite:calendar — create / update / delete toolsset_foremost_event needs both — it reads the target first to tell whether it is a todo or a scheduleThe server publishes the AS location and scope list at GET /.well-known/oauth-protected-resource (RFC 9728).
30 tools, including the describe_tool meta tool. Responses are openAPI raw passthrough — no field renames, raw Unix-second timestamps kept, with *_iso siblings added alongside.
For the actual dates repeating events fall on in a range, use get_expanded_* (the server expands them into occurrences). For the raw recurrence rules only, use get_todos / get_schedules.
tools/list carries short summaries only (no outputSchema, 1–3 sentence descriptions). Each tool's full guide and complete I/O JSON Schemas come on demand from describe_tool({name}). Rules shared by every tool — ISO time handling, discriminators, the CONFIRM flow — are stated once in the initialize response instructions.
| domain | tools | CONFIRM |
|---|---|---|
| todo | get_todos / get_expanded_todos / create_todo / update_todo / complete_todo / replace_todo / delete_todo | delete_todo |
| schedule | get_schedules / get_expanded_schedules / create_schedule / update_schedule / exclude_schedule_occurrence / replace_schedule_occurrence / branch_schedule_repeating / delete_schedule | delete_schedule |
| tag | get_tags / create_tag / update_tag / delete_tag | — |
| done todo | get_done_todos / update_done_todo / revert_done_todo / delete_done_todo | — |
| event detail | get_event_details / set_event_detail / delete_event_detail | — |
| foremost event | get_foremost_event / set_foremost_event / clear_foremost_event | — |
| meta | describe_tool | — |
For detailed input/output schemas, see the describe_tool({name}) response (docs + input_schema + output_schema).
Two-step CONFIRM (delete_todo / delete_schedule): the first call deletes nothing and returns only a confirmToken; echoing the token on a second call performs the deletion. Tokens expire in 5 minutes and are bound to user + tool + args, so they cannot be reused for another user or other arguments.
First-party server-side AI hosts such as aiFrontAPI skip the MCP transport and import the tool functions directly.
Public package on npmjs.com — no auth or .npmrc setup needed.
npm install todocalendar-tools
import { tools, type Auth } from 'todocalendar-tools/tools'
// The caller builds the auth context. This library does not verify credentials: // verify the token (e.g. Firebase Auth) first, then pass the resulting userId. const auth: Auth = { userId: ' ', scopes: ['read:calendar', 'write:calendar'], // clientId?: OAuth client_id. Usually undefined on the dev/lib path. }
const result = await tools.get_todos.execute(auth, { mode: 'current' })
auth.userId only from a verified token's sub. The library ignores any userId passed in tool args, but verifying the caller is your job.auth.scopes; on the library import path they have no enforcing effect. openAPI calls always carry both read:calendar and write:calendar. The field exists for shape compatibility.OPENAPI_BASE_URL — openAPI base URLOPENAPI_PAT_MCP — service auth PAT (mcp_ format)SIGNING_SECRET — HS256 signing key for x-open-user-token (shared with openAPI)CONFIRM_SECRET — HMAC key for confirm tokensoutputSchema documents the shape for the LLM and is never parsed at runtime, so extra fields are preserved.ToolError — { status, code, message }. code catalog: InvalidParameter (400) / NotFound (404) / InsufficientScope (403) / Timeout (0) and others. message adds a natural-language explanation; code and status are always the originals.Only todocalendar-tools/tools is public. Signature or type changes are a semver major.
MIT.