Todoist

Created By
stanislavlysenko0912a year ago
Overview

what is Todoist MCP Server?

Todoist MCP Server is a Model Context Protocol (MCP) server implementation that integrates Claude and other AI assistants with Todoist, enabling natural language task management.

how to use Todoist MCP Server?

To use the Todoist MCP Server, you need to obtain a Todoist API token and configure it in your AI assistant's configuration file. You can then interact with Todoist using natural language commands.

key features of Todoist MCP Server?

  • Complete Todoist API Integration for natural language access to tasks.
  • Manage tasks: create, update, close, reopen, and delete tasks using conversational language.
  • Project management capabilities including creating and managing projects and sections.
  • Support for adding and managing comments on tasks and projects.
  • Label management for personal and shared labels.

use cases of Todoist MCP Server?

  1. Managing daily tasks through voice commands.
  2. Creating and organizing projects for personal or team use.
  3. Adding comments and labels to tasks for better organization.

FAQ from Todoist MCP Server?

  • How do I get a Todoist API token?

Log in to your Todoist account, navigate to Settings → Integrations, and find your API token under "Developer".

  • Can I use this with any AI assistant?

Yes, it is designed to work with AI assistants that support the Model Context Protocol.

  • Is there a cost associated with using Todoist MCP Server?

The server itself is free to use, but you need a Todoist account which may have its own pricing.

Server Config

{
  "mcpServers": {
    "todoist": {
      "command": "npx",
      "args": [
        "-y",
        "todoist-mcp"
      ],
      "env": {
        "API_KEY": "your_todoist_api_token_here"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
stanislavlysenko0912
Star
-
Language
-
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)

2 days ago