What is the key difference between Backlog and Ticktick Sdk?

Backlog belongs to the Workplace & Productivity category with local stdio execution, while Ticktick Sdk belongs to the Workplace & Productivity category with local stdio execution.

How do I install Backlog or Ticktick Sdk in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Backlog and Ticktick Sdk free or paid?

Backlog operates under a Free / Open Source model (No auth required). Ticktick Sdk operates under a Free / Open Source model (OAuth 2.0).

Which MCP server has more tools and community activity?

Backlog lists 24 tools with 3 views and 5 GitHub stars. Ticktick Sdk lists 43 tools with 3 views and 141 GitHub stars.

Can I use both Backlog and Ticktick Sdk together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Backlog vs Ticktick Sdk

In-depth architectural comparison of the Backlog and Ticktick Sdk MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Backlog

Workplace & Productivity · Local stdio

Quality: 47/100 (Fair) | Auth: No auth required

Ticktick Sdk

Workplace & Productivity · Local stdio

Quality: 56/100 (Good) | Auth: OAuth 2.0

Verdict Summary: Choose Backlog if you need specialized Workplace & Productivity tools running via a local process. Choose Ticktick Sdk if your workspace requires Workplace & Productivity integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Backlog when:

You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: TASKDATA, TASKDATA_ROOT, BACKLOG_NAMESPACE, BACKLOG_AUTO_NAMESPACE, BACKLOG_AGENT_ID, BACKLOG_BACKEND, BACKLOG_S3_BUCKET, BACKLOG_S3_REGION.
Primary tools included: task_list, task_count, task_add.

Explore Backlog Details

Choose Ticktick Sdk when:

You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Free / Open Source).
You have access to required keys: TICKTICK_CLIENT_ID, TICKTICK_CLIENT_SECRET, TICKTICK_ACCESS_TOKEN, TICKTICK_USERNAME, TICKTICK_PASSWORD.

Feature & Specification Comparison

Specification	Backlog backloghq Workplace & Productivity	Ticktick Sdk dev-mirzabicer Workplace & Productivity
Summary	Persistent, cross-session task management for Claude Code. 24 MCP tools, 7 skills, and agent coordination with event-sourced storage and per-project isolation.	Comprehensive async Python SDK for TickTick with MCP server support. Features 45 tools for tasks, projects, tags, habits, focus/pomodoro sessions, and user analytics.
Category & Scope

Tools & Capabilities Breakdown

Backlog Tools (24)

task_list

Query tasks with filter syntax. Returns JSON array with all fields.

task_count

Count tasks matching a filter. Same syntax as task_list.

task_add

Create a new pending task. Only description required; all other fields optional.

task_log

Record already-completed work directly in completed status.

task_modify

Partial-update one or more tasks matching a filter. Only provided fields change.

task_duplicate

Copy an existing task with optional field overrides.

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Backlog Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "backloghq-backlog": {
      "command": "npx",
      "args": [
        "-y",
        "backloghq-backlog"
      ],
      "env": {
        "TASKDATA": "YOUR_TASKDATA_HERE",
        "TASKDATA_ROOT": "YOUR_TASKDATA_ROOT_HERE",
        "BACKLOG_NAMESPACE": "YOUR_BACKLOG_NAMESPACE_HERE",
        "BACKLOG_AUTO_NAMESPACE": "YOUR_BACKLOG_AUTO_NAMESPACE_HERE",
        "BACKLOG_AGENT_ID": "YOUR_BACKLOG_AGENT_ID_HERE",
        "BACKLOG_BACKEND": "YOUR_BACKLOG_BACKEND_HERE",
        "BACKLOG_S3_BUCKET": "YOUR_BACKLOG_S3_BUCKET_HERE",
        "BACKLOG_S3_REGION": "YOUR_BACKLOG_S3_REGION_HERE"
      }
    }
  }
}

Ticktick Sdk Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "dev-mirzabicer-ticktick-sdk": {
      "command": "uvx",
      "args": [
        "ticktick-sdk"
      ],
      "env": {
        "TICKTICK_CLIENT_ID": "YOUR_TICKTICK_CLIENT_ID_HERE",
        "TICKTICK_CLIENT_SECRET": "YOUR_TICKTICK_CLIENT_SECRET_HERE",
        "TICKTICK_ACCESS_TOKEN": "YOUR_TICKTICK_ACCESS_TOKEN_HERE",
        "TICKTICK_USERNAME": "YOUR_TICKTICK_USERNAME_HERE",
        "TICKTICK_PASSWORD": "YOUR_TICKTICK_PASSWORD_HERE"
      }
    }
  }
}

Frequently Asked Questions

Backlog is categorized under Workplace & Productivity and uses a local stdio subprocess. In contrast, Ticktick Sdk belongs to Workplace & Productivity using local stdio subprocess. Select Backlog when you need capabilities focused on workplace & productivity and Ticktick Sdk when you require tools for workplace & productivity.

More alternatives to Backlog More alternatives to Ticktick Sdk Workplace & Productivity category hub