Todoist Mcp

Created By
stevengonsalveza year ago
This MCP server enables advanced task and project management via Claude Desktop and other MCP-compatible clients.
Overview

What is Todoist MCP?

Todoist MCP is a Model Context Protocol (MCP) server designed for advanced task and project management, enabling integration with Claude Desktop and other MCP-compatible clients.

How to use Todoist MCP?

To use Todoist MCP, you need to install it via npm or clone the repository, set your Todoist API token, and run the server. You can then interact with it through commands in Claude Desktop.

Key features of Todoist MCP?

  • List, create, update, complete, reopen, and delete tasks.
  • Manage projects, sections, labels, and comments.
  • Fetch project collaborators and manage shared labels.

Use cases of Todoist MCP?

  1. Managing personal and team tasks efficiently.
  2. Organizing projects and sections for better workflow.
  3. Collaborating with team members on shared projects.

FAQ from Todoist MCP?

  • What are the requirements to use Todoist MCP?

You need Node.js, npm or yarn, a Todoist account, and a Todoist API token.

  • Is Todoist MCP free to use?

Yes! Todoist MCP is free to use for everyone.

  • Can I use Todoist MCP with other clients?

Yes! It is compatible with Claude Desktop and other MCP-compatible clients.

Server Config

{
  "mcpServers": {
    "mcp-todoist": {
      "command": "npx",
      "args": [
        "todoist-mcp-server"
      ],
      "env": {
        "TODOIST_API_TOKEN": "your-todoist-token"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
stevengonsalvez
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)

a day ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago