Ext Ops Panel
Open dashboard
Comparison

CalmLoop Task Manager vs io.github.evalor/dida365

CalmLoop Task Manager is an MCP server published by calmloop.in. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.evalor/dida365 is an MCP server published by evalor. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceCalmLoop Task Managerio.github.evalor/dida365
Official MCP Registry Listed
Version: 2.0.0
No figure published
Not marked · First seen
Listed
Version: 0.2.2
Downloads/month (npm): 293
Downloads/week (npm): 55
Forks (GitHub): 1
Stars (GitHub): 4
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

CalmLoop Task Manager vs io.github.evalor/dida365
FactCalmLoop Task Managerio.github.evalor/dida365
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub4
Forks (GitHub) (differs)No figure on GitHub1
Last releaseNot publishedNot published
Where it runs (differs)Remote server (calmloop.in/mcp)On your machine (dida365-mcp-server)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 2
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/evalor/dida365mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 2 days ago, requires a keyno remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

CalmLoop Task Manager

In its own words, on Official MCP Registry:

Manage tasks, Focus Zone, notes, projects, and task history from compatible AI assistants.

io.github.evalor/dida365

In its own words, on Official MCP Registry:

MCP Server for Dida365 (TickTick) Task Management Integration

How to run each

CalmLoop Task Manager As a remote MCP server

Claude Code
claude mcp add --transport http tasks https://calmloop.in/mcp --header "Authorization: Bearer <YOUR_CALMLOOP_MCP_TOKEN>"

Requires: Authorization header

io.github.evalor/dida365 As a local MCP server: npm package

Claude Code
claude mcp add --env "DIDA365_CLIENT_ID=<YOUR_DIDA365_CLIENT_ID>" --env "DIDA365_CLIENT_SECRET=<YOUR_DIDA365_CLIENT_SECRET>" --transport stdio dida365 -- npx -y dida365-mcp-server

Requires: DIDA365_CLIENT_ID (secret), DIDA365_CLIENT_SECRET (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only CalmLoop Task Manager has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of CalmLoop Task Manager publish no settings it asks for, so we do not compare settings.

What it can do: CalmLoop Task Manager · What it can do: io.github.evalor/dida365 · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built