mcp-ical
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| create_eventC | Generate an RFC 5545 ICS file for a single calendar event. |
| create_calendarB | Build a multi-event ICS calendar file from an array of events. |
| parse_icsB | Parse an ICS file content and return an array of event objects. |
| google_calendar_urlA | Build a one-click 'Add to Google Calendar' URL for an event (no auth needed). |
| outlook_calendar_urlC | Build a one-click 'Add to Outlook Web Calendar' URL. |
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 5 tools
Each tool targets a distinct function: multi-event calendar creation, single event creation, Google Calendar URL, Outlook URL, and ICS parsing. No overlap.
All tool names use consistent snake_case with a clear verb_noun pattern (create_calendar, create_event, google_calendar_url, outlook_calendar_url, parse_ics).
5 tools is well-scoped for a calendar utility server covering creation, URL generation, and parsing. Not excessive or sparse.
The set covers all common needs: single/multi-event creation, popular calendar URL generation, and ICS parsing. No obvious gaps for the stated purpose.