# TickTick MCP MCP Server

> **TickTick MCP MCP Server** is a hosted, multitenant Model Context Protocol (MCP) server run by **MewCP** (https://mewcp.com), giving AI agents managed access to TickTick MCP.
>
> MewCP takes care of all MCP infrastructure for you — credential storage, OAuth flows,
> token refresh, and production-grade auto-scaling — so your AI agents can connect to
> third-party services and run freely without you managing any MCP server yourself.
>
> Server page:  https://mewcp.com/mcp/ticktick-mcp
> MewCP docs:   https://docs.mewcp.com
> Full catalog: https://mewcp.com/llms.txt

---

## About

TickTick helps users organize daily work by creating and updating tasks, managing to-do lists, setting due dates and reminders, organizing tasks with tags, and tracking progress across projects and routines.

---

## Details

- Server ID: `ticktick-mcp`
- Version: 1.0.0
- Tools: 57
- Authentication: OAuth, managed by MewCP
- Transport: http

---

## Access

The gateway URL below serves your **entire MewCP toolset**, not this server on its
own. Pasting a config snippet is not enough — TickTick MCP has to be in the toolset
first. In order:

1. Add TickTick MCP to your toolset at https://mewcp.com/mcp/ticktick-mcp
2. Connect your TickTick MCP account (OAuth); MewCP stores the credential and attaches it to each call
3. Copy your MewCP API key from the dashboard (Developer)
4. Configure your client with the snippet for it below

Once connected, an agent does **not** see this server's tools as top-level tools.
It sees four meta-tools and reaches everything through them:

- `search(query)` — find tools by keyword across the toolset
- `get_schema(tools)` — full description and arguments for the tools you picked
- `list_accounts(provider)` — only when one app has several connected accounts
- `call_tool(server_maskedId, tool_name, args)` — execute

So the list below is what `search` can return for this server, not a set of
callable tool names on their own.

---

## Tools (57)

Descriptions are truncated to 160 characters; call `get_schema`
for the full text and the argument schema. Where a tool is annotated, its type
is shown — treat `destructive` as irreversible.

- `list_projects` _(read)_ — List projects. Supports offset/limit pagination; unpaginated results also include virtual "inbox".
- `get_project_by_id` _(read)_ — Get project details by projectId.
- `get_project_with_undone_tasks` _(read)_ — Get project details and all undone tasks in the project by projectId.
- `list_project_members` _(read)_ — List members of a shared project. Use a returned username when assigning a task in that project.
- `create_project` _(write)_ — Create a new project (list) in TickTick.
- `update_project` _(write)_ — Update an existing project by projectId.
- `create_task` _(write)_ — Create a new task in TickTick.
- `update_task` _(write)_ — Update a task. Set parentId='' to detach; set startDate/dueDate to "1970-01-01T00:00:00.000+0000" to clear. completedTime can only correct a closed task's…
- `assign_task` _(write)_ — Assign a task in a shared project to one of the project's members.
- `unassign_task` _(write)_ — Remove the assignee from a task in a shared project.
- `get_task_in_project` _(read)_ — Get a task by projectId and taskId.
- `complete_task` _(write)_ — Mark a task as completed by projectId and taskId.
- `complete_checklist_item` _(write)_ — Complete one checklist item in a CHECKLIST task.
- `delete_task` _(destructive)_ — Delete a task by projectId and taskId.
- `complete_tasks_in_project` _(write)_ — Complete multiple tasks in a project. Maximum 20 tasks per request.
- `list_habits` _(read)_ — List all habits of the current user.
- `list_habit_sections` _(read)_ — List all habit sections of the current user.
- `get_habit` _(read)_ — Get habit details by habitId.
- `create_habit` _(write)_ — Create a new habit in TickTick.
- `update_habit` _(write)_ — Update an existing habit by habitId.
- `upsert_habit_checkins` _(write)_ — Create or update check-ins for a habit by habitId.
- `get_habit_checkins` _(read)_ — Get habit check-ins by habitIds and yyyyMMdd int stamp range.
- `get_focus` _(read)_ — Get a single focus record by focusId and type.
- `get_focuses_by_time` _(read)_ — Get focus records by time range and type. The time range must not exceed one month.
- `delete_focus` _(destructive)_ — Delete a focus record by focusId and type.
- `create_focus` _(write)_ — Create a focus record. Required: startTime, endTime, type (0=pomodoro, max 3h; 1=timing, max 12h). Optional: taskId, habitId, note.
- `update_focus` _(write)_ — Update an existing focus record. The focus type is required.
- `search_task` _(read)_ — Search tasks by keyword. Returns a list of matching tasks with taskId, title, and url.
- `search` _(read)_ — Search tasks in TickTick. Return a list of relevant result with IDS, title and URLs.
- `fetch` _(read)_ — Fetch the full contents of a task by its ID.
- `list_undone_tasks_by_date` _(read)_ — List undone tasks within a date range. The maximum range is 14 days between startDate and endDate.
- `list_undone_tasks_by_time_query` _(read)_ — List undone tasks by time query: today, last24hour, last7day, tomorrow, next24hour, next7day.
- `get_task_by_id` _(read)_ — Get full task details by taskId.
- `filter_tasks` _(read)_ — Filter tasks by various criteria including date range, project IDs, priority, tag, kind and status.
- `list_completed_tasks_by_date` _(read)_ — Get completed tasks based on specified search criteria including project IDs and date range.
- `move_task` _(write)_ — Move tasks to different projects. Used for reorganizing tasks across projects.
- `batch_add_tasks` _(write)_ — Batch add multiple tasks to TickTick. Each task should have required fields filled in.
- `batch_update_tasks` _(write)_ — Batch update existing tasks.
- `get_user_preference` _(read)_ — Get user preferences including timezone settings.
- `list_columns` _(read)_ — List all columns in a project by projectId.
- `create_column` _(write)_ — Create a new column in a project.
- `update_column` _(write)_ — Update an existing column in a project by columnId.
- `get_comment` _(read)_ — Get comments for a task by projectId and taskId.
- `add_comment` _(write)_ — Add a comment to a task. Comment content is plain text, max 1024 characters.
- `delete_comment` _(destructive)_ — Delete a comment from a task by comment id.
- `list_countdowns` _(read)_ — List all countdowns of the current user.
- `list_project_groups` _(read)_ — List all project groups of the current user.
- `create_project_group` _(write)_ — Create a new project group.
- `update_project_group` _(write)_ — Update an existing project group by projectGroupId.
- `delete_project_group` _(destructive)_ — Delete a project group by projectGroupId.
- `list_tags` _(read)_ — List all tags of the current user.
- `create_tag` _(write)_ — Create a new tag.
- `update_tag` _(write)_ — Update tag attributes other than its name or label.
- `rename_tag` _(write)_ — Rename a tag and its display label.
- `delete_tag` _(destructive)_ — Delete a tag and remove its task associations.
- `list_calendar_accounts` _(read)_ — List third-party calendar accounts connected to TickTick.
- `query_calendar_events` _(read)_ — Query events from connected third-party calendars. Omit the query for the server's default range (now through the next three months); explicit ranges cannot…

---

## Connect

Gateway URL: https://gateway.mewcp.com/personal/mcp

Every request carries one header:

    Authorization: Bearer <API_KEY>

Replace `API_KEY` with your own key from the dashboard (Developer).

## Apps

### Claude Desktop

Mac & Windows app

- macOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
- Windows: `%APPDATA%\Claude\claude_desktop_config.json`

```json
{
  "mcpServers": {
    "mewcp": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://gateway.mewcp.com/personal/mcp",
        "--header",
        "Authorization:${AUTH_HEADER}"
      ],
      "env": {
        "AUTH_HEADER": "Bearer API_KEY"
      }
    }
  }
}
```

Already have an "mcpServers" section in your config? Just add the server entry inside it.

1. Open Claude Desktop → Settings → Developer → "Edit Config"
2. Paste the snippet inside the outer { } of the config file (merge with your existing "mcpServers" section if you have one)
3. Save the file, then quit Claude Desktop completely and reopen it
4. Start a new conversation — your tool will be available

### VS Code

Copilot / Cline

- Command Palette → "MCP: Open User Configuration" (opens mcp.json). For one project only, use .vscode/mcp.json instead.

```json
{
  "mcp.servers": {
    "mewcp": {
      "type": "http",
      "url": "https://gateway.mewcp.com/personal/mcp",
      "headers": {
        "Authorization": "Bearer API_KEY"
      }
    }
  }
}
```

Already have a "servers" section in your mcp.json? Just add the server entry inside it.

1. Open VS Code → Command Palette (Cmd+Shift+P / Ctrl+Shift+P)
2. Run "MCP: Open User Configuration" to open your mcp.json
3. Paste the snippet and save
4. Start the server when prompted (or from the MCP servers view) and use it in Copilot Chat

### Cursor

AI-first editor

- macOS: `~/.cursor/mcp.json`
- Windows: `%USERPROFILE%\.cursor\mcp.json`

```json
{
  "mcpServers": {
    "mewcp": {
      "url": "https://gateway.mewcp.com/personal/mcp",
      "headers": {
        "Authorization": "Bearer API_KEY"
      }
    }
  }
}
```

Already have an "mcpServers" section in your mcp.json? Just add the server entry inside it.

1. Open Cursor → Settings → Cursor Settings → MCP
2. Click "Add new global MCP server"
3. Paste the snippet and save
4. Restart Cursor

### Codex

OpenAI's CLI agent

- Add the snippet to your Codex MCP config or your standard MCP config file for the CLI tool you use.

```json
{
  "mcpServers": {
    "mewcp": {
      "type": "http",
      "url": "https://gateway.mewcp.com/personal/mcp",
      "headers": {
        "Authorization": "Bearer API_KEY"
      }
    }
  }
}
```

Codex generally reads a standard MCP server block, so you can add this alongside your other configured servers.

1. Open your Codex MCP config or project-level config file
2. Paste the MewCP server block inside the config JSON/TOML structure your tool expects
3. Save the file and restart Codex
4. Verify the tool is available inside a fresh session

### Claude Code

Anthropic's CLI agent

- ~/.claude.json (user scope) or .mcp.json in your project root — create it if it doesn't exist. Or skip the file and use the CLI command below.

```json
{
  "mcpServers": {
    "mewcp": {
      "type": "http",
      "url": "https://gateway.mewcp.com/personal/mcp",
      "headers": {
        "Authorization": "Bearer API_KEY"
      }
    }
  }
}
```

Already have an "mcpServers" section in your config? Just add the server entry inside it.

1. Open ~/.claude.json (or .mcp.json in your project root) in a text editor
2. Paste the snippet inside the outer { } (merge with your existing "mcpServers" section if you have one)
3. Save the file and start (or restart) Claude Code
4. Or skip the file entirely and run the CLI command below instead

### OpenCode

Open-source terminal agent

- ~/.config/opencode/opencode.json (global) or opencode.json in your project root — create it if it doesn't exist.

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mewcp": {
      "type": "remote",
      "url": "https://gateway.mewcp.com/personal/mcp",
      "enabled": true,
      "headers": {
        "Authorization": "Bearer API_KEY"
      }
    }
  }
}
```

Already have an "mcp" section in your opencode.json? Just add the server entry inside it.

1. Open ~/.config/opencode/opencode.json (or opencode.json in your project root) in a text editor
2. Paste the snippet inside the outer { } (merge with your existing "mcp" section if you have one)
3. Save the file and start (or restart) OpenCode

### OpenClaw

Self-hosted agent gateway

- ~/.openclaw/openclaw.json — create it if it doesn't exist.

```json
{
  "mcp": {
    "servers": {
      "mewcp": {
        "transport": "streamable-http",
        "url": "https://gateway.mewcp.com/personal/mcp",
        "enabled": true,
        "headers": {
          "Authorization": "Bearer API_KEY"
        }
      }
    }
  }
}
```

Already have an "mcp" section in your openclaw.json? Just add the server entry inside "servers".

1. Open ~/.openclaw/openclaw.json in a text editor
2. Paste the snippet inside the outer { } (merge with your existing "mcp" section if you have one)
3. Save the file and restart OpenClaw

### Antigravity

Google's agentic IDE

- ~/.gemini/config/mcp_config.json (global) or .agents/mcp_config.json (workspace-local) — create it if it doesn't exist.

```json
{
  "mcpServers": {
    "mewcp": {
      "serverUrl": "https://gateway.mewcp.com/personal/mcp",
      "headers": {
        "Authorization": "Bearer API_KEY"
      }
    }
  }
}
```

Already have an "mcpServers" section in your config? Just add the server entry inside it. Remote servers must use the "serverUrl" field — the legacy "url"/"httpUrl" fields aren't supported.

1. In the editor's agent side panel, click "…" → "MCP Servers" → "Manage MCP Servers" → "View raw config" (Antigravity CLI: type /mcp instead to open the Interactive MCP Manager)
2. Paste the snippet inside the outer { } (merge with your existing "mcpServers" section if you have one)
3. Save the file — the server connects automatically

### Hermes

Nous Research's CLI agent

- config.yaml in your Hermes config directory (~/.hermes) — add this under a top-level "mcp_servers:" key.

```yaml
mcp_servers:
  mewcp:
    url: "https://gateway.mewcp.com/personal/mcp"
    headers:
      Authorization: "Bearer API_KEY"
```

Already have an "mcp_servers" section in your config.yaml? Just add the server entry inside it.

1. Open config.yaml in your Hermes config directory
2. Paste the snippet under the top-level "mcp_servers:" key (merge with existing entries if you have any)
3. Save the file, then run /reload-mcp in Hermes (or start a fresh session)
4. Ask Hermes "Tell me which MCP-backed tools are available right now" to confirm it connected

### DeepSeek Harness

DeepSeek's agent harness

- cordis.yml in your DSH project — or the patch file you mount plugins from.

```yaml
- id: mcp-mewcp
  name: '@deepseek-ai/dsh-mcp-client'
  config:
    serverName: mewcp
    transport: streamable-http
    url: https://gateway.mewcp.com/personal/mcp
    headers:
      Authorization: "Bearer API_KEY"
```

One plugin instance = one MCP server. Add this entry to your plugin list; don't nest it inside another entry.

1. Open cordis.yml (or your patch file) in your DSH project
2. Paste the entry into your plugin list, keeping the leading dash and indentation
3. Restart DSH (or let HMR reload) — tools register as mcp__mewcp__<tool_name>
4. Verify with: dsh web --dump-config | grep -A3 mcp

## SDKs

### Python

fastmcp client

```python
import asyncio
from fastmcp import Client
from fastmcp.client.transports import StreamableHttpTransport

SERVER_URL = "https://gateway.mewcp.com/personal/mcp"
API_KEY = "API_KEY"

transport = StreamableHttpTransport(
    url=SERVER_URL,
    headers={
        "Authorization": f"Bearer {API_KEY}",
    }
)

async def main():
    client = Client(transport)
    async with client:
        tools = await client.list_tools()
        print(tools)

asyncio.run(main())
```

1. Install fastmcp: pip install fastmcp
2. Copy the snippet into your project
3. Replace API_KEY with your key from the dashboard
4. Run your script

### TypeScript

MCP SDK

```typescript
import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js";

const SERVER_URL = "https://gateway.mewcp.com/personal/mcp";
const API_KEY = "API_KEY";

const transport = new StreamableHTTPClientTransport(new URL(SERVER_URL), {
  requestInit: {
    headers: {
      Authorization: `Bearer ${API_KEY}`,
    },
  },
});

const client = new Client({ name: "mewcp-client", version: "1.0.0" });
await client.connect(transport);

const tools = await client.listTools();
console.log(tools.tools.map((t) => t.name));
```

1. Install: npm install @modelcontextprotocol/sdk
2. Copy the snippet into your project
3. Replace API_KEY with your key from the dashboard
4. Run with Node 18+ as an ES module (e.g. npx tsx script.ts)