Dida MCP Server

Created By
zhongwencoola year ago
A Model Context Protocol (MCP) server for interacting with TickTick/Dida365 task management service. This server provides tools to manage tasks, projects, and tags through the TickTick API.
Overview

What is Dida MCP Server?

Dida MCP Server is a Model Context Protocol (MCP) server designed for interacting with the TickTick/Dida365 task management service, providing tools to manage tasks, projects, and tags through the TickTick API.

How to use Dida MCP Server?

To use Dida MCP Server, clone the repository, install dependencies, authenticate with TickTick/Dida365, and start the server. You can then connect with any MCP-compatible client.

Key features of Dida MCP Server?

  • OAuth-based authentication with TickTick/Dida365 API
  • Comprehensive task management (create, read, update, delete, move tasks)
  • Project management capabilities (create, read, update, delete projects)
  • Batch operations for efficient task management
  • Built-in GTD (Getting Things Done) assistant for task organization
  • Cached data for efficient access to projects and tags

Use cases of Dida MCP Server?

  1. Automating task management workflows in TickTick/Dida365.
  2. Integrating with AI assistants to help users manage their tasks effectively.
  3. Supporting developers in building applications that require task management functionalities.

FAQ from Dida MCP Server?

  • What is the purpose of Dida MCP Server?

It serves as a bridge between AI assistants and the TickTick/Dida365 task management service, enabling efficient task and project management.

  • Is there a cost to use Dida MCP Server?

Dida MCP Server is open-source and free to use.

  • What are the prerequisites for using Dida MCP Server?

You need Node.js, npm, a TickTick/Dida365 account, and a Client ID and Client Secret from the Dida365 Developer Center.

Server Config

{
  "mcpServers": {
    "dida": {
      "command": "node",
      "args": [
        "/path/to/dida-mcp-server/build/index.js"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
zhongwencool
Star
0
Language
TypeScript
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