Timeline MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POSTY_WORKSPACE | Yes | Path to your Posty workspace directory containing the SQLite database |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| timeline_add_scheduled_eventA | Add a scheduled event to a track. IMPORTANT: 1) Use the terminal MCP tool to get the current date/time (execute_command("date")) before scheduling events to ensure correct dates. 2) ALWAYS use timeline_list_tracks first to check existing tracks - if a track with a similar name or purpose already exists, use that instead of creating a new one. If unsure whether an existing track matches your needs, ask the user for clarification before proceeding. |
| timeline_list_tracksC | List all tracks |
| timeline_add_trackA | Create a new track for organizing timeline events. Check existing tracks with timeline_list_tracks first to avoid duplicates. |
| timeline_list_scheduled_eventsA | List scheduled events with optional filtering by track, status, platform, and date range. STATUS FILTERING:
DATE FILTERING:
EXAMPLES:
|
| timeline_update_scheduled_eventC | Update an existing scheduled event |
| timeline_remove_scheduled_eventC | Remove a scheduled event |
| timeline_remove_trackA | Remove a track and all its associated events. WARNING: This will delete all events in the track. |
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 7 tools
Each tool has a clearly distinct purpose: timeline_add_scheduled_event and timeline_update_scheduled_event handle event creation/modification, timeline_remove_scheduled_event handles deletion, timeline_list_scheduled_events handles listing with filtering, timeline_add_track and timeline_remove_track manage tracks, and timeline_list_tracks lists tracks. There is no overlap or ambiguity between tools.
All tools follow a consistent 'timeline_verb_noun' pattern with snake_case, such as timeline_add_scheduled_event, timeline_list_tracks, and timeline_remove_track. This predictable naming convention makes it easy to understand each tool's function at a glance.
With 7 tools, this server is well-scoped for managing timeline tracks and scheduled events. It provides a complete set of operations (add, list, update, remove for both tracks and events) without being overly complex or too sparse, fitting typical use cases effectively.
The toolset offers full CRUD coverage for both tracks (add, list, remove) and scheduled events (add, list, update, remove), including advanced filtering for events. There are no obvious gaps; agents can manage the entire lifecycle of timeline data without dead ends.