Itinerary Travel Plan Schedule Events is answering right now. Last checked 13 min ago. It exposes 12 tools. Last commit 22 Oct 2026.
Trip itinerary planner: events, free-busy, double bookings, schedule export.
Uptime history
32 days of history · worst day 92%
32 days agonow
100.0%
Uptime 24h
88 of 88 checks
12
Tools
read from the server
237 ms
Response time
average over 24h
2
Stars
last commit 22 Oct 2026
What changed 1
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 15 October 2026. No other catalogue keeps this.
15 Oct
a tool changed version
Nothing serious here today
Today is the operative word: we check Itinerary Travel Plan Schedule Events every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.
run in your terminal
claude mcp add itinerary-travel-plan-schedule-events --transport http https://mcp.zovo.one/mcp/itinerary-travel-plan-schedule-eventsSettings → Connectors → Add custom connector, then paste this address
https://mcp.zovo.one/mcp/itinerary-travel-plan-schedule-events~/.codex/config.toml
[mcp_servers.itinerary-travel-plan-schedule-events]
url = "https://mcp.zovo.one/mcp/itinerary-travel-plan-schedule-events".cursor/mcp.json
{
"mcpServers": {
"itinerary-travel-plan-schedule-events": {
"url": "https://mcp.zovo.one/mcp/itinerary-travel-plan-schedule-events"
}
}
}.vscode/mcp.json
{
"servers": {
"itinerary-travel-plan-schedule-events": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/itinerary-travel-plan-schedule-events"
}
}
}Available tools 12
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
event
event_export
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.
event_to_time_entry
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.
events
events_list
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.
events_search
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.
ics
ics_forget
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.
ics_import
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.
license
license_activate
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.
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.
calendars
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.
conflicts
conflicts
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.
free
free_busy
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.
next
next_event
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.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://mcp.zovo.one/mcp/itinerary-travel-plan-schedule-events | streamable-http | answering | 103 ms | 13 min ago |
Alternatives to Itinerary Travel Plan Schedule Events
same job, measured the same wayCalendar Ics Reader Events Freebusy Conflicts
by theluckystrike
Read the .ics your calendar exports: events in a window, free-busy, double bookings, export.
Availability
by theluckystrike
Read .ics calendar exports: free-busy, availability windows, double bookings, conflicts.
Slotlock
by pilotaai
Calendars for AI agents: free/busy, next free slot, and bookings PostgreSQL never double-books.
Travel Facts
by nomadpoint
No-auth: save a planned trip as a claimable itinerary, visa rules per passport, Schengen 90/180
Tripsy
by tripsyapp
Plan trips and manage itineraries, stays, transport, activities, expenses, and documents in Tripsy.
Calcom MCP
by mrfentmen
Query Cal.com API v2: event types, bookings, schedules. v1 is decommissioned.
Zwier (Group event planner)
by zwier
Plan group events together: dates, itineraries, expenses, polls, and tasks.
Calendar MCP
by deciduus
Google Calendar for LLM agents: find, create, update, move, delete events; free/busy; scheduling.
Itinerary Travel Plan Schedule Events — questions
Answers built from our own checks of this server.
What can Itinerary Travel Plan Schedule Events do?
It exposes 12 tools, read directly from the server on our last check. Among them: calendars_list, conflicts, event_export, events_list, events_search, event_to_time_entry and 6 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is Itinerary Travel Plan Schedule Events mostly used for?
Its tools cluster around event, events and ics. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Itinerary Travel Plan Schedule Events working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 88 of 88 checks got a reply (100.0%), average response time 237 ms. The bar chart above shows every period we have measured.
How do I connect Itinerary Travel Plan Schedule Events?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Itinerary Travel Plan Schedule Events need an API key?
No. Itinerary Travel Plan Schedule Events completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 12 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Itinerary Travel Plan Schedule Events?
It answers our handshake in 237 ms on average, which is faster than 63% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Itinerary Travel Plan Schedule Events open source?
The code is open source: it is published under the MIT licence, written in JavaScript and 2 stars on GitHub. The licence covers the code in the repository, not the hosted service at mcp.zovo.one, which runs on its operator's own terms.