MeetSync MCP Server
@nicholasemccormick
About MeetSync MCP Server
Calendar negotiation API for AI agents. Exposes all 19 MeetSync endpoints as named MCP tools — find mutual availability across participants, manage scheduling proposals, and confirm bookings directly from Claude or any MCP-compatible agent. No OAuth required, API key auth only.
Basic information
Config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"meetsync": {
"command": "npx",
"args": [
"mcp-meetsync"
],
"env": {
"MEETSYNC_API_URL": "https://your-api-url",
"MEETSYNC_API_KEY": "your-api-key"
}
}
}
}Tools
No tools detected
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Overview
What is MeetSync MCP Server?
MeetSync MCP Server is an MCP server for the MeetSync calendar negotiation API, built for AI agents. It exposes all 19 MeetSync endpoints as MCP tools, enabling any MCP-compatible LLM to autonomously find availability, propose meeting times, and confirm bookings without human back-and-forth.
How to use MeetSync MCP Server?
Install globally with npm install -g mcp-meetsync or run with npx mcp-meetsync. Configure two environment variables: MEETSYNC_API_URL (optional, default http://localhost:3000) and MEETSYNC_API_KEY (required). Add the server to Claude Desktop by pasting the provided JSON snippet into its configuration file, then restart Claude. The 19 tools appear automatically.
Key features of MeetSync MCP Server
- Exposes all 19 MeetSync operationIds as MCP tools
- Seven participant management tools (register, update, delete, preferences)
- Two availability tools (single participant and mutual availability with scoring)
- Five proposal tools (create, respond, cancel, list, get)
- Five booking tools (create, reschedule, cancel, list, get)
- Typed fetch wrapper with automatic X-API-Key injection
- Uses stdio transport for MCP communication
Use cases of MeetSync MCP Server
- Automatically register participants and set working-hour preferences
- Find mutually available scored time slots for multiple participants
- Propose meeting times and collect acceptances or rejections
- Confirm, reschedule, or cancel bookings directly from an AI agent
- Execute a complete scheduling workflow without human intervention
FAQ from MeetSync MCP Server
What runtime and dependencies are required?
Node.js is required. The server runs via npx or after global installation. Only environment variables for API URL and API key are needed.
How does the server communicate with the MeetSync API?
The server uses a typed fetch wrapper (client.ts) that sends HTTP requests to the configured MEETSYNC_API_URL and injects the MEETSYNC_API_KEY as the X-API-Key header.
What transport does the MCP server use?
It uses stdio transport, as shown in the architecture where index.ts contains the MCP server with ListTools and CallTool handlers over stdio.
How are API keys and data handled?
The API key is read from the MEETSYNC_API_KEY environment variable and sent in the X-API-Key header. Data lives on the MeetSync API server; no local storage is used.
Are there any known limits or unsupported endpoint features?
The README does not mention any limits. It exposes all 19 MeetSync operationIds as tools exactly matching the API operationIds.
More Developer Tools MCP servers
Burp Suite MCP Server Extension
PortSwiggerMCP Server for Burp
MCP Framework
QuantGeekDevThe Typescript MCP Framework

Sentry
modelcontextprotocolModel Context Protocol Servers
MCP-Scan: An MCP Security Scanner
invariantlabs-aiSecurity scanner for AI agents, MCP servers and agent skills.
TalkToFigma
sonnylazuardiTalkToFigma: MCP integration between AI Agent (Cursor, Claude Code, Codex) and Figma, allowing Agentic AI to communicate with Figma for reading designs and modifying them programmatically.
Comments