What is the key difference between Ticktick Sdk and Teamwork MCP?

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

How do I install Ticktick Sdk or Teamwork MCP 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 Ticktick Sdk and Teamwork MCP free or paid?

Ticktick Sdk operates under a Free / Open Source model (OAuth 2.0). Teamwork MCP operates under a BYOK (Pay Provider Direct) model (API Key required).

Which MCP server has more tools and community activity?

Ticktick Sdk lists 43 tools with 3 views and 141 GitHub stars. Teamwork MCP lists 5 tools with 2 views and 25 GitHub stars.

Can I use both Ticktick Sdk and Teamwork MCP 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

Ticktick Sdk vs Teamwork MCP

In-depth architectural comparison of the Ticktick Sdk and Teamwork MCP 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

Ticktick Sdk

Workplace & Productivity · Local stdio

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

Teamwork MCP

Workplace & Productivity · Local stdio

Quality: 43/100 (Fair) | Auth: API Key required

Verdict Summary: Choose Ticktick Sdk if you need specialized Workplace & Productivity tools running via a local process. Choose Teamwork MCP 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 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.
Primary tools included: ticktick_create_tasks, ticktick_get_task, ticktick_list_tasks.

Explore Ticktick Sdk Details

Choose Teamwork MCP when:

You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: TW_MCP_SERVER_ADDRESS, TW_MCP_BEARER_TOKEN, NODE_EXTRA_CA_CERTS.

Feature & Specification Comparison

Specification	Ticktick Sdk dev-mirzabicer Workplace & Productivity	Teamwork MCP teamwork Workplace & Productivity
Summary	Comprehensive async Python SDK for TickTick with MCP server support. Features 45 tools for tasks, projects, tags, habits, focus/pomodoro sessions, and user analytics.	Project and resource management platform that keeps your client projects on track, makes managing resources a breeze, and keeps your profits on point.
Category & Scope	Workplace & Productivity

Tools & Capabilities Breakdown

Ticktick Sdk Tools (43)

ticktick_create_tasks

Create 1-50 tasks with titles, dates, tags, etc.

ticktick_get_task

Get task details by ID

ticktick_list_tasks

List tasks (active/completed/abandoned/deleted via status filter)

ticktick_update_tasks

Update 1-100 tasks (includes column assignment)

ticktick_complete_tasks

Complete 1-100 tasks

ticktick_delete_tasks

Delete 1-100 tasks (moves to trash)

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).

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"
      }
    }
  }
}

Teamwork MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "teamwork-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "teamwork-mcp"
      ],
      "env": {
        "TW_MCP_SERVER_ADDRESS": "YOUR_TW_MCP_SERVER_ADDRESS_HERE",
        "TW_MCP_BEARER_TOKEN": "YOUR_TW_MCP_BEARER_TOKEN_HERE",
        "NODE_EXTRA_CA_CERTS": "YOUR_NODE_EXTRA_CA_CERTS_HERE"
      }
    }
  }
}

Frequently Asked Questions

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

More alternatives to Ticktick Sdk More alternatives to Teamwork MCP Workplace & Productivity category hub