MCP.so
ログイン

Dida MCP Server

@zhongwencool

基本情報

カテゴリ

その他

トランスポート

stdio

作者

zhongwencool

投稿者

忠文 邓

Dida MCP Server について

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.

Dida MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "dida": {
      "command": "node",
      "args": [
        "/path/to/dida-mcp-server/build/index.js"
      ]
    }
  }
}

Dida MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

What is Dida MCP Server?

Dida MCP Server is a Model Context Protocol (MCP) server that allows AI assistants to interact with the TickTick/Dida365 task management service. It provides tools to manage tasks, projects, and tags through the TickTick API, with built-in support for GTD methodology.

How to use Dida MCP Server?

Install dependencies with npm install, build with npm run build, then run npm run get-token to authenticate via OAuth or username/password. Start the server with npm start and connect any MCP-compatible client using a configuration that points to the server script at dist/index.js.

Key features of Dida MCP Server

  • OAuth-based authentication with TickTick/Dida365 API
  • Full CRUD for tasks and projects
  • Batch operations for tasks (update, delete, move)
  • Built-in GTD Assistant system prompt
  • Efficient caching of projects and tags data

Use cases of Dida MCP Server

  • Let an AI assistant organize your inbox according to GTD principles
  • Automate batch updates, moves, or deletions across multiple tasks
  • Manage projects and tasks conversationally through any MCP-compatible client

よくある質問

1

What are the prerequisites to use Dida MCP Server?

You need Node.js v16 or higher, npm v7 or higher, and a TickTick/Dida365 account. For OAuth authentication, you also need a Client ID and Client Secret from the Dida365 Developer Center.

2

How does authentication work?

Two methods are supported: OAuth Authentication (V1 API) using tokens from the Dida365 Open API, and Username/Password Authentication (V2 API) using session tokens. The `get-access-token` script handles both and stores tokens in `~/.dida-mcp-config.json`.

3

Where is the configuration stored?

Authentication tokens and configuration are stored in `~/.dida-mcp-config.json`, which the server automatically detects and uses on startup.

4

What tools does the server provide?

Tools include check‑auth‑status, project management (list, create, update, delete, refresh‑cache), task management (list, create, get, update, complete, delete, move) and batch variants (batch‑update‑tasks, batch‑delete‑tasks, batch‑move‑tasks), plus a data query tool (list‑cached‑data).

コメント

「その他」の他のコンテンツ