renfield-mcp-calendar
Unified MCP server for calendar access connecting Exchange (EWS), Google Calendar, and CalDAV through a single MCP interface, enabling multi-calendar event management via natural language.
README
renfield-mcp-calendar
Unified MCP server for calendar access — connect Exchange (EWS), Google Calendar, and CalDAV (Nextcloud, ownCloud, Radicale) through a single Model Context Protocol interface.
Features
- Multi-calendar — Configure multiple calendar accounts via YAML, query them individually or all at once
- Cross-calendar merge —
list_eventswithout a calendar parameter returns events from ALL calendars sorted chronologically - Three backends — Exchange Web Services (EWS), Google Calendar API, CalDAV
- No passwords in config — Credentials referenced via environment variable names
- Lazy connections — Backend clients are initialized on first use, not at startup
- Async-ready — All blocking I/O wrapped with
asyncio.run_in_executor - Google OAuth2 helper — Built-in
--auth googleCLI for initial token setup
Installation
pip install renfield-mcp-calendar
Or directly from GitHub:
pip install "renfield-mcp-calendar @ https://github.com/ebongard/renfield-mcp-calendar/archive/refs/heads/main.tar.gz"
Configuration
Set CALENDAR_CONFIG to point to your YAML config file (default: /config/calendar_accounts.yaml).
Example calendar_accounts.yaml
calendars:
# Exchange 2019 (on-premise, direct EWS endpoint)
- name: work
label: "Work Calendar"
type: ews
ews_url: "https://exchange.example.com/EWS/Exchange.asmx"
username_env: CALENDAR_WORK_USERNAME
password_env: CALENDAR_WORK_PASSWORD
# Google Calendar (OAuth2 Desktop Flow)
- name: family
label: "Family Calendar"
type: google
calendar_id: "primary"
credentials_file: "/config/google_calendar_credentials.json"
token_file: "/data/google_calendar_token.json"
# Nextcloud / CalDAV
- name: club
label: "Club Calendar"
type: caldav
url: "https://nextcloud.example.com/remote.php/dav/calendars/user/club/"
username_env: CALENDAR_CLUB_USERNAME
password_env: CALENDAR_CLUB_PASSWORD
Security: Passwords and tokens are never stored in the YAML file — use *_env fields to reference environment variable names.
Backend-specific notes
| Backend | Library | Auth | Notes |
|---|---|---|---|
| EWS | exchangelib | NTLM/Basic | Direct EWS URL, no Autodiscover needed |
| google-api-python-client | OAuth2 Desktop Flow | Token auto-refresh, one-time browser auth | |
| CalDAV | caldav | Basic Auth | Works with Nextcloud, ownCloud, Radicale, etc. |
Google Calendar setup (one-time)
- Google Cloud Console → Create project → Enable Google Calendar API
- Create OAuth2 credentials (Desktop App) → Download
credentials.json - Place as
google_calendar_credentials.jsonin your config directory - Run the auth flow:
python -m renfield_mcp_calendar --auth google --calendar family - Complete the browser-based authorization — token is saved automatically
MCP Tools
| Tool | Parameters | Description |
|---|---|---|
list_calendars |
— | List all configured calendar accounts |
list_events |
calendar?, start, end |
Events from one or all calendars. Empty calendar = merged from all. |
create_event |
calendar, title, start, end, description?, location? |
Create a new event |
update_event |
calendar, event_id, title?, start?, end?, ... |
Update specific fields of an event |
delete_event |
calendar, event_id |
Delete an event |
get_event |
calendar, event_id |
Get a single event with full details |
Example queries (via LLM)
- "Was steht heute an?" →
list_events()(all calendars, today) - "Was steht im Firmenkalender diese Woche?" →
list_events(calendar="work", start="...", end="...") - "Erstelle einen Familientermin morgen um 14 Uhr: Zahnarzt" →
create_event(calendar="family", ...) - "Bin ich morgen Nachmittag frei?" →
list_events(start="...", end="...")
Usage
# Run as MCP server (stdio transport)
python -m renfield_mcp_calendar
# Or via entry point
renfield-mcp-calendar
# Google OAuth2 setup (one-time)
python -m renfield_mcp_calendar --auth google --calendar family
Claude Desktop / MCP client config
{
"mcpServers": {
"calendar": {
"command": "python",
"args": ["-m", "renfield_mcp_calendar"],
"env": {
"CALENDAR_CONFIG": "/path/to/calendar_accounts.yaml",
"CALENDAR_WORK_USERNAME": "user@example.com",
"CALENDAR_WORK_PASSWORD": "secret"
}
}
}
}
Development
# Install with dev dependencies
pip install -e ".[dev]"
# Run tests (29 tests)
pytest tests/ -v
License
MIT
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。