Chronos MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CALDAV_BASE_URL | Yes | Base URL of the CalDAV server (e.g., http://localhost:5232) | |
| CALDAV_PASSWORD | Yes | Password for CalDAV authentication | |
| CALDAV_USERNAME | Yes | Username for CalDAV authentication |
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 | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_accountA | Add a new CalDAV account to Chronos By default, this function blocks URLs pointing to localhost and private IP addresses for security (SSRF protection). For local development or testing, set allow_local=True to explicitly allow these addresses. |
| list_accountsA | List all configured CalDAV accounts |
| remove_accountC | Remove a CalDAV account from Chronos |
| test_accountA | Test connectivity to a CalDAV account |
| list_calendarsC | List all calendars for an account |
| create_calendarC | Create a new calendar |
| delete_calendarC | Delete a calendar |
| create_eventB | Create a new calendar event |
| get_events_rangeC | Get events within a date range |
| delete_eventC | Delete a calendar event |
| update_eventA | Update an existing calendar event. Only provided fields will be updated. |
| create_recurring_eventC | Create a recurring event with validation. |
| search_eventsB | Search for events across calendars with advanced filtering |
| create_taskC | Create a new task |
| list_tasksC | List tasks in a calendar |
| update_taskA | Update an existing task. Only provided fields will be updated. |
| delete_taskC | Delete a task |
| create_journalC | Create a new journal entry |
| list_journalsB | List journal entries in a calendar |
| update_journalB | Update an existing journal entry. Only provided fields will be updated. |
| delete_journalB | Delete a journal entry |
| bulk_create_eventsB | Create multiple events in bulk |
| bulk_delete_eventsC | Delete multiple events in bulk |
| bulk_create_tasksB | Create multiple tasks in bulk |
| bulk_delete_tasksB | Delete multiple tasks in bulk |
| bulk_create_journalsC | Create multiple journal entries in bulk |
| bulk_delete_journalsB | Delete multiple journal entries in bulk |
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 27 tools
Each tool targets a distinct resource (account, calendar, event, journal, task) and action (create, update, delete, list, etc.). No two tools have overlapping purposes, and descriptions clearly differentiate them.
All tool names follow a consistent verb_noun pattern (e.g., add_account, create_calendar, update_event). Bulk operations use prefix 'bulk_' uniformly. No mixing of conventions.
27 tools cover accounts, calendars, and CRUD for three resource types (events, journals, tasks) plus bulk operations and search. While slightly high, each tool serves a specific need and the count is justified by the domain scope.
The tool surface includes account management, calendar CRUD, and full CRUD plus extras (recurring events, search, bulk ops) for events, journals, and tasks. Missing calendar updates and some advanced features, but core workflows are well covered.