A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
Nothing to run from here
Sync is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
5
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Check availability, book meetings and find group times — without sharing your calendar.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http sync-mcp https://sync.lucie.network/api/mcp
# 2 — ask your agent for something these tools do
# check_availability, book_meeting, find_group_times and 2 more
Sync costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
LUAll 1 server
lucie1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http sync-mcp https://sync.lucie.network/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
5 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 TH
| Parameter | Type | Required | Notes |
|---|---|---|---|
| handle | string | yes | The host's booking handle, e.g. "@alice" or "alice" (from their lucie.network/book/@<handle> link). The leading @ is optional. |
| durationMinutes | integer | no | Desired meeting length in minutes. Must be one the host offers. Defaults to 30 if omitted. |
| viewerTimeZone | string | no | The booker's IANA time zone, e.g. "Asia/Singapore" or "America/New_York". Pass the booker's own zone so slots are shown in their local time. Defaults to the host's zone if omitted. |
| from | string | no | ISO-8601 start of the search window. Defaults to now + the host's minimum notice. |
| to | string | no | ISO-8601 end of the search window. Defaults to the host's max-advance horizon. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| handle | string | yes | The host's booking handle, e.g. "@alice" or "alice" (the leading @ is optional). |
| startAt | string | yes | The exact ISO-8601 start value copied verbatim from a check_availability slot (an absolute UTC instant, e.g. 2026-07-28T17:00:00Z). Do NOT construct this from a local wall-clock time the booker said |
| durationMinutes | integer | yes | Meeting length in minutes. Must be one the host offers. |
| bookerName | string | yes | Full name of the person the meeting is for (the booker). |
| bookerEmail | string | yes | The booker's email. The confirmation and calendar invite are sent here. |
| reason | string | yes | A short description of why the booker wants to meet (the agenda / purpose). Required — ask the booker for it before booking. Shared with the host alongside the invite. |
| viewerTimeZone | string | no | The BOOKER's IANA time zone (e.g. America/New_York) — the same one you passed to check_availability. Their confirmation email and reminders are written in this zone, so without it they read the host's |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| handles | array | yes | The participants' booking handles, e.g. ["@alice", "@bob"]. The leading @ is optional. |
| durationMinutes | integer | no | Meeting length in minutes. Must be one every participant offers. Defaults to 30. |
| viewerTimeZone | string | no | The organizer's IANA time zone, e.g. "America/New_York". Common times are shown in this zone. Defaults to UTC. |
| from | string | no | ISO-8601 start of the search window. |
| to | string | no | ISO-8601 end of the search window. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| title | string | yes | The meeting title, e.g. "Q3 planning sync". |
| handles | array | yes | Participants' @handles whose availability seeds the candidate times. The leading @ is optional. |
| organizerName | string | yes | The organizer's name (shown on the poll). |
| organizerEmail | string | yes | The organizer's email. |
| durationMinutes | integer | no | Meeting length in minutes. Defaults to 30. |
| timeZone | string | no | IANA time zone for the poll's displayed times, e.g. "America/New_York". Defaults to UTC. |
| from | string | no | ISO-8601 start of the search window. |
| to | string | no | ISO-8601 end of the search window. |
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 dou
| Parameter | Type | Required | Notes |
|---|---|---|---|
| participantHandles | array | yes | The other participants' @handles, e.g. ["@lucie", "@taylor"]. Each must have a live Lucie booking page. Leading @ optional. |
| startAt | string | yes | The exact ISO-8601 start copied verbatim from a find_group_times common slot (absolute UTC instant). Do NOT construct it from a wall-clock time. |
| durationMinutes | integer | yes | Meeting length in minutes. Must be one the organizer offers. |
| title | string | yes | The meeting title, e.g. "Q3 planning sync". |
| reason | string | yes | A short agenda/purpose, shared with everyone on the invite. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Sync or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Sync can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.