MCP Todoist
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CONVEX_DEPLOYMENT | No | Your Convex deployment name | |
| TODOIST_API_TOKEN | Yes | Your Todoist API token | |
| NEXT_PUBLIC_CONVEX_URL | No | Your Convex URL (e.g., https://your-convex-url.convex.cloud) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-tasksB | Get all the tasks from Todoist |
| get-projectsB | Get all the projects from Todoist |
| get-project-idC | Get the id of the project from Todoist |
| add-task-to-projectC | Add task to a specific Project in Todoist |
| add-task-to-any-projectC | Add task to a any Project in Todoist |
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 5 tools
There is significant overlap and confusion between 'add-task-to-any-project' and 'add-task-to-project'—they appear to serve nearly identical purposes, with only subtle differences in wording that could easily lead to misselection. The other tools are more distinct but the core task-adding functionality is ambiguous.
The naming follows a consistent kebab-case pattern (e.g., 'add-task-to-any-project', 'get-projects') throughout all tools, which is predictable and readable. There are no deviations in style, though the specific verb choices could be more standardized.
With 5 tools, the count is reasonable for a Todoist integration, covering core operations like adding tasks and retrieving projects/tasks. It's slightly thin but manageable for basic functionality without feeling overloaded.
The toolset has significant gaps for a Todoist domain: it lacks update or delete operations for tasks or projects, and there is no way to manage task completion or priorities. This incomplete coverage will likely cause agent failures in common workflows.