Schema | Todoist Meeting MCP

Todoist Meeting MCP

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.

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

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).

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ajmastra/todoist-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server