todoist

This MCP server provides integration with Todoist, enabling natural language control over Todoist tasks, projects, sections, labels, and more. It exposes a suite of tools that map to the Todoist REST API v2 (and Sync API), including creating, updating, listing, and deleting tasks, projects, labels, and comments, as well as moving and organizing items. You can query by name, batch process multiple items in a single request, and use conversational prompts to perform common Todoist actions without manually handling IDs. To use it, ensure your Todoist API token is available to the server (via the API_KEY environment variable in the mcpServers configuration). Then invoke the server through MCP-enabled clients (e.g., Claude, Codex, or other MCP clients) using the configured command (npx -y todoist-mcp). The server will authenticate requests with your API token and respond with structured results for the requested Todoist operations.

Prerequisites:

• Node.js (including npm) installed on your machine
• Internet access to fetch packages from npm

1. Clone the MCP server repository or prepare the project directory:

• git clone https://github.com/stanislavlysenko0912/todoist-mcp-server.git
• cd todoist-mcp-server

2. Install dependencies:

• npm install

3. Build the project (if applicable) and prepare for running via MCP inspector (as shown in the Development section):

• npm run build
• npx @modelcontextprotocol/inspector -e YOUR_API_KEY_HERE node dist/index.js

4. Run the MCP server via MCP config (see mcp_config in this document):

• npm install -g todoist-mcp # if you rely on the separate package, otherwise use the npx command per config
• Use the configured mcpServers.todoist entry: npx -y todoist-mcp

5. Verify the server is running and reachable by your MCP client and that the API_KEY is correctly applied.

Tips and notes:

• Ensure your Todoist API token is kept secret. Use environment variables in your MCP configuration (API_KEY) to avoid hardcoding.
• If you encounter authentication errors, double-check that the API token has the necessary Todoist permissions and that it is correctly wired in the MCP environment.
• The server supports batch operations and name-based lookups for tasks, projects, sections, labels, and collaborators, which can simplify prompts for your AI assistant.
• If you need to upgrade the Todoist MCP package, update the dependency version in your deployment environment and rebuild as needed.
• For Codex, Claude, or other MCP clients, ensure the client’s transport and scope settings align with your server configuration (e.g., stdio with the appropriate environment).
• Review rate limits and error responses from Todoist API to implement robust retry logic in your prompts.