mcpField
M
MeetSync MCP Server

MeetSync MCP Server

Local
github.com/nicholasemccormickDeveloper Tools0Updated 29w ago

About MeetSync MCP Server

MeetSync MCP Server exposes MeetSync's calendar negotiation API as MCP tools. It is for AI agents that need to find shared availability, coordinate proposals, and manage bookings using API-key authentication.

Key features

  1. 01Participant and preference management
  2. 02Individual and mutual availability search
  3. 03Create and track meeting proposals
  4. 04Confirm, reschedule, or cancel bookings
  5. 05API-key authentication

Use cases

  1. 01Find meeting slots that fit multiple participants
  2. 02Send candidate times for participant responses
  3. 03Turn an accepted proposal into a booking
  4. 04Reschedule or cancel an existing meeting

MCP support

Exposes all 19 MeetSync API operations as named tools over MCP. MCP clients use the server to call the API with an API key.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"meetsync": {
"command": "npx",
"args": [
"-y",
"mcp-meetsync"
],
"env": {
"MEETSYNC_API_URL": "<MEETSYNC_API_URL>",
"MEETSYNC_API_KEY": "<MEETSYNC_API_KEY>"
}
}
}
}
Run commandnpx -y mcp-meetsync
Environment variables to set
MEETSYNC_API_URL
MEETSYNC_API_KEYSecret

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npmmcp-meetsync

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

mcp-meetsync

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.


Installation

npm install -g mcp-meetsync

Or run directly with npx:

npx mcp-meetsync

Configuration

The server reads two environment variables:

VariableRequiredDefaultDescription
MEETSYNC_API_URLNohttp://localhost:3000Base URL of your MeetSync API
MEETSYNC_API_KEYYes—API key sent in X-API-Key header

Copy .env.example to .env and fill in your values, or pass them directly in the Claude tool definition.


Adding to Claude

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.


Tools

All 19 MeetSync operationIds are exposed as tools. Tool names match operationIds exactly.

Participants (7 tools)
ToolWhen to use
listParticipantsBrowse or search registered participants
createParticipantRegister a new person before they can be scheduled
getParticipantLook up a specific participant's timezone/provider details
updateParticipantChange a participant's name, email, timezone, or calendar setup
deleteParticipantPermanently remove a participant (use force to cascade)
getParticipantPreferencesRead a participant's working hours and scheduling constraints
setParticipantPreferencesDefine or replace working hours, blackout windows, and buffers
Availability (2 tools)
ToolWhen to use
getParticipantAvailabilityFind free windows for a single participant
findMutualAvailabilityFind scored slots that work for all participants simultaneously
Proposals (5 tools)
ToolWhen to use
listProposalsBrowse pending or historical proposals
createProposalPropose candidate time slots and send to participants for consensus
getProposalCheck proposal status and see who has responded
cancelProposalWithdraw a pending proposal
respondToProposalRecord a participant's acceptance or rejection
Bookings (5 tools)
ToolWhen to use
listBookingsBrowse confirmed, cancelled, or rescheduled meetings
createBookingConfirm a booking from an accepted proposal, or book directly
getBookingRetrieve full details of a specific meeting
rescheduleBookingMove a confirmed meeting to a new time
cancelBookingCancel a meeting permanently

Example agent workflow

Here is a complete scheduling workflow an AI agent would follow using these tools:

1. createParticipant  ← register [email protected]
2. createParticipant  ← register [email protected]
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

Development

# 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 dev

Architecture

src/
  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 + handlers

Each 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

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.