todoist

This MCP server enables natural language interaction with Todoist through Claude by exposing a set of tools to manage tasks. It supports creating tasks with optional descriptions, due dates, and priority; retrieving and filtering tasks by due date, priority, or project; updating tasks using natural language search; marking tasks as complete; and deleting tasks. The server relies on the Todoist API token provided via environment variables to perform actions on your Todoist account. To use, run the server through your preferred client (e.g., Claude Desktop) with the appropriate MCP server configuration, then issue requests that map to the available tools (todoist_create_task, todoist_get_tasks, todoist_update_task, todoist_complete_task, todoist_delete_task). The tools interpret natural language inputs, allowing you to say things like creating a high-priority task due tomorrow or listing tasks due this week. Ensure your Todoist API token is valid and that the token has the necessary permissions to read and modify tasks.

Prerequisites:

• Node.js (LTS version) and npm installed on your machine
• Access to the internet to install the MCP server package via npm

Installation steps:

1. Install Node.js and npm if not already installed. Refer to https://nodejs.org/ for instructions.

2. Install the Todoist MCP Server from npm (global installation is optional; you can run via npx):

   npm install -g @abhiz123/todoist-mcp-server

3. Verify installation by listing help or running a quick test command (if provided by the package).

4. Configure your Claude Desktop or hosting environment to point to the MCP server using the provided mcp_config snippet (see the README for how to integrate with Claude Desktop).

Optional: If you prefer using npx directly without a global install, you can run commands as shown in the mcp_config example using npx with the package name.

Notes and tips:

• Always provide a valid Todoist API token with the necessary permissions. Store tokens securely and avoid hard-coding them in code.
• The server uses the Todoist API, so rate limits may apply; design prompts to minimize excessive requests.
• If tasks fail to be created or updated, double-check token scopes and that the Todoist account contains the referenced projects or attributes.
• The tool names (todoist_create_task, todoist_get_tasks, todoist_update_task, todoist_complete_task, todoist_delete_task) should be invoked via the MCP interface; refer to Claude prompts and sample usages in the README to craft natural language requests.
• When running locally, ensure network access to Todoist’s API endpoints is available and not blocked by firewalls or proxies.
• If you change the API token, update the environment variable in your MCP runner configuration accordingly.