MCP I Cal Server

MCPAI代理

提供方 未标注

AI代理 HTTP · 远程 API Key 社区 / 第三方
查看接入方式

全面解析MCP Calender AgentMCP Server的核心功能、安装配置和实用案例。作为顶级Model Context Protocol服务器,MCP Calender Agent能让AI助手访问实时数据、执行操作,为您提供更智能的工作体验和自动化解决方案。

一句话选型结论

按资料字段整理

MCP I Cal Server 属于AI代理类 MCP 服务器,HTTP · 远程,API Key,有可直接复制的远程端点配置。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

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

工具与能力

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

能力标签

安装与配置

HTTP · 远程 API Key
连远程 HTTPS 端点,通常为 Streamable HTTP
pip install openai pyobjc

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

  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

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

  3. 3
    写入客户端配置

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

  4. 4
    验证是否可用

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

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

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

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

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

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
MCP I Cal Server当前 未标注 HTTP · 远程 远程部署 有 2026-05-17
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类AI代理本站按上游分类展示
连接方式HTTP · 远程连远程 HTTPS 端点,通常为 Streamable HTTP
鉴权方式API Key远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Python本地安装时用到的包标识与运行时
部署类型远程部署上游给出的部署形态
最近核验2026-05-17上游最后核验时间

详细介绍

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

MCP iCal Server

🗓️ Agent-Powered Calendar Management for macOS

> This project is based on Omar-V2/mcp-ical with a reimplemented user interaction layer using an agent-based approach.

🌟 Overview

Transform how you interact with your macOS calendar using a dedicated AI agent! This MCP iCal server leverages the OpenAI Agent SDK to provide a single, powerful entry point for all your calendar operations.

Unlike traditional MCP implementations that expose multiple tools, this server uses an agent-based approach:
- 🧠 Single Tool Interface: Just one MCP tool (send_to_calendar_agent) that delegates to a specialized calendar agent
- 🤖 Stateful Conversations: The agent maintains context between requests in the same session
- 🔄 Zero-Config Operation: Natural language processing handled automatically by the specialized agent```
You: "What's my schedule for next week?"
Claude: "Let me check that for you..."
[Calendar agent processes request and returns clean schedule]

You: "Add a lunch meeting with Sarah tomorrow at noon"
Claude: "Event created: Lunch with Sarah, tomorrow at 12:00 PM"


## ✨ Features

### 📅 Event Creation
Transform natural language into calendar events instantly!```
"Schedule a team lunch next Thursday at 1 PM at Bistro Garden"
↓
📎 Created: Team Lunch
   📅 Thursday, 1:00 PM
   📍 Bistro Garden

Supported Features:

  • Custom calendar selection
  • Location and notes
  • Smart reminders
  • Recurring events

Power User Examples:```

🔄 Recurring Events:
"Set up my weekly team sync every Monday at 9 AM with a 15-minute reminder"

📝 Detailed Events:
"Schedule a product review meeting tomorrow from 2-4 PM in the Engineering calendar,
add notes about reviewing Q1 metrics, and remind me 1 hour before"

📱 Multi-Calendar Support:
"Add a dentist appointment to my Personal calendar for next Wednesday at 3 PM"


### 🔍 Smart Schedule Management & Availability
Quick access to your schedule with natural queries:```
"What's on my calendar for next week?"
↓
📊 Shows your upcoming events with smart formatting

"When am I free to schedule a 2-hour meeting next Tuesday?"
↓
🕒 Available time slots found:
   • Tuesday 10:00 AM - 12:00 PM
   • Tuesday 2:00 PM - 4:00 PM

✏️ Intelligent Event Updates

Modify events naturally:```
"Move tomorrow's team meeting to 3 PM instead"
↓
✨ Meeting rescheduled to 3:00 PM


#### Update Capabilities:
- Time and date modifications
- Calendar transfers
- Location updates
- Note additions
- Reminder adjustments
- Recurring pattern changes

### 📊 Calendar Management
- View all available calendars
- Smart calendar suggestions
- Seamless Google Calendar integration when configured with iCloud

> 💡 **Pro Tip**: Since you can create events in custom calendars, if you have your Google Calendar synced with your iCloud Calendar, you can use this MCP server to create events in your Google Calendar too! Just specify the google calendar when creating/updating events.

## 🚀 Quick Start

> 💡 **Note**: While these instructions focus on setting up the MCP server with Claude for Desktop, this server can be used with any MCP-compatible client. For more details on using different clients, see the MCP documentation.

### Prerequisites
- uv package manager
- macOS with Calendar app configured
- An MCP client - Claude for desktop is recommended
- OpenAI API key (set as `OPENAI_API_KEY` environment variable)

### Installation

Whilst this MCP server can be used with any MCP compatible client, the instructions below are for use with Claude for desktop.

1. **Clone and Setup**```bash
# Clone the repository
git clone https://github.com/yourusername/mcp-ical.git
cd mcp-ical

