Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-meetsync Find a time for Alice and Bob to meet for an hour next Tuesday."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
MCP server for MeetSync — a calendar negotiation API built for AI agents.
Exposes all 19 MeetSync endpoints as MCP tools so any MCP-compatible LLM can autonomously find availability, propose meeting times, and confirm bookings — no human back-and-forth required.
npm install -g mcp-meetsyncOr run directly with npx:
npx mcp-meetsyncRelated MCP server: M365 Calendar MCP Server
The server reads two environment variables:
Variable | Required | Default | Description |
| No |
| Base URL of your MeetSync API |
| Yes | — | API key sent in |
Copy .env.example to .env and fill in your values, or pass them directly in the Claude tool definition.
Paste this snippet into your Claude desktop configuration (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):
{
"mcpServers": {
"meetsync": {
"command": "npx",
"args": ["-y", "mcp-meetsync"],
"env": {
"MEETSYNC_API_URL": "https://api.yourmeetsync.com",
"MEETSYNC_API_KEY": "your-api-key-here"
}
}
}
}After saving, restart Claude. The 19 MeetSync tools will appear in Claude's tool list.
All 19 MeetSync operationIds are exposed as tools. Tool names match operationIds exactly.
Tool | When to use |
| Browse or search registered participants |
| Register a new person before they can be scheduled |
| Look up a specific participant's timezone/provider details |
| Change a participant's name, email, timezone, or calendar setup |
| Permanently remove a participant (use |
| Read a participant's working hours and scheduling constraints |
| Define or replace working hours, blackout windows, and buffers |
Tool | When to use |
| Find free windows for a single participant |
| Find scored slots that work for all participants simultaneously |
Tool | When to use |
| Browse pending or historical proposals |
| Propose candidate time slots and send to participants for consensus |
| Check proposal status and see who has responded |
| Withdraw a pending proposal |
| Record a participant's acceptance or rejection |
Tool | When to use |
| Browse confirmed, cancelled, or rescheduled meetings |
| Confirm a booking from an accepted proposal, or book directly |
| Retrieve full details of a specific meeting |
| Move a confirmed meeting to a new time |
| Cancel a meeting permanently |
Here is a complete scheduling workflow an AI agent would follow using these tools:
1. createParticipant ← register alice@example.com
2. createParticipant ← register bob@example.com
3. setParticipantPreferences ← Alice: Mon–Fri 09–17, 15 min buffer
4. setParticipantPreferences ← Bob: Mon–Fri 10–18, no back-to-back
5. findMutualAvailability ← find 60-min slots next week for [alice, bob]
→ returns top 5 scored slots
6. createProposal ← "Budget Review" with top 3 slots, expires in 24h
→ proposal id: prop_abc123
7. respondToProposal ← alice accepts, prefers slot 1
8. respondToProposal ← bob accepts, prefers slot 1
→ proposal auto-transitions to "accepted", acceptedSlotId set
9. getProposal ← confirm acceptedSlotId
10. createBooking ← proposalId + slotId
→ booking confirmed, calendarEventIds written# Install dependencies
npm install
# Type-check without building
npm run typecheck
# Build to dist/
npm run build
# Run in dev mode (auto-reloads)
MEETSYNC_API_URL=http://localhost:3000 MEETSYNC_API_KEY=dev-key npm run devsrc/
index.ts ← MCP Server, ListTools + CallTool handlers, stdio transport
client.ts ← Typed fetch wrapper: GET/POST/PUT/PATCH/DELETE + X-API-Key injection
tools/
participants.ts ← 7 participant tools + handlers
availability.ts ← 2 availability tools + handlers
proposals.ts ← 5 proposal tools + handlers
bookings.ts ← 5 booking tools + handlersEach tool file exports:
A Tool[] array with name, description, and inputSchema (strict JSON Schema)
A handle*Tool(name, args) async function that calls the MeetSync API via client
MIT
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Calendar API for AI agents: events, availability, Google/Microsoft setup, scheduling, and iCal.
AI-native scheduling: check availability, book meetings, cancel and reschedule via MCP
Agentic scheduling & booking for field service: availability, jobs, customers, crews, fleet.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/nicholasemccormick/mcp-meetsync'
If you have feedback or need assistance with the MCP directory API, please join our Discord server