TickTick MCP Server (Vercel)
A Model Context Protocol server for TickTick, deployed on Vercel.
Deploy to Vercel
1. Environment Variables
Set these in Vercel Dashboard > Settings > Environment Variables:
| Variable | Description |
|---|---|
TICKTICK_ACCESS_TOKEN | Your TickTick API access token |
REDIS_URL | Redis connection URL (for SSE transport) |
2. Add Redis (for SSE support)
- Go to Vercel Dashboard > Storage
- Add Upstash Redis
- The
REDIS_URLwill be automatically configured
3. Deploy
vercel --prod
Connect from Claude
Option 1: Claude Pro/Max/Team/Enterprise
- Open Claude Desktop or claude.ai
- Go to Settings > Connectors
- Add new connector with URL:
https://your-app.vercel.app/api/mcp
Option 2: Using mcp-remote (Free users)
Edit ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"ticktick": {
"command": "npx",
"args": [
"mcp-remote",
"https://your-app.vercel.app/api/sse"
]
}
}
}
Available Tools
| Tool | Description |
|---|---|
list_projects | List all TickTick projects |
get_tasks | Get tasks (all or by project) |
create_task | Create a new task |
update_task | Update an existing task |
complete_task | Mark task as completed |
delete_task | Delete a task |
Local Development
# Install dependencies
npm install
# Set environment variables
export TICKTICK_ACCESS_TOKEN="your-token"
export REDIS_URL="your-redis-url" # Optional for local
# Run development server
npm run dev
Test with MCP Inspector:
npx @anthropic-ai/mcp-inspector
Endpoints
/api/mcp- Streamable HTTP transport (recommended)/api/sse- Server-Sent Events transport
