mcpbeat Sign in

Sync MCP Server

not responding

Sync is listed as active in the registry but did not answer our last check. It exposes 5 tools.

Check availability, book meetings and find group times — without sharing your calendar.

Uptime history 8 days of history · worst day 0%
8 days agonow
3.3%
Uptime 24h
3 of 91 checks
5
Tools
read from the server
438 ms
Response time
average over 24h
open, no key
Access
streamable-http

Sync does not always answer

Over the last week it answered 0.8% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add sync --transport http https://sync.lucie.network/api/mcp
Settings → Connectors → Add custom connector, then paste this address
https://sync.lucie.network/api/mcp
~/.codex/config.toml
[mcp_servers.sync]
url = "https://sync.lucie.network/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "sync": {
      "url": "https://sync.lucie.network/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "sync": {
      "type": "http",
      "url": "https://sync.lucie.network/api/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

book
book_group_meeting
Confirm a group meeting at a specific time across several Lucie hosts (by @handle), creating ONE shared Google Calendar event with everyone invited. YOU (the connector's owner) are the organizer and host the event on your calendar — no organizer handle needed. This is a real write: it re-verifies every participant (you included) is free at that instant and refuses if anyone isn't — so it never double-books. Always call find_group_times first and copy an exact common-slot start. Before calling, confirm the time (in each person's zone), the participants, the title, and the reason. Requires you to be on Sync Pro (or a Lucie Membership) via your personal connector; everyone must have a live booking page.
book_meeting
Book a confirmed meeting on a Lucie Sync host's calendar at a specific start time. This is a real write: it creates a calendar event and emails both the host and the booker. Always call check_availability first and use one of the open slots it returns. Before calling, (1) show the booker the specific date/time you're about to book — in their own time zone — and get their explicit confirmation, and (2) collect their name, email, AND a brief reason for the meeting (ask for the reason if not given; it's required and shared with the host).
group
create_group_event
Create a Lucie group event (a poll) for several participants, pre-filled with candidate times when everyone is free (the intersection of their availability). Returns a vote link to share: participants pick which proposed times work, and people WITHOUT a Lucie handle can vote manually too. This is a write (creates a poll) but sends no emails and touches no calendars. Confirm the title, participants, and duration with the organizer before creating. Note: agent group scheduling is a Sync Pro feature — the organizer's email must be on Sync Pro (or a Lucie Membership).
find_group_times
Given several Lucie hosts (by @handle), return the meeting times when ALL of them are free — the intersection of their availability — for a meeting of the given length. Read-only: never books, never exposes anyone's raw calendar (only the shared open slots). Use it to propose a group time. Times are absolute instants; pass viewerTimeZone so they show in the organizer's local zone.
availability
check_availability
Return the open meeting slots a Lucie Sync host offers, plus their booking rules (durations offered, minimum notice, how far ahead you can book, buffer between meetings). Returns only bookable slots and policy — never the host's raw calendar. Use this to find a time before proposing one to the user. Slots are absolute instants (ISO-8601 UTC). Pass the booker's viewerTimeZone so times display in THEIR local zone — the booker should never have to do time-zone math.

Endpoints

URLTransportStateLatencyChecked
https://sync.lucie.network/api/mcp streamable-http answering 74 ms 12 min ago

Alternatives to Sync

same job, measured the same way
Meet.bot MCP
by meet

AI-native scheduling and booking: check availability, book meetings, share links.

8 tools answering
Astrocal
by astrocal

AI-native scheduling: check availability, book meetings, cancel and reschedule via MCP

17 installs/wk answering
AllMyMeetings
by allmymeetings

Sync Google, Outlook, and iCloud calendars and manage events, availability, and booking links.

answering
MCP Meet
by pzep1

One-click Google Meet scheduling and Apple Calendar mirroring with smart availability detection

local only
Calendly MCP Server
by nyxtoolsdev

Connect Claude to Calendly — schedule meetings, check availability, manage events

106 installs/wk local only
RentalCal
by rentalcal

Find direct-booking vacation rentals, check availability, and get stay quotes.

4 tools answering
AgentBookable
by agentbookable

Find local services, check live availability, and book real appointments with consent.

9 tools answering
W
Whenly — group meeting scheduler for AI agents
by workers-notdown-app-whenly

Find a time a group can meet: no-login availability poll that picks the best meeting slot.

2 tools answering

Sync — questions

Answers built from our own checks of this server.

What can Sync do?
It exposes 5 tools, read directly from the server on our last check. Among them: book_group_meeting, book_meeting, check_availability, create_group_event, find_group_times. 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 Sync mostly used for?
Its tools cluster around book and group. 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 Sync working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 3 of 91 checks got a reply (3.3%), average response time 438 ms. The bar chart above shows every period we have measured.
The registry lists Sync as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Sync?
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 Sync need an API key?
No. Sync completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Sync?
It answers our handshake in 438 ms on average, which is faster than 31% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.