Chronos MCP

MCP日程管理

提供方 democratize-technology

日程管理 stdio · 本地进程 无需鉴权 社区 / 第三方
查看接入方式

Chronos MCP是一个基于FastMCP 2.0构建的高级CalDAV日历管理服务器,提供多账户支持、完整CRUD操作、高级事件管理、任务管理和日志记录功能。

一句话选型结论

按资料字段整理

Chronos MCP 属于日程管理类 MCP 服务器,stdio · 本地进程,无需鉴权,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类日程管理 传输方式stdio · 本地进程 鉴权无需鉴权 部署方式本地部署
GitHub 星标 19 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

日程管理
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

适用场景

日历管理Python本地部署事件管理任务管理日志记录多账户支持

安装与配置

stdio · 本地进程 无需鉴权
客户端在本机拉起子进程,数据不出本机
python scripts/migrate_to_keyring.py --dry-run

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Python,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
日程安排

按空闲时间自动排日程。

提醒与待办

设提醒、管待办清单。

时间协调

在多人之间找共同空档。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 资料标注无需鉴权,装好就能连。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在日程管理场景里让模型直接调用外部能力的人。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Chronos MCP当前 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Todoist MCP Server 79e800d2 35 stdio · 本地进程 支持远程部署 有 2026-05-17
Outlook Calendar MCP 7 stdio · 本地进程 本地部署 有 2026-05-18
MCP Server Apple Events 5 stdio · 本地进程 本地部署 有 2026-05-17
y-cli 未标注 stdio · 本地进程 本地部署 无 2026-10-05
Google Calendar 未标注 HTTP · 远程 支持远程部署 有 2026-05-17

服务器档案

日程管理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方democratize-technology上游标注的维护方 democratize-technology
分类日程管理本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式无需鉴权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Python本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

7.4 KB
来自项目仓库与上游目录的原文,未做删改

Chronos MCP - Advanced CalDAV Management Server

A comprehensive Model Context Protocol (MCP) server for CalDAV calendar management, built with FastMCP 2.0. Chronos provides advanced calendar and event management capabilities with multi-account support.

🚀 Features

  • Multi-account Support: Manage multiple CalDAV servers simultaneously
  • Full CRUD Operations: Create, read, update, and delete calendars and events ✅
  • Advanced Event Management:
  • Recurring events with RRULE support ✅
  • Event updates with partial field modifications ✅
  • Attendee management and invitations (JSON format) ✅
  • Reminders and alarms (VALARM) ✅
  • Timezone-aware operations
  • Advanced Search:
  • Full-text search across events ✅
  • Field-specific search (title, description, location) ✅
  • Multiple match types (contains, starts_with, exact, regex) ✅
  • Date range filtering ✅
  • Relevance ranking algorithm ✅
  • Bulk Operations:
  • Create multiple events in parallel ✅
  • Delete multiple events efficiently ✅
  • Atomic operations with rollback ✅
  • Configurable error handling modes ✅
  • Security Hardening:
  • Comprehensive input validation ✅
  • XSS and injection prevention ✅
  • Path traversal protection ✅
  • RFC-compliant validation ✅
  • Task Management: Full VTODO support ✅
  • Journal Entries: Full VJOURNAL support ✅

📋 Task Management (VTODO)

Chronos MCP provides comprehensive support for CalDAV tasks:

  • Create tasks with due dates, priorities, and descriptions
  • Track progress with percentage completion (0-100%)
  • Manage status: NEEDS-ACTION, IN-PROCESS, COMPLETED, CANCELLED
  • Create subtasks using related_to relationships
  • Bulk operations for efficient task management

Available tools:
- create_task — Create a task with summary, due date, priority, description
- list_tasks — List tasks in a calendar, optionally filtering by status
- update_task — Partial update of task fields (status, priority, progress, etc.)
- delete_task — Delete a task by UID
- bulk_create_tasks — Create multiple tasks in parallel
- bulk_delete_tasks — Delete multiple tasks in parallel```bash

Example: Create a task

mcp call create_task '{
"calendar_uid": "my-calendar",
"summary": "Complete project documentation",
"due": "2025-02-01T15:00:00Z",
"priority": 2
}'


## 📓 Journal Entries (VJOURNAL)

Keep detailed records with CalDAV journal entries:

- **Create journal entries** with timestamps and rich descriptions
- **Link related entries** using related_to relationships
- **Organize with categories** for better searchability
- **Update and manage** existing journal entries

**Available tools:**
- `create_journal` — Create a journal entry with summary and description
- `list_journals` — List journal entries in a calendar
- `update_journal` — Partial update of journal fields
- `delete_journal` — Delete a journal entry by UID
- `bulk_create_journals` — Create multiple journal entries in parallel
- `bulk_delete_journals` — Delete multiple journal entries in parallel```bash
# Example: Create a journal entry
mcp call create_journal '{
  "calendar_uid": "my-calendar",
  "summary": "Team Meeting Notes",
  "description": "Discussed Q1 objectives..."
}'

For detailed usage, see VTODO/VJOURNAL Guide.

🔐 Security

Secure Password Storage (New!)

Chronos MCP now supports secure password storage using your system's keyring (via python-keyring). When available, passwords are automatically stored in:
- macOS: Keychain Access
- Windows: Windows Credential Locker
- Linux: Secret Service (GNOME Keyring, KWallet, etc.)

Migration to Secure Storage

If you have existing accounts with passwords stored in plain text, migrate them to secure storage:```bash

Check what will be migrated (dry run)

python scripts/migrate_to_keyring.py --dry-run

Perform actual migration

python scripts/migrate_to_keyring.py


The migration script will:
1. Read existing passwords from `~/.chronos/accounts.json`
2. Store them securely in your system keyring
3. Create a backup of the original configuration
4. Remove passwords from the JSON file

### Fallback Behavior

If keyring is not available (e.g., SSH sessions, containers), Chronos MCP will:
- Warn about the security implications
- Fall back to storing passwords in the configuration file
- Automatically attempt to migrate passwords to keyring when it becomes available

### Legacy Security Warning

**Note**: If keyring is not installed or available, passwords will be stored in plain text at `~/.chronos/accounts.json`. Install keyring support with:```bash
pip install "chronos-mcp[secure]"  # or just: pip install keyring

Installation

Standard Installation```bash

pip install -e .


### Secure Installation (Recommended)
Includes keyring support for secure password storage:```bash
pip install -e ".[secure]"

Or if you already have Chronos installed:```bash
pip install keyring>=24.0.0


## Configuration

### Environment Variables (Default Account)```bash
CALDAV_BASE_URL=http://<YOUR_CALDAV_SERVER>:5232
CALDAV_USERNAME=<YOUR_USERNAME>
CALDAV_PASSWORD=<YOUR_PASSWORD>

Multi-Account Configuration

Create ~/.chronos/accounts.json:```json
{
"accounts": {
"personal": {
"url": "http://<YOUR_CALDAV_SERVER>:5232",
"username": "<YOUR_USERNAME>",
"display_name": "Personal Calendar"
},
"work": {
"url": "https://caldav.company.com",
"username": "user",
"display_name": "Work Calendar"
}
},
"default_account": "personal"
}


**Note**: Passwords are not included in the JSON when using keyring. They will be:
- Prompted for on first use and stored securely
- Migrated from existing configuration using `scripts/migrate_to_keyring.py`
- Only stored in JSON if keyring is unavailable (with a warning)

## Usage

### Running the Server```bash
./run_chronos.sh

Basic Operations

List all configured accounts:```
list_accounts()


### Example Tool Usage

Create an event with reminder:```python
chronos:create_event(
    calendar_uid=&quot;assistant&quot;,
    summary=&quot;Team Meeting&quot;,
    start=&quot;2025-07-08T14:00:00&quot;,
    end=&quot;2025-07-08T15:00:00&quot;,
    location=&quot;Conference Room&quot;,
    alarm_minutes=&quot;15&quot;  # Note: Pass as string!
)

Create recurring event with attendees:```python
chronos:create_event(
calendar_uid="work",
summary="Weekly Standup",
start="2025-07-07T09:00:00",
end="2025-07-07T09:30:00",
recurrence_rule="FREQ=WEEKLY;BYDAY=MO,WE,FR",
attendees_json='[{"email": "team@example.com", "name": "Team"}]'
)


Delete an event:```python
chronos:delete_event(
    calendar_uid=&quot;assistant&quot;,
    event_uid=&quot;abc-123-def-456&quot;
)

Update an event (partial update):python chronos:update_event( calendar_uid=&quot;assistant&quot;, event_uid=&quot;abc-123-def-456&quot;, location=&quot;Room 202&quot;, # Update location alarm_minutes=&quot;30&quot; # Change reminder to 30 minutes # Other fields remain unchanged )

Documentation

  • Usage - Basic tool usage examples
  • Architecture Guide - System design and components
  • RRULE Guide - Recurring events documentation
  • VTODO/VJOURNAL Guide - Task and journal management
  • Architecture Decisions - ADR records
  • Contributing - Development guidelines
  • Security Policy - Security reporting and practices

Known Issues

See GitHub Issues for current limitations and workarounds.

Changelog

See CHANGELOG.md for version history.

Contributing

See CONTRIBUTING.md for development guidelines.

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Chronos MCP 怎么安装?

在客户端按下面的安装命令接入:python scripts/migrate_to_keyring.py --dry-run。装完在客户端配置里引用同一个包或端点。

Chronos MCP 怎么在客户端里配置?

它的传输方式未标注,在客户端 MCP 配置里按官方文档填写启动命令和参数,保存后重启客户端生效。

Chronos MCP 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Chronos MCP 需要 API Key 吗?

资料标注为无需认证,装好就能连;如果实际调用时报鉴权错误,按官方文档补上凭据。

Chronos MCP 能提供哪些能力?

资料显示能力标签包括 日程管理、Python、日志记录、事件管理。具体工具清单以官方文档为准。

Chronos MCP 需要什么运行环境?

运行时为 Python;属于本地进程,需要在本机装好运行环境。

Chronos MCP 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-05-17。