🚀 TaskMaster: Todoist MCP for Cursor AI

Created By
mingolladanielea year ago
A lightweight Model Context Protocol (MCP) server that enables natural language interaction with your Todoist tasks directly from your IDE. Built with simplicity and maintainability in mind.
Overview

what is TaskMaster?

TaskMaster is a lightweight Model Context Protocol (MCP) server that enables natural language interaction with your Todoist tasks directly from your IDE, specifically designed for Cursor AI.

how to use TaskMaster?

To use TaskMaster, clone the repository, install the dependencies, set your Todoist API token as an environment variable, and run the server using Python.

key features of TaskMaster?

  • Flexible task filtering using Todoist's powerful filter syntax.
  • Rich task formatting displaying priority, due date, and relevant information.
  • Seamless integration with Cursor AI for direct interaction with Todoist tasks.

use cases of TaskMaster?

  1. Managing tasks directly from your coding environment.
  2. Filtering tasks based on due dates and priority levels.
  3. Enhancing productivity by integrating task management with coding workflows.

FAQ from TaskMaster?

  • Can TaskMaster work with any IDE?

TaskMaster is designed to work specifically with Cursor AI.

  • Is TaskMaster free to use?

Yes! TaskMaster is open-source and free to use.

  • What are the prerequisites for using TaskMaster?

You need Python 3.10 or higher, Poetry for dependency management, and a Todoist account with an API token.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mingolladaniele
Star
4
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago