TimeTree-MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TIMETREE_EMAIL | Yes | Your TimeTree account email address | |
| TIMETREE_PASSWORD | Yes | Your TimeTree account password | |
| TIMETREE_POSTER_WORKSPACE_ROOT | No | Path to poster workspace folder (default: ~/Desktop/timetree-posters) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_calendarsA | List configured TimeTree public calendars. Without args, returns the calendars set in TIMETREE_CALENDAR_ALIASES env var. Pass alias_codes to override (each code is the short ID in the URL https://timetr.ee/p/). Returns calendar id, alias_code, name, category, subscription count, and label palette. |
| list_eventsA | List events in a TimeTree public calendar within a date range. Pass alias_code (from list_calendars) and ISO date strings for from/to. Timezone defaults to Asia/Taipei. |
| create_eventA | Create an event in a TimeTree public calendar that the authenticated account manages. Use this after reading an event poster: pass alias_code (from list_calendars), title, ISO start date, optional location, and a short description (1-2 sentences). Timezone defaults to Asia/Taipei. Returns the created event with id and public URL. |
| update_eventA | Update an existing event in a TimeTree public calendar (full replace — PUT). Use this to add/replace/remove a cover image on an existing event, or change title/time/etc. Pass event_id (from list_events) plus all the fields you want the event to have. For cover: pass image_path to upload+set a new one, or remove_image=true to clear it; if neither is passed, cover is CLEARED (PUT is full-replace). To preserve the current cover while editing other fields, you must re-upload via image_path. |
| poster_workspace_statusA | Prepare and inspect the local poster workflow folder. Creates the standard folders if missing, moves loose image files from the root into 00_待處理 by default, and returns only pending poster image paths that should be read next. |
| mark_poster_processedA | Move one poster image out of 00_待處理 after processing and append the CSV log. Normally create_event/update_event do this automatically when image_path is inside 00_待處理. Use this for manual corrections or posters that need review. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool has a clear, distinct purpose: calendar listing, event listing, event creation, event updating, poster workspace inspection, and poster processed marking. No two tools overlap in function, and the descriptions reinforce the boundaries.
Most tools follow a consistent verb_noun pattern (list_calendars, list_events, create_event, update_event, mark_poster_processed). The exception is poster_workspace_status, which uses a noun_noun structure, but it is still understandable and does not create confusion.
Six tools is well-scoped for the server's dual purpose of TimeTree calendar management and local poster workflow. Each tool earns its place without redundancy or unnecessary bloat.
The server covers the core lifecycle of events (list, create, update) and the poster workflow (status, mark processed, integrated image upload). Minor gaps include no delete_event or get_single_event, but these can be worked around with list_events and update_event, so the coverage is adequate for typical use.