# Install dependencies
uv sync
  1. Configure Claude for Desktop with API Key

Create or edit ~/Library/Application\ Support/Claude/claude_desktop_config.json and include your OpenAI API key as an environment variable:```json
{
"mcpServers": {
"mcp-ical": {
"command": "uv",
"args": [
"--directory",
"/ABSOLUTE/PATH/TO/PARENT/FOLDER/mcp-ical",
"run",
"mcp-ical"
],
"env": {
"OPENAI_API_KEY": "your-api-key-here"
}
}
}
}


3. **Launch Claude for Calendar Access**

> ⚠️ **Critical**: Claude must be launched from the terminal to properly request calendar permissions. Launching directly from Finder will not trigger the permissions prompt.```bash
/Applications/Claude.app/Contents/MacOS/Claude
  1. Start Using!```
    Try: "What's my schedule looking like for next week?"

> 🔑 **Note**: When you first use a calendar-related command, macOS will prompt for calendar access. This prompt will only appear if you launched Claude from the terminal as specified above.

## 🧪 Testing

> ⚠️ **Warning**: Tests will create temporary calendars and events. While cleanup is automatic, only run tests in development environments.```bash
# Install dev dependencies
uv sync --dev

# Run test suite
uv run pytest tests

🧠 How It Works

This implementation uses a unique architecture:

  1. A single MCP tool (send_to_calendar_agent) is exposed to the client
  2. When invoked, this tool passes the request to a specialized calendar agent built with the OpenAI Agent SDK
  3. The agent processes the natural language request and calls the appropriate calendar operations
  4. Results are formatted and returned to the client

This approach offers several advantages:
- Simplified client integration: Only one tool to invoke
- Improved context handling: The agent maintains conversation state
- More natural interactions: The specialized agent understands calendar-specific terminology and intent

❓ How This Project Differs From The Original

This implementation maintains much of the core calendar functionality from Omar-V2/mcp-ical but completely reimplements the user interaction layer:

  1. Single Entry Point: Instead of exposing multiple MCP tools directly to the client, we've implemented a single entry point that delegates to an OpenAI-powered agent
  2. Stateful Conversations: Added conversation context tracking between requests in the same session
  3. Simplified Client Integration: Clients only need to know about one tool instead of multiple calendar operations

The core calendar operations (event creation, listing, etc.) and macOS integration remain largely unchanged from the original implementation.

🐛 Known Issues

Recurring Events

  • Non-standard recurring schedules may not always be set correctly
  • Better results with more powerful LLM models
  • Reminder timing for recurring all-day events may be off by one day

🤝 Contributing

Feedback and contributions are welcomed! Here's how you can help:

  1. Fork the repository
  2. Create your feature branch
  3. Commit your changes
  4. Push to the branch
  5. Open a Pull Request

📝 License

This project is licensed under the MIT License - see the LICENSE file for details.

📝 Acknowledgments

  • Original Project: Based on Omar-V2/mcp-ical by Omar-V2
  • Built with Model Context Protocol
  • Calendar integration built with PyObjC
  • Agent capabilities powered by OpenAI Agent SDK

常见问题

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

在客户端按下面的安装命令接入:pip install openai pyobjc。装完在客户端配置里引用同一个包或端点。

MCP I Cal Server 怎么在客户端里配置?

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

MCP I Cal Server 收费吗?

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

MCP I Cal Server 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

MCP I Cal Server 能提供哪些能力?

资料显示能力标签包括 日程管理、自然语言、Python、AI代理。具体工具清单以官方文档为准。

MCP I Cal Server 需要什么运行环境?

运行时为 Python;属于远程端点,不需要在本地装运行时。

MCP I Cal Server 是本地还是远程?

它是远程端点,连服务地址即可。传输方式为HTTP · 远程。

热门专题

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

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