@ticktick-ecosystem/mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TICKTICK_CLIENT_ID | No | Your TickTick API client ID. Required for production mode. | |
| TICKTICK_DEMO_MODE | No | Set to 'true' to run in demo mode (no authentication required). | |
| TICKTICK_ACCESS_TOKEN | No | OAuth access token (optional, will be obtained via OAuth if not provided). | |
| TICKTICK_REDIRECT_URI | No | OAuth redirect URI. Defaults to http://localhost:3000/callback. | |
| TICKTICK_CLIENT_SECRET | No | Your TickTick API client secret. Required for production mode. | |
| TICKTICK_REFRESH_TOKEN | No | OAuth refresh token (optional). |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/marketing-shibata50/ticktick-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server