AI / MCP Integration
Synced integrates with AI assistants through the Model Context Protocol (MCP), an open standard that lets language models interact with external tools and data sources. Instead of copy-pasting calendar links or switching between apps, you can manage your entire scheduling workflow through natural conversation.
What is MCP?
The Model Context Protocol is an open protocol that standardizes how AI models connect to external systems. It defines a set of "tools" that a model can call, along with their input schemas and descriptions. When a user asks Claude to "schedule a meeting with Sarah next Tuesday," MCP is the layer that translates that request into a structured API call to Synced.
MCP supports multiple transports — stdio for local desktop applications and SSE (Server-Sent Events) for web-based clients — so Synced works seamlessly in both Claude Desktop and Claude.ai.
How Synced Uses MCP
Synced exposes a dedicated MCP server that provides six tools covering the full scheduling lifecycle:
- Read your calendar — Retrieve upcoming, past, or draft meetings
- Check availability — See free/busy slots for any date
- Find optimal times — Get AI-powered slot recommendations across multiple participants
- Schedule meetings — Create meetings with calendar invites sent automatically
- Natural language scheduling — Parse freeform requests like "coffee with Alex Friday afternoon"
- Manage contacts — Access your trusted contacts list
Benefits
Natural Language Scheduling
No more toggling between your calendar app, email, and chat. Tell Claude what you need in plain language — "find 30 minutes with the design team next week" — and it handles availability checks, slot selection, and invite sending in one step.
AI Agent Workflows
MCP tools can be composed into multi-step workflows. An AI agent can check your availability, cross-reference it with a participant's schedule, propose the best slot, and book the meeting — all within a single conversation turn.
Automation at Scale
Because MCP tools are structured API calls under the hood, they integrate cleanly into automated pipelines. Use them inside Claude-based agents, scheduled tasks, or any system that supports the MCP protocol.
Supported MCP Clients
Synced's MCP server works with the following clients:
| Client | Transport | Setup Guide |
|---|---|---|
| Claude Desktop | stdio | Claude Desktop (stdio) |
| Claude.ai Web | SSE | Claude.ai Web (SSE) |
Other MCP clients
Any MCP-compatible client that supports stdio or SSE transport can connect to Synced. The setup steps are similar — you provide the server command (stdio) or URL (SSE) along with your API key.Architecture Overview
The integration follows a straightforward flow:
- User sends a message — e.g., "What's on my calendar tomorrow?"
- Claude selects the right tool — Based on the message, Claude picks the appropriate MCP tool (e.g.,
get_meetings) and constructs the parameters - MCP transport delivers the call — The request is sent to Synced's MCP server via stdio (Desktop) or SSE (Web)
- Synced processes the request — The server authenticates with your API key, queries your connected calendars, and returns structured data
- Claude formats the response — The raw data is presented as a natural language answer in the conversation
User ──▶ Claude ──▶ MCP Transport ──▶ Synced MCP Server ──▶ Calendar APIs
(stdio / SSE) (authenticated) (Google / Outlook)