Ext Ops Panel
Open dashboard
Comparison

backlog vs io.github.evalor/dida365

backlog is a plugin bundle for AI coding tools published by backloghq. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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-14. 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
Marketplacebacklogio.github.evalor/dida365
Claude Code: claude-plugins-community Listed
Version: 2.4.3
Forks (GitHub): 2
Stars (GitHub): 5
Not marked · First seen
Not listed
Official MCP Registry Not listed 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

backlog vs io.github.evalor/dida365
Factbacklogio.github.evalor/dida365
Marketplaces that list it11
Stars (GitHub) (differs)5 (better)4 (worse)
Forks (GitHub) (differs)2 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (dida365-mcp-server)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 03, secrets among them: 2
Hooks it runs (differs)4Not published
Parts of the bundle (differs)13Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/backloghq/backloggithub.com/evalor/dida365mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

backlog

In its own words, on Claude Code: claude-plugins-community:

Persistent, cross-session task management for Claude Code. 24 tools, 7 skills, and hooks that sync Claude's built-in tasks to a durable backlog. Zero external dependencies.

io.github.evalor/dida365

In its own words, on Official MCP Registry:

MCP Server for Dida365 (TickTick) Task Management Integration

How to run each

backlog As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install backlog@claude-community

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.

Tools each declares

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

Settings each asks for

Only backlog asks for

  • TASKDATA_ROOT

Only io.github.evalor/dida365 asks for

  • DIDA365_CLIENT_ID (secret)
  • DIDA365_CLIENT_SECRET (secret)
  • DIDA365_REGION

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

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

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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