Three servers that all convert a time between zones, and then diverge. stockvibes07/meeting-mcp is a hosted scheduling assistant with a public holiday dataset and Google Calendar event creation, paid per call. @iflow-mcp/timezone-toolkit is a local time utility that reaches into sunrise, sunset, twilight and moon phase. Ours is a meeting planner: ranked slots inside everyone's working hours, the honest overlap, and the invite file.
| Fact | Ours | meeting-mcp | timezone-toolkit |
|---|---|---|---|
| Tools | 9 plus license_status and license_activate | 6: convert_time, get_holidays, check_business_hours, find_meeting_slots, create_calendar_link, create_event | 9: convert_time, get_current_time, sunrise/sunset, moon phase, timezone difference, list_timezones, countdown, business days, format_date |
| Transport | stdio (npx or .mcpb bundle) | Hosted streamable HTTP at meeting-mcp--stockvibes07.run.tools | stdio (npx) |
| Licence | MIT | Hosted service, no package licence to read | ISC |
| Latest version read | publish pending; .mcpb bundle and clone-and-build | Smithery registry entry, read 2026-09-03 | 1.0.1, published 2025-08-08 on npm |
| Cost per call | None. Runs locally | x402: its listing says $0.01 per call, no signup needed | None |
| Ranks slots by fairness | Yes, worst participant's distance from 13:00 local | find_meeting_slots is listed; no ranking rule published | No slot finder |
| Public holidays | No. Pass them to business_days yourself | Yes, 100+ countries | Bundles date-holidays as a dependency |
| Writes an .ics file | Yes, UTC times, no VTIMEZONE block | Calendar link and Google Calendar event creation | No |
| Saved contacts with working hours | Yes, 5 free, unlimited on Pro | No | No |
| Network calls | None at all | Hosted, every call is a request | Local, but it bundles express-rate-limit and suncalc |
The meeting-mcp row was read from its Smithery registry entry and the timezone-toolkit rows from its npm registry record and README, both on 2026-09-03.
Pick it when you want the holidays and the calendar write, and you are happy paying per call. Its
get_holidays covers more than 100 countries, which is real work we have not done: ours knows
weekends and the working hours you give it, and holidays only if you pass them into
business_days. It also creates the Google Calendar event rather than handing you a file to
attach. If the agent needs to put the meeting in a calendar without a human, that is the one.
Pick it when the question is about the sky or the clock rather than about a meeting. Sunrise, sunset,
civil, nautical and astronomical twilight, day length and moon phase for a location and date are things
we do not compute at all, and it adds countdowns and date formatting across locales. It runs locally like
ours and is ISC licensed. It has no slot finder, no overlap window and no .ics output, so it
is a complement to a planner rather than a replacement for one.
Pick ours when the output has to be a time three people will actually accept. Slots are offered only
when the whole meeting, start to end, sits inside every participant's own working window on their own
local calendar day, and every candidate is scored by the worst participant's distance from 13:00 local,
not the average, so a slot that is pleasant for two and 07:00 for the third never outranks one that is
10:00 for everybody. When nothing fits, the server says so and shows the windows instead of proposing a
06:00 call. The .ics it writes carries UTC times and no VTIMEZONE block on
purpose, because a hand-written block with stale rules is the usual way an invite lands an hour off. No
network call is made anywhere, including for license activation.
DST is not stored here; every offset comes from the ICU data inside your Node build, and the
consequence is measurable. Warsaw and New York, both on 09:00 to 17:00 days, share exactly 2 hours on
2026-09-10, when Warsaw is UTC+2 and New York UTC-4, and 3 hours on 2026-03-16, when Warsaw is still
UTC+1 because Europe does not change until 29 March while the United States changed on 8 March. A
recurring call booked at the edge of that wider March window falls outside somebody's working day at the
end of the month. Place names resolve through a table of 510 entries, each verified against
Intl.supportedValuesOf("timeZone") at startup, and an unknown name returns suggestions
rather than a guess.
Ours, Claude Code:
claude mcp add timezone -- npx -y @theluckystrike/mcp-timezonemeeting-mcp:
claude mcp add --transport http meeting https://meeting-mcp--stockvibes07.run.toolstimezone-toolkit:
claude mcp add timezone-toolkit -- npx -y @iflow-mcp/timezone-toolkitPer client config paths for ours are on the setup pages, the product page is MCP Timezone Planner, and the walkthrough is in meeting slots across time zones.
meeting-mcp does, for more than 100 countries, and timezone-toolkit bundles the date-holidays package. Ours does not: business_days excludes weekends and any holidays you pass it, and the README says so rather than implying a holiday calendar exists.
meeting-mcp creates Google Calendar events and calendar links. Ours writes an .ics file to your disk and never connects to a calendar service, which is the trade: nothing of yours is held by a third party, and you attach the file yourself.
Ours and timezone-toolkit run locally. meeting-mcp is a hosted endpoint, so every call is a request, and its listing prices calls at $0.01 through x402.
Each candidate is scored by the worst participant's distance from 13:00 in their own local time, in hours, and slots are sorted ascending. A fairness of 0 would be midday for everyone; under about 2 is comfortable. Three hours on a Warsaw and New York pair is the truth about that pair, not a ranking failure.
meeting-mcp publishes its tool list, transport and pricing on its Smithery registry entry; timezone-toolkit publishes its tool table, licence and dependencies on npm. Both were read on 2026-09-03 and the URLs are in docs/CONTENT_R3_RESULT.md.