MeetSync MCP Server

@nicholasemccormick

代码仓库

基本信息

分类

开发工具

传输方式

stdio

作者

nicholasemccormick

提交者

Nickitico

关于 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.

#scheduling #calendar #ai-agent #mcp #booking #availability

MeetSync MCP Server 配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "meetsync": {
      "command": "npx",
      "args": [
        "mcp-meetsync"
      ],
      "env": {
        "MEETSYNC_API_URL": "https://your-api-url",
        "MEETSYNC_API_KEY": "your-api-key"
      }
    }
  }
}

MeetSync MCP Server 工具

工具列表暂未提供

当前收录暂时没有可展示的工具列表，不代表服务没有工具。请查阅项目文档了解支持的能力。

点击上方按钮,在临时沙箱中运行此服务器并实时获取工具列表。

概览

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

常见问题

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.