Ticktick Mcp

Created By
jen6a year ago
Enhance your TickTick workflow with MCP server. Better filtering interface
Overview

What is TickTick MCP Server?

TickTick MCP Server is a tool designed to enhance your TickTick workflow by providing a better filtering interface and improved task management capabilities through the MCP protocol.

How to use TickTick MCP Server?

To use the TickTick MCP Server, you need to set up the server with your TickTick API credentials and run it. You can then integrate it with MCP-compatible applications to manage your tasks effectively.

Key features of TickTick MCP Server?

  • Comprehensive task management including creation, updating, and deletion of tasks.
  • Subtask management to link existing tasks.
  • Advanced task retrieval and filtering options based on various criteria.
  • Project and tag management functionalities.
  • Helper tools for converting datetime strings to TickTick format.

Use cases of TickTick MCP Server?

  1. Automating task management for personal productivity.
  2. Integrating with AI assistants for enhanced task handling.
  3. Streamlining project management workflows.

FAQ from TickTick MCP Server?

  • What is required to run the server?

You need Python >= 3.10 and access to TickTick with API credentials.

  • Is there a cost to use the TickTick MCP Server?

No, it is free to use as it is an open-source project.

  • Can I integrate it with other applications?

Yes, it is designed to work with MCP-compatible applications like Claude Desktop and VS Code.

Server Config

{
  "mcpServers": {
    "ticktick": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/jen6/ticktick-mcp.git",
        "ticktick-mcp"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jen6
Star
6
Language
Python
License
-
Category

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
Crevio

2 days ago