Because it takes Todoist's own filter syntax rather than a reduced set of options, any view you have already built in Todoist is a question you can ask from the editor.
A read view of Todoist built for Cursor. Tasks come back through Todoist's filter query language and are formatted with priority and due date rather than as raw fields.
- Tasks retrieved with any Todoist filter query — today, tomorrow, overdue, a named date, or a date range
- Filtering by priority level 1 to 4, where 1 is the highest
- Complex queries combined, so "due before May 5 and high priority" is a single call
- Each task rendered with its priority, due date and other relevant fields marked with icons instead of run together
Python 3.10 or higher and Poetry. A Todoist account and its API token, which you take from Todoist settings under Integrations → Developer and hand to the server as an environment variable. It reads tasks; nothing here creates or completes them.
One command plus a key — npx -y @smithery/cli install @mingolladaniele/taskMaster-todoist-mcp --client claude, then supply credentials
