itinerary-travel-plan-schedule-events

Trip itinerary planner: events, free-busy, double bookings, schedule export.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
87%
Naming quality
82%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~2,235Tokens (tool definitions)
~1.2 KBTypical response size
Moderate attention impact (1.75% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "itinerary-travel-plan-schedule-events": {
      "command": "uvx",
      "args": [
        "https://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/calendar.mcpb"
      ]
    }
  }
}

Runnable packages

mcpbhttps://github.com/theluckystrike/mcp-servers/releases/download/v0.22.0/calendar.mcpb0.22.0stdio

Remote endpoints

https://mcp.zovo.one/mcp/itinerary-travel-plan-schedule-eventsstreamable-http

What it can do

Tool inventory

Tools (12)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢license_status

Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.

Input Schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
license_activate(key)

Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.

Input Schema

{
  "type": "object",
  "properties": {
    "key": {
      "type": "string",
      "description": "License key from checkout, MCPL1.<payload>.<signature>"
    }
  },
  "required": [
    "key"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢ics_import(path, url, text, name)

Call this tool to read a calendar export and keep it under a name. Give path (.ics file), text (contents), or url (public .ics/webcal feed; Pro). Google, Apple, Outlook exports read. Re-importing a name replaces it.

Input Schema

{
  "type": "object",
  "properties": {
    "path": {
      "type": "string",
      "maxLength": 4096,
      "description": "Not available on this hosted endpoint, which has no filesystem: paste the file as text instead"
    },
    "url": {
      "type": "string",
      "maxLength": 4096,
      "description": "Public https:// or webcal:// .ics feed. Fetched once, only because you asked; Pro feature"
    },
    "text": {
      "type": "string",
      "maxLength": 5242880,
      "description": "The .ics file contents, pasted"
    },
    "name": {
      "type": "string",
      "maxLength": 80,
      "description": "What to call this calendar, e.g. \"work\" or \"family\""
    }
  },
  "required": [
    "name"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢calendars_list

List imported calendars: name, event-definition count, size, source, import time and free-tier use of the 2 slots. It also names stored .ics files with no calendar row. With none it prints the export steps.

Input Schema

{
  "type": "object",
  "properties": {},
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢events_list(calendar, from, to, zone)

Every event between two dates, recurring expanded to occurrences, sorted by start. Times shown in your zone (profile's, else this machine's) unless zone passed. Each id works for event_export or event_to_time_entry.

Input Schema

{
  "type": "object",
  "properties": {
    "calendar": {
      "type": "string",
      "maxLength": 80,
      "description": "One calendar name; default every imported calendar"
    },
    "from": {
      "type": "string",
      "maxLength": 20,
      "description": "First day, YYYY-MM-DD"
    },
    "to": {
      "type": "string",
      "maxLength": 20,
      "description": "Last day, YYYY-MM-DD, included"
    },
    "zone": {
      "type": "string",
      "maxLength": 100,
      "description": "Show local times in this zone or city instead of your own"
    }
  },
  "required": [
    "from",
    "to"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢events_search(query, from, to)

Find events whose title, description, location or attendees contain a phrase. Searches every imported calendar. Without from/to it looks a year back and a year forward on Pro, and the free window either side of today.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string",
      "maxLength": 200,
      "description": "Words to look for, case-insensitive"
    },
    "from": {
      "type": "string",
      "maxLength": 20,
      "description": "First day, YYYY-MM-DD"
    },
    "to": {
      "type": "string",
      "maxLength": 20,
      "description": "Last day, YYYY-MM-DD, included"
    }
  },
  "required": [
    "query"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
free_busy(calendars, from, to, work_start, work_end, ...)

Merged busy blocks and the free gaps inside your working hours over a day range. Events marked free do not count; whole-day events block the day. Free: 31 days. Use conflicts for overlapping pairs.

Input Schema

{
  "type": "object",
  "properties": {
    "calendars": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 80
      },
      "maxItems": 20,
      "description": "Calendar names; default all of them"
    },
    "from": {
      "type": "string",
      "maxLength": 20,
      "description": "First day, YYYY-MM-DD"
    },
    "to": {
      "type": "string",
      "maxLength": 20,
      "description": "Last day, YYYY-MM-DD, included"
    },
    "work_start": {
      "type": "string",
      "maxLength": 10,
      "description": "Start of your working day, HH:MM, default 09:00"
    },
    "work_end": {
      "type": "string",
      "maxLength": 10,
      "description": "End of your working day, HH:MM, default 17:00"
    },
    "zone": {
      "type": "string",
      "maxLength": 100,
      "description": "Zone the working hours and the output are in; default your own"
    }
  },
  "required": [
    "from",
    "to"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢conflicts(calendar, from, to)

Find double bookings: every PAIR of timed events that overlap, with the minutes they collide, across all calendars unless you name one. Whole-day events are reported apart. Free: 31 days. free_busy shows gaps.

Input Schema

{
  "type": "object",
  "properties": {
    "calendar": {
      "type": "string",
      "maxLength": 80,
      "description": "One calendar name; default every imported calendar"
    },
    "from": {
      "type": "string",
      "maxLength": 20,
      "description": "First day, YYYY-MM-DD"
    },
    "to": {
      "type": "string",
      "maxLength": 20,
      "description": "Last day, YYYY-MM-DD, included"
    }
  },
  "required": [
    "from",
    "to"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
next_event(calendar)

The first event not yet started, within the next 366 days, across every imported calendar or one you name. Returns title, times in your zone, how long until it starts, location, attendees and its id.

Input Schema

{
  "type": "object",
  "properties": {
    "calendar": {
      "type": "string",
      "maxLength": 80,
      "description": "One calendar name; default every imported calendar"
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢event_export(ids, from, to, calendar, out_path)

Call this tool to write chosen events to a new .ics file you can send or import elsewhere. Pass either ids (from events_list) or a from/to window. Times are written in UTC so the file lands correctly in any client.

Input Schema

{
  "type": "object",
  "properties": {
    "ids": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 200
      },
      "maxItems": 500,
      "description": "Event ids from events_list, events_search or next_event"
    },
    "from": {
      "type": "string",
      "maxLength": 20,
      "description": "First day, YYYY-MM-DD (alternative to ids)"
    },
    "to": {
      "type": "string",
      "maxLength": 20,
      "description": "Last day, YYYY-MM-DD, included"
    },
    "calendar": {
      "type": "string",
      "maxLength": 80,
      "description": "With from/to: limit to one calendar"
    },
    "out_path": {
      "type": "string",
      "maxLength": 4096,
      "description": "Name for the downloaded .ics file, e.g. week.ics"
    }
  },
  "required": [
    "out_path"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
event_to_time_entry(event_id, project, rate, currency)

Take one event and return the exact arguments for the time-tracker's entry_add, so a meeting that already happened becomes billable time without retyping it. Writes nothing: pass the JSON straight to entry_add.

Input Schema

{
  "type": "object",
  "properties": {
    "event_id": {
      "type": "string",
      "maxLength": 200,
      "description": "Event id from events_list, events_search or next_event"
    },
    "project": {
      "type": "string",
      "maxLength": 80,
      "description": "Project or client the meeting is billed to"
    },
    "rate": {
      "anyOf": [
        {
          "type": "number",
          "minimum": 0
        },
        {
          "type": "string",
          "maxLength": 60
        }
      ],
      "description": "Hourly rate for this entry; a number (120) or the words the user said ('120 euros an hour')"
    },
    "currency": {
      "type": "string",
      "maxLength": 20,
      "description": "Currency of the rate: EUR, USD, GBP, PLN, or the word the user said ('euros'). Without it the time-tracker falls back to USD."
    }
  },
  "required": [
    "event_id",
    "project"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🔴ics_forget(name)

Remove one imported calendar by name and delete this server's local copy of its .ics, freeing a slot. Your own calendar and the source file are untouched. ics_import replaces a name in place.

Input Schema

{
  "type": "object",
  "properties": {
    "name": {
      "type": "string",
      "maxLength": 80,
      "description": "The calendar name from calendars_list"
    }
  },
  "required": [
    "name"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded12 tools