Mu
News, web search, mail, markets, weather, places, files, calendar, contacts. 67 tools, one endpoint.
Trip itinerary planner: events, free-busy, double bookings, schedule export.
Texto original del autor
Las listas se ordenan por una puntuación de uso (sobre 100) con estas partes
| Popularidad | 0/80 | Estrellas de GitHub o descargas semanales: la mayor cuenta 60, la menor 20 |
|---|---|---|
| Actualidad | 12/12 | Puntuación completa con una versión o cambio de código en 30 días |
| Sigue respondiendo | 0/8 | El endpoint en la nube respondió en la última revisión |
| Puntuación de uso | 12/100 |
Calidad: Pasó 3/3 revisiones básicas (se muestra, no ordena) · Impulso: Sin datos aún (Solo se usa en la pestaña En auge)
Elige la app de IA que usas y copia la configuración.
Pasó 3/3 revisiones · Funciona en tu computadora
Primero: ¿qué IA usas?
Elige tu app y los pasos aparecen abajo.
Funciona con Claude, pero hay que preparar algo antes
Sin clave y sin instalar nada · Solo en la app de Claude para computadora (Windows o Mac), no en la web ni en el móvil
Descargar el archivo .mcpb del creador
El archivo .mcpb viene directo del autor; no lo modificamos
Usa Itinerary Travel Plan Schedule Events y dime qué puedes hacer por mí; luego muéstrame una cosa✓ Si Claude dice que está usando Itinerary Travel Plan Schedule Events o muestra una herramienta de Itinerary Travel Plan Schedule Events en la respuesta, ya está conectado
Nombres de menú comprobados con la ayuda de Anthropic el 11 nov 2026 · tu pantalla puede variar un poco según la versión
ChatGPT todavía no puede conectar Itinerary Travel Plan Schedule Events
Itinerary Travel Plan Schedule Events se instala en tu computadora, pero ChatGPT solo conecta servidores que funcionan en la web
A · Usa una app que pueda conectar Itinerary Travel Plan Schedule Events
B · Otros en Viajes, mapas y clima que funcionan con ChatGPT
Elegidos entre los más usados de la misma categoría, solo los que se conectan con una dirección y sin clave
Claude Code todavía no puede conectar Itinerary Travel Plan Schedule Events
El autor solo ofrece un instalador para la app de Claude de escritorio
A · Usa una app que pueda conectar Itinerary Travel Plan Schedule Events
Cursor todavía no puede conectar Itinerary Travel Plan Schedule Events
El autor solo ofrece un instalador para la app de Claude de escritorio
A · Usa una app que pueda conectar Itinerary Travel Plan Schedule Events
VS Code todavía no puede conectar Itinerary Travel Plan Schedule Events
El autor solo ofrece un instalador para la app de Claude de escritorio
A · Usa una app que pueda conectar Itinerary Travel Plan Schedule Events
Otras apps que usan MCP, como Windsurf, Zed o Gemini CLI, añaden servidores de forma distinta. Míralo en la lista de apps
Ver todas las apps que usan MCP →
La configuración JSON está en “Para desarrolladores”, abajo
MCP_LICENSE_KEY secreto envDescripciones traducidas automáticamente; los nombres de variables quedan como en el original. Si dudas, mira el original.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
mcpb: …/calendar.mcpbSegún cómo se conecta este servidor y la documentación de cada app, comprobado el 10 nov 2026.
Se ejecutan en tu computadora en
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 20 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub theluckystrike, dueña del repo
Último cambio de código: anteayer
Usa MIT
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
No revisado: solo se pueden revisar paquetes npm y PyPI con versión
Si lo creaste tú, pega este código en tu README. La insignia enlaza a esta página.
[](https://mcp.popnx.com/en/servers/theluckystrike-itinerary-travel-plan-schedule-events)Pregunta, comparte un consejo o avisa de que no funciona. Ordenado por lo que la gente marcó como útil.
Aún no hay publicaciones. Sé la primera persona en preguntar o compartir.
Lo publicado aquí lo escriben usuarios, no el equipo de PopNx.
Aún no hay reseñas
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 3 de 3 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez anteayer, y la última versión (0.22.6) llegó al registro hace 37 días.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas MCPB en tu computadora.
En la misma categoría: Mu, Award Travel Finder, Killbottleneck, Gondola Award Travel Search, Whimsical
Misma categoría, otros creadores, comandos ya revisados. Primero los oficiales, luego por estrellas.
Cómo leer una tarjeta:↓ Descargas por semanai★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
News, web search, mail, markets, weather, places, files, calendar, contacts. 67 tools, one endpoint.
Search award flight availability and points pricing across 27 airlines and 23 loyalty programs.
Free-to-self-host goal and process maps for humans and AI agents, with REST API and MCP.
Compare cash vs points on hotels, flights, and cars. Checkout supported hotels and rental cars.
Create and edit flowcharts, mind maps, wireframes, and docs in Whimsical, or search your workspace.
| Este Itinerary Travel Plan Schedule Events | Mu | Award Travel Finder | Killbottleneck | Gondola Award Travel Search | Whimsical | |
|---|---|---|---|---|---|---|
| Dónde se ejecuta | Se instala en tu equipo | Funciona en la nube, sin instalar nada | Funciona en la nube, sin instalar nada | Se instala en tu equipo | Funciona en la nube, sin instalar nada | Funciona en la nube, sin instalar nada |
| Necesita clave | No | No | No | Sí | No | No |
| Se añade con + en Claude | No | No | No | No | No | Sí |
| Revisiones básicas | 3/3 | 4/4 | 3/3 | 3/3 | 4/4 | 4/4 |
| Licencia | MIT | AGPL-3.0 | MIT | MIT | MIT | MIT |
| Precio | Sin coste en el registro | Sin coste en el registro | Sin coste en el registro | Sin coste en el registro | Sin coste en el registro | Sin coste en el registro |
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
Your calendar app can show you next Tuesday. It cannot tell you where your week actually went, which two things you said yes to at the same time, or how many billable hours last month's meetings were worth. This server reads the .ics file your calendar already exports and answers those questions: events in any window with recurring series expanded properly, merged busy blocks and the real free gaps inside your working hours, every double booking across work and personal calendars at once, a clean .ics of just the events you picked, and the exact time entry for a meeting you should have billed. No account is connected, nothing is synced, and the calendar file stays on your machine as plain text.
Built by theluckystrike.
In the [official MCP Registry](https://registry.modelcontextprotocol.io/v0.1/servers/io.github.theluckystrike%2Fcalendar-ics-reader-events-freebusy-conflicts/versions/latest) (io.github.theluckystrike/calendar-ics-reader-events-freebusy-conflicts).
Listed on the [AI Product Index](https://index.percall.dev/l/zovo-calendar.html) - live remote endpoint at mcp.zovo.one/s/calendar, free tier, no signup.
Import the .ics your calendar exports, then ask what is on, when you are free, and what clashes, zero setup, all local.
npm publish for @theluckystrike/mcp-calendar is pending. Until then, the .mcpb one-click bundle or a clone+build is the working path, both are verified below.
One-click (.mcpb): download calendar.mcpb from the latest release and double-click it in Claude Desktop: https://github.com/theluckystrike/mcp-servers/releases/latest
(claude_desktop_config.json):
{
"mcpServers": { "calendar": { "command": "npx", "args": ["-y", "@theluckystrike/mcp-calendar"] } } }
Claude Code:
claude mcp add calendar -- npx -y @theluckystrike/mcp-calendar
(.cursor/mcp.json):
{
"mcpServers": { "calendar": { "command": "npx", "args": ["-y", "@theluckystrike/mcp-calendar"] } } }
The npx form above starts working the moment the package is published. Until then, use the .mcpb bundle above, or build from source with exactly these four commands:
git clone https://github.com/theluckystrike/mcp-servers.git && cd mcp-servers
npm install npm run build -w packages/mcp-license -w servers/timezone -w servers/calendar
Then point your client's command at node with one arg: the absolute path to servers/calendar/dist/index.js.
To run in Pro mode set MCP_LICENSE_KEY in the same config block, or call license_activate once with your key.
| App | Where |
|---|---|
| Google Calendar | Settings -> Import & export -> Export. You get a zip; import the .ics inside it. |
| Apple Calendar | File -> Export -> Export... |
| Outlook (desktop) | File -> Save Calendar, format iCalendar (.ics) |
| Outlook / Microsoft 365 (web) | Settings -> Calendar -> Shared calendars -> Publish, then use the ICS link (Pro) |
| Anything else | Any published feed URL ending in .ics, or webcal:// (Pro) |
Then: ics_import {path: "~/Downloads/mike@example.com.ics", name: "work"}
| Tool | What it does |
|---|---|
ics_import | Read a .ics file (path), pasted contents (text) or a public feed (url, Pro) and keep it locally under a name. Importing the same name again replaces it. |
calendars_list | Every imported calendar: name, source, event count, size, when it was imported. |
events_list | Every event between two dates with recurring series expanded to real occurrences, sorted, in your own time zone. Each row carries an id. |
events_search | Events whose title, description, location, organizer or attendees contain a phrase. |
free_busy | Merged busy blocks and the free gaps inside your working hours, day by day. Events marked free/transparent do not count as busy. |
conflicts | Every pair of events that overlap, with the overlap in minutes -- across all calendars, so a client call clashing with a school run is caught. A longer window is shortened to the free 31 days and answered, never refused. |
next_event | The next thing that has not started, and how long until it does. |
event_export | Write chosen events (by id, or a whole window) to a new .ics you can send. Times in UTC, so it lands correctly in any client. |
event_to_time_entry | Turn one meeting into the exact arguments for the time-tracker's entry_add, so a call becomes billable time without retyping it. |
ics_forget | Remove one calendar and its local copy. |
license_status / license_activate | Show the tier; activate a Pro key offline. |
Resource calendar://today gives today's schedule in one read. Prompt plan_my_day walks the whole loop: what is on, what clashes, where the free stretches are, and which finished meetings to bill.
Written against real exports, not just the spec: line folding (CRLF, bare LF and bare CR, and folds that Exchange places inside a multi-byte character, which are rejoined on the bytes before decoding), \n \, \; \\ escaping, whole-day events with an exclusive DTEND, DURATION instead of DTEND, TZID and UTC times, floating times, RRULE for HOURLY, DAILY, WEEKLY, MONTHLY and YEARLY with COUNT, UNTIL (inclusive), INTERVAL, BYDAY including ordinals (2MO, -1FR), BYMONTHDAY, BYMONTH and BYSETPOS, EXDATE, RDATE, RECURRENCE-ID overrides (the moved instance replaces the original instead of appearing twice), STATUS:CANCELLED, TRANSP:TRANSPARENT, and VALARM blocks inside an event. An event it cannot read is skipped and counted rather than costing you the rest of the file.
FREQ=MINUTELY and FREQ=SECONDLY are deliberately not expanded: one such rule fills any window with thousands of occurrences and buries the rest of the week. Those events are listed at their first occurrence and the reason is said out loud. A rule with no COUNT and no UNTIL is expanded only as far as the window you asked for.
Exports written by this server keep whole-day events as DATE values, so a holiday leaves as the same day it arrived rather than a timed block on the day before in your machine's zone.
VTIMEZONE is deliberately ignored. A file's inline DST rules are only as fresh as the app that wrote it; the TZID is kept and every offset is computed from the ICU data inside your Node build instead, which is what keeps a weekly Warsaw 10:00 meeting at 10:00 local across the March clock change.
| Free | Pro ($19 one-time) | |
|---|---|---|
| Calendars kept | 2 | unlimited |
| Window per question | up to 31 days | any window |
conflicts over a longer window | answered for the first 31 days, cap named | any window |
| Events per export | 50 | unlimited |
| Import from a URL or webcal feed | -- | yes |
| Everything else | full | full |
Get Pro, or $39 for every server in the suite, lifetime.
Everything is local. The calendar file you import is copied to ${XDG_DATA_HOME:-~/.local/share}/mcp-servers/calendar/ and read from there; deleting that directory resets the server. There is exactly one network call in the whole server, and only when you pass a url yourself: it fetches that address once, with a 12-second timeout, a 5 MB cap, and a refusal on loopback, private and cloud-metadata addresses. Nothing is uploaded, no account is linked, and licence keys verify offline.
.ics engine from it: convert a meeting time, find slots across countries, write an invite.event_to_time_entry hands it a finished meeting; it tracks and reports the hours.No. There is no OAuth, no token and no sync. You export a file (or paste a public feed URL on Pro) and it is read locally. That also means an import is a snapshot: re-import when the calendar has moved on.
Yes, and that is most of the code. A weekly series is expanded on the wall clock, so a Warsaw 10:00 meeting stays 10:00 through the DST change rather than drifting to 11:00. Monthly on the 31st skips February instead of rolling into March, UNTIL includes the occurrence that falls exactly on it, and a single moved instance replaces the original.
It is not: RFC 5545 makes DTEND exclusive for a whole-day event, so 1--3 June means the 1st and the 2nd. This server follows the spec, which is what your calendar app does too.
It writes .ics files with event_export, which you can import anywhere. It never modifies the calendar it read.
5 MB, which is a few thousand events. Export a narrower date range if a full history is bigger than that.
Any MCP client (Claude, Cursor, Windsurf, VS Code) can read this repository's documentation directly via GitMCP - no install: