MeetSync MCP Server

by nicholasemccormick

277 downloads

Not rated

GitHub

About

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.

Details

Author: nicholasemccormick
Downloads: 277
Categories: Developer Tools, AI

- 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

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

Download and install Highlight from highlightai.com/download
Navigate to the plugins tab and select "Add Custom Plugin"
Configure the plugin with the settings below

Plugin Name MeetSync MCP Server

Command (node, npx, python, etc.)

Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
Enable "Start Automatically" if you want the plugin to start when Highlight launches

Setting up with Cursor

Open Cursor's settings
Navigate to the MCP section
Click "Add new Global MCP server"
Copy and paste the configuration below based on your operating system

JSON

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

JSON

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

JSON

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

Setting up with Claude Desktop

Open Claude Desktop's settings
Go to the Integrations tab
Click "Add MCP Server"
Use the configuration below based on your operating system

Note: Make sure Claude Desktop is running before attempting to connect.

JSON

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

JSON

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

JSON

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

Setting up with Windsurf

Open Windsurf's preferences
Go to the Integrations section
Click "Add MCP Integration"
Use the configuration below based on your operating system

JSON

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

JSON

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

JSON

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

Setting up with Cline

Open Cline's settings
Navigate to the Integrations section
Click "Add MCP Server"
Copy and paste the configuration below based on your operating system

Note: Make sure to restart Cline after adding the configuration.

JSON

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

JSON

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

JSON

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

Setting up with Goose

Open Goose's preferences
Go to the Integrations tab
Select "MCP Servers"
Click "Add New Server"
Use the configuration below based on your operating system

JSON

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

JSON

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

JSON

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

From the repository

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.

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

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

McpServers

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

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:

| Variable | Required | Default | Description |
|--------------------|----------|--------------------------|--------------------------------------|
| MEETSYNC_API_URL | No | http://localhost:3000 | Base URL of your MeetSync API |
| MEETSYNC_API_KEY | Yes | — | 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)

| Tool | When to use |
|----------------------------|-------------------------------------------------------------------|
| listParticipants | Browse or search registered participants |
| createParticipant | Register a new person before they can be scheduled |
| getParticipant | Look up a specific participant's timezone/provider details |
| updateParticipant | Change a participant's name, email, timezone, or calendar setup |
| deleteParticipant | Permanently remove a participant (use force to cascade) |
| getParticipantPreferences| Read a participant's working hours and scheduling constraints |
| setParticipantPreferences| Define or replace working hours, blackout windows, and buffers |

Availability (2 tools)

| Tool | When to use |
|-----------------------------|-----------------------------------------------------------------|
| getParticipantAvailability| Find free windows for a single participant |
| findMutualAvailability | Find scored slots that work for all participants simultaneously |

Proposals (5 tools)

| Tool | When to use |
|--------------------|--------------------------------------------------------------------------|
| listProposals | Browse pending or historical proposals |
| createProposal | Propose candidate time slots and send to participants for consensus |
| getProposal | Check proposal status and see who has responded |
| cancelProposal | Withdraw a pending proposal |
| respondToProposal| Record a participant's acceptance or rejection |

Bookings (5 tools)

| Tool | When to use |
|--------------------|--------------------------------------------------------------------------|
| listBookings | Browse confirmed, cancelled, or rescheduled meetings |
| createBooking | Confirm a booking from an accepted proposal, or book directly |
| getBooking | Retrieve full details of a specific meeting |
| rescheduleBooking| Move a confirmed meeting to a new time |
| cancelBooking | Cancel a meeting permanently |

---

Example agent workflow

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

---

Development

```bash

No reviews yet — be the first

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.

About

Details

Jump to

Setting up with Highlight

From the repository

Claude Desktop / Cursor

McpServers

mcp-meetsync

Installation

Configuration

Adding to Claude

Tools

Participants (7 tools)

Availability (2 tools)

Proposals (5 tools)

Bookings (5 tools)

Example agent workflow

Development

Install

More like this

Sentry

Github

Git

GitLab

Context 7

1Panel