PlanManager MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_planB | 创建一个通用计划. Args: |
| add_stepC | Add a step (sub-task) to an existing plan. Args: plan_id：父计划的id。 name:步骤的名称。 description:有关此步骤的详细信息。 scheduled_at：何时应该完成此步骤（ISO 8601）。 元数据：用于额外数据的JSON字符串。 |
| create_plan_batchA | Create a plan with multiple steps in one go. Useful for generating full schedules like "Weekly Study Plan" or "21-Day Challenge". Args: name: Name of the main plan. children: A JSON string representing a LIST of step objects. Example: '[{"name": "Day 1", "scheduled_at": "2025-12-25"}, {"name": "Day 2"}]' category: Category for the plan and all children. |
| list_plansB | List top-level plans (items without a parent). Args: category: Filter by category (e.g., "travel", "study"). status: Filter by status (e.g., "pending", "completed"). |
| get_plan_detailsB | Get the full details and structure of a plan, including all its steps. |
| update_plan_statusC | Update the status of a plan or step. Args: plan_id: The ID of the item. status: New status ('pending', 'in_progress', 'completed', 'cancelled'). |
| reschedule_planB | Change the scheduled time for a plan or step. Args: plan_id: The ID of the item. new_time: New ISO 8601 date string (e.g., "2025-12-25"). |
| delete_plan_by_nameB | 按名称删除计划（级联删除所有子计划）- 适合语音交互 Args: plan_name: 要删除的计划名称（支持模糊匹配） |
| delete_planC | 删除计划（级联删除所有子计划） |
| cancel_travel_planB | 取消旅行计划 - 当用户时间变动时批量删除所有旅行相关计划 Args: reason: 取消原因（默认为"时间变动"） keyword: 搜索关键词（默认搜索"旅行"相关的计划） |
| get_operation_logsC | 获取操作日志记录 Args: limit: 显示最近的日志条数（默认20条） |
| preview_delete_planA | 预览删除计划的影响（不实际删除） Args: plan_id: 要预览的计划ID |
| create_travel_planC | 快速创建旅行计划模板. Args: destination: 目的地（例如，"云南"、"日本"、"欧洲"） start_date: 开始日期 (YYYY-MM-DD) end_date: 结束日期 (YYYY-MM-DD) budget: 预算金额 description: 旅行描述 |
| create_study_planB | 快速创建学习计划模板. Args: subject: 学习主题（例如，"Python编程"、"英语口语"、"数据分析"） duration_weeks: 学习周期（周数） start_date: 开始日期 (YYYY-MM-DD) description: 学习计划描述 |
| search_plansC | 搜索计划（按名称或描述）. Args: keyword: 搜索关键词 |
| get_plan_statisticsC | 获取计划统计信息. |
| guided_plan_creationC | 引导式创建计划 - 一步步帮助用户创建完整计划 Args: plan_type: 计划类型 ("general", "travel", "study", "work", "health") |
| validate_and_save_planC | 验证计划数据并保存到数据库 Args: name: 计划名称 plan_data: 计划数据的JSON字符串 auto_save: 是否自动保存到数据库 |
| fix_old_datesB | 修复过去的日期 - 将指定年份之前的计划日期更新为指定年份 Args: year: 目标年份（默认为"2025"） |
| backup_plansB | 备份所有计划数据 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 20 tools
There is significant overlap between tools like create_plan, create_plan_batch, create_study_plan, create_travel_plan, and guided_plan_creation, which all create plans with varying approaches. However, descriptions help clarify distinctions (e.g., batch creation vs. guided creation), and tools like backup_plans or fix_old_dates have unique purposes, preventing complete confusion.
Most tools follow a consistent verb_noun pattern (e.g., create_plan, delete_plan, update_plan_status), with clear actions and targets. Minor deviations exist, such as backup_plans (noun_verb) and get_operation_logs (get_noun_noun), but the overall naming is predictable and readable.
With 20 tools, the count feels heavy for a plan management server, bordering on excessive. While the domain supports many operations, some tools (e.g., create_plan_batch vs. guided_plan_creation) could be consolidated, making the set feel slightly bloated rather than well-scoped.
The tool set provides comprehensive coverage for plan management, including CRUD operations (create, get, update, delete), specialized templates (study, travel), batch and guided creation, status updates, rescheduling, search, statistics, logs, backups, and validation. No obvious gaps exist for core workflows in this domain.