INDIVIDUAL MCP TOOL
submit_availability
Save (or replace) one person's availability: the candidate start keys they can make, from get_event.
LIVE ENDPOINT
https://sync.day/mcp/mcp
Connect to this endpoint to inspect the live schema for submit_availability and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.sync-day]
url = "https://sync.day/mcp/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"sync-day": {
"type": "http",
"url": "https://sync.day/mcp/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: sync-day
Remote MCP URL: https://sync.day/mcp/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"sync-day": {
"url": "https://sync.day/mcp/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"sync-day": {
"type": "http",
"url": "https://sync.day/mcp/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "sync-day",
"transport": "streamable-http",
"url": "https://sync.day/mcp/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
create_event— Create a sync.parse_event_text— Turn a natural-language sentence (Chinese works best) into create_event input using sync.get_event— Read an event: settings, every candidate start key per day (startOptions), who has answered (participants with their start keys; names may repeat), the top 10 start times by head-count (ranked), the starts EVERYONE with picks can make with their votes (voteOptions), each person's vote (votes) and decidedStart.remove_participant— Organiser only: remove one participant by name (the oldest row with that name when it repeats), together with their vote.update_event— Organiser only: change any event settings (same fields and rules as create_event; omitted fields keep their current value; endDate wins over days).vote_time— Approval voting: set every start one person accepts (replaces their earlier approvals; an empty list clears them).decide_time— Organiser only: settle on a start time (locks availability picking and voting; the page shows 已定).