mcp-todo
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_TODO_API_URL | No | API URL (기본값 설정됨) | |
| MCP_TODO_WORKSPACE_ID | Yes | mcp-todo 앱에서 발급받은 Workspace ID |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_todosC | 일정 목록을 조회합니다. 카테고리나 날짜로 필터링할 수 있습니다. |
| create_todoC | 새로운 일정을 생성합니다. |
| update_todoC | 기존 일정을 수정합니다. |
| delete_todoC | 일정을 삭제합니다. |
| list_memosB | 메모 목록을 조회합니다. 최근 수정순으로 정렬됩니다. |
| get_memoC | 특정 메모의 상세 내용을 조회합니다. |
| create_memoC | 새로운 메모를 생성합니다. |
| update_memoC | 기존 메모를 수정합니다. |
| delete_memoC | 메모를 삭제합니다. |
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 9 tools
Every tool has a clearly distinct purpose with no ambiguity. The tools are cleanly separated into memo and todo categories, each with create, delete, get/list, and update operations, making it easy for an agent to select the correct tool without confusion.
Tool names follow a highly consistent verb_noun pattern throughout, such as create_memo, delete_todo, list_memos, and update_todo. There are no deviations in naming conventions, making the set predictable and readable.
With 9 tools, the count is well-scoped and appropriate for a todo/memo management server. Each tool earns its place by covering essential CRUD operations for both memos and todos, without being overly sparse or bloated.
The tool surface provides complete CRUD/lifecycle coverage for both memos and todos, including create, delete, get, list, and update operations. There are no obvious gaps, ensuring agents can handle all core workflows without dead ends.