Todoist Meeting MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TODOIST_API_TOKEN | Yes | Your Todoist API token, found in Settings -> Integrations -> Developer. |
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 |
|---|---|
| parse_meeting_notesA | Parse raw meeting note text to extract action items, decisions, follow-ups, and deadlines; create Todoist tasks with inferred due dates and priorities. Optionally route to a target project by name. |
| create_taskA | Create a single Todoist task. Supports project/section by name, natural language due date, priority 1-4, labels, and optional parent task (subtask). |
| create_subtasksC | Create multiple subtasks under a parent task. Parent is found by name (fuzzy match). |
| list_projectsB | List all Todoist projects with their IDs, names, and section names. Use for routing context. |
| list_tasksB | List tasks with optional filters: project_name, section_name, priority (1-4), due_today. |
| update_taskC | Update a task found by name. Can change content, description, due date, priority, project, or section. |
| complete_taskC | Mark a task as complete. Task is found by name (fuzzy match). |
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 7 tools
Each tool has a clearly distinct purpose with no overlap: list_projects and list_tasks are for retrieval, create_task and create_subtasks for creation, update_task and complete_task for modification, and parse_meeting_notes for a specialized parsing function. The descriptions clearly differentiate their roles, preventing agent misselection.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., list_projects, create_task, update_task). This predictability makes the set easy to navigate and understand, with no deviations in naming conventions.
With 7 tools, this server is well-scoped for managing Todoist tasks and projects, covering core operations like listing, creating, updating, and completing tasks, plus a specialized parsing tool. Each tool earns its place without bloat or thinness.
The tool set provides complete CRUD/lifecycle coverage for the Todoist domain: list_projects and list_tasks for retrieval, create_task and create_subtasks for creation, update_task for updates, and complete_task for deletion/completion. The parse_meeting_notes tool adds a valuable specialized workflow, leaving no obvious gaps.