meetergo
Model Context Protocol

Your agent runs your calendar

Nine MCP tools over the meetergo API. Find slots, book, reschedule, cancel — from Claude, Cursor, or anything that speaks MCP.

Get your API tokenRead the docs
claude_desktop_config.json
{
  "mcpServers": {
    "meetergo": {
      "command": "npx",
      "args": ["-y", "@meetergo/mcp-server"],
      "env": { "MEETERGO_TOKEN": "pat_your_token" }
    }
  }
}
MIT licensedSource on GitHub@meetergo/mcp-server

Prefer to write the integration yourself? The REST API has 100 endpoints.

What it does on day one

Every one of these is buildable with the nine tools below and nothing else.

Protect prep time

Your agent reads tomorrow's calendar and blocks focus time ahead of every external meeting, while there is still room to.

Rebook no-shows

It spots the meeting nobody joined, finds the next slot that works, and sends the invitation. Nobody chases anyone.

Route inbound leads

A lead lands in your CRM and the agent books it into the right host's calendar, with the context already in the invite.

Nine tools

Four of them write, and they declare it — so your MCP client can ask a human before an agent books or cancels anything.

list_meeting_typesWhat can be booked. Start here.
get_availabilityBookable slots for a meeting type and date range.
book_appointmentBook a slot. Sends the real invitations.writes
reschedule_appointmentMove a meeting. Duration stays the same.writes
cancel_appointmentCancel, or drop a single attendee from a group booking.writes
list_appointmentsThe calendar, paginated.
get_todays_appointmentsToday only.
add_guestsAdd guest emails to a meeting that already exists.writes
list_calendar_connectionsWhich calendars are actually connected.

The API has 100 endpoints. We expose nine, because an agent choosing between a hundred near-identical operations chooses worse than one choosing between nine. Everything else stays available over REST.

Your agent reads calendar data. Ours never leaves Germany.

An agent with calendar access sees attendee names, email addresses and meeting subjects. That is a GDPR question before it is a developer-experience question — and it is the one every US-hosted scheduler answers the same way.

See the security modelRead the source
  • Servers Germany. No US parent company.
  • Contracts Real GDPR liability, not a self-certification.
  • Access Scoped to your Personal Access Token. Revoke it and the agent stops.
  • Confirmation Writes are flagged, so your client can require a human before anything changes.
  • Source MIT licensed and published in full. Read it before you connect it.

Questions

Does meetergo have an MCP server?
Yes. meetergo publishes an MCP server at @meetergo/mcp-server that exposes nine scheduling tools over the Model Context Protocol. An AI agent can find available slots, book a meeting, reschedule it, cancel it and read the calendar — using a meetergo Personal Access Token.
Can an AI agent actually book a meeting?
Yes. book_appointment creates a real appointment and sends the real invitations. Four of the nine tools change something — book, reschedule, cancel and add guests — and each is flagged as a write, so your MCP client can ask a human before it acts.
Which tools does the meetergo MCP server provide?
Nine: list_meeting_types, get_availability, book_appointment, reschedule_appointment, cancel_appointment, list_appointments, get_todays_appointments, add_guests and list_calendar_connections. The full meetergo API has 100 endpoints; the MCP surface is curated so an agent picks the right tool reliably.
How do I connect Claude or Cursor to meetergo?
Create a Personal Access Token in meetergo, then add the server to your MCP client config with the command npx -y @meetergo/mcp-server and MEETERGO_TOKEN set to your token. It runs over stdio, so it works with Claude Desktop, Claude Code, Cursor and any other MCP client.
Where is the data hosted, and is it GDPR compliant?
meetergo runs on servers in Germany with no US parent company, under real GDPR liability rather than a self-certification. That matters here because an agent with calendar access reads attendee names, email addresses and meeting subjects.
Is the meetergo MCP server open source?
Yes. It is MIT licensed at github.com/meetergo/meetergo-mcp-server and published on npm as @meetergo/mcp-server. You can read all nine tools before granting an agent access to your calendar, open an issue, or run your own fork against the same API.
Does the MCP server cost extra?
No. The MCP server is free and open source. It uses the meetergo API, which is available on paid plans — a Personal Access Token requires Essentials or above.