
ticktick-mcp-server
A MCP server for TickTick that enables interacting with your TickTick task management system directly through Claude and other MCP clients.
jacepark12
README
TickTick MCP Server
A Model Context Protocol (MCP) server for TickTick that enables interacting with your TickTick task management system directly through Claude and other MCP clients.
Features
- 📋 View all your TickTick projects and tasks
- ✏️ Create new projects and tasks through natural language
- 🔄 Update existing task details (title, content, dates, priority)
- ✅ Mark tasks as complete
- 🗑️ Delete tasks and projects
- 🔄 Full integration with TickTick's open API
- 🔌 Seamless integration with Claude and other MCP clients
Prerequisites
- Python 3.10 or higher
- uv - Fast Python package installer and resolver
- TickTick account with API access
- TickTick API credentials (Client ID, Client Secret, Access Token)
Installation
-
Clone this repository:
git clone https://github.com/parkjs814/ticktick-mcp.git cd ticktick-mcp
-
Install with uv:
# Install uv if you don't have it already curl -LsSf https://astral.sh/uv/install.sh | sh # Create a virtual environment uv venv # Activate the virtual environment # On macOS/Linux: source .venv/bin/activate # On Windows: .venv\Scripts\activate # Install the package uv pip install -e .
-
Authenticate with TickTick:
# Run the authentication flow uv run -m ticktick_mcp.cli auth
This will:
- Ask for your TickTick Client ID and Client Secret
- Open a browser window for you to log in to TickTick
- Automatically save your access tokens to a
.env
file
-
Test your configuration:
uv run test_server.py
This will verify that your TickTick credentials are working correctly.
Authentication with TickTick
This server uses OAuth2 to authenticate with TickTick. The setup process is straightforward:
-
Register your application at the TickTick Developer Center
- Set the redirect URI to
http://localhost:8000/callback
- Note your Client ID and Client Secret
- Set the redirect URI to
-
Run the authentication command:
uv run -m ticktick_mcp.cli auth
-
Follow the prompts to enter your Client ID and Client Secret
-
A browser window will open for you to authorize the application with your TickTick account
-
After authorizing, you'll be redirected back to the application, and your access tokens will be automatically saved to the
.env
file
The server handles token refresh automatically, so you won't need to reauthenticate unless you revoke access or delete your .env
file.
Usage with Claude for Desktop
-
Install Claude for Desktop
-
Edit your Claude for Desktop configuration file:
macOS:
nano ~/Library/Application\ Support/Claude/claude_desktop_config.json
Windows:
notepad %APPDATA%\Claude\claude_desktop_config.json
-
Add the TickTick MCP server configuration, using absolute paths:
{ "mcpServers": { "ticktick": { "command": "<absolute path to uv>", "args": ["run", "--directory", "<absolute path to ticktick-mcp directory>", "-m", "ticktick_mcp.cli", "run"] } } }
-
Restart Claude for Desktop
Once connected, you'll see the TickTick MCP server tools available in Claude, indicated by the 🔨 (tools) icon.
Available MCP Tools
Tool | Description | Parameters |
---|---|---|
get_projects |
List all your TickTick projects | None |
get_project |
Get details about a specific project | project_id |
get_project_tasks |
List all tasks in a project | project_id |
get_task |
Get details about a specific task | project_id , task_id |
create_task |
Create a new task | title , project_id , content (optional), start_date (optional), due_date (optional), priority (optional) |
update_task |
Update an existing task | task_id , project_id , title (optional), content (optional), start_date (optional), due_date (optional), priority (optional) |
complete_task |
Mark a task as complete | project_id , task_id |
delete_task |
Delete a task | project_id , task_id |
create_project |
Create a new project | name , color (optional), view_mode (optional) |
delete_project |
Delete a project | project_id |
Example Prompts for Claude
Here are some example prompts to use with Claude after connecting the TickTick MCP server:
- "Show me all my TickTick projects"
- "Create a new task called 'Finish MCP server documentation' in my work project with high priority"
- "List all tasks in my personal project"
- "Mark the task 'Buy groceries' as complete"
- "Create a new project called 'Vacation Planning' with a blue color"
- "When is my next deadline in TickTick?"
Development
Project Structure
ticktick-mcp/
├── .env.template # Template for environment variables
├── README.md # Project documentation
├── requirements.txt # Project dependencies
├── setup.py # Package setup file
├── test_server.py # Test script for server configuration
└── ticktick_mcp/ # Main package
├── __init__.py # Package initialization
├── authenticate.py # OAuth authentication utility
├── cli.py # Command-line interface
└── src/ # Source code
├── __init__.py # Module initialization
├── auth.py # OAuth authentication implementation
├── server.py # MCP server implementation
└── ticktick_client.py # TickTick API client
Authentication Flow
The project implements a complete OAuth 2.0 flow for TickTick:
- Initial Setup: User provides their TickTick API Client ID and Secret
- Browser Authorization: User is redirected to TickTick to grant access
- Token Reception: A local server receives the OAuth callback with the authorization code
- Token Exchange: The code is exchanged for access and refresh tokens
- Token Storage: Tokens are securely stored in the local
.env
file - Token Refresh: The client automatically refreshes the access token when it expires
This simplifies the user experience by handling the entire OAuth flow programmatically.
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
- Fork the repository
- Create your feature branch (
git checkout -b feature/amazing-feature
) - Commit your changes (
git commit -m 'Add some amazing feature'
) - Push to the branch (
git push origin feature/amazing-feature
) - Open a Pull Request
License
This project is licensed under the MIT License - see the LICENSE file for details.
Recommended Servers
Apple MCP Server
Enables interaction with Apple apps like Messages, Notes, and Contacts through the MCP protocol to send messages, search, and open app content using natural language.

google-calendar-mcp
Lets LLMs read and manage Google Calendar events.
Todoist MCP
An MCP server that enables LLMs to interact with Todoist tasks, projects, and other features through the Todoist API.

Notion API MCP Server
Enables advanced todo list management and content organization using Notion's API, supporting features like creating databases, dynamic filtering, and collaborative task tracking.
Todoist MCP Server
Integrates Claude with Todoist for natural language task management, supporting project and section organization, task creation, updating, completion, and deletion using everyday language.
Todoist MCP Server
An MCP server that integrates Claude with Todoist, enabling natural language task management including creating, updating, completing, and deleting tasks.
Curri MCP Server
Enables interaction with Curri's API by managing text notes, offering tools for note creation, and generating summaries using structured prompts.
Inkdrop MCP Server
Integrates Inkdrop note-taking app with Claude AI through Model Context Protocol, allowing Claude to search, read, create, and update notes in your Inkdrop database.
Notion MCP Server
Enables interaction with Notion through the Notion API by exposing it as tools for LLMs, allowing operations like reading, creating, updating, and deleting Notion pages seamlessly via natural language.
Notion MCP Server
A Model Context Protocol server that connects Claude and other AI assistants to your Notion workspace, allowing AIs to interact with databases, pages, and blocks.