MCP server: let an AI agent run your scheduling

The meetergo MCP server connects an AI assistant directly to your meetergo account. Once it is connected, you can ask your assistant to check when you are free, book a meeting, reschedule one, add a contact, or set up your whole website assistant, and it does the work in your account.

MCP (Model Context Protocol) is the standard that lets AI clients talk to outside tools. Claude, ChatGPT, Cursor and a growing number of other apps speak it.

Available on every plan, including Free. You only need a Personal Access Token.

What you need

A Personal Access Token. Create one at my.meetergo.com/integrations; it starts with rgo-. See Personal Access Token (API Key) if you have not made one before.

Treat the token like a password. Anyone holding it can act in your account. When you create it, give it only the capability groups the assistant actually needs, and delete it when you stop using it.

Connect

Hosted (recommended)

Point your MCP client at:

https://mcp.meetergo.com/mcp

and send your token as a bearer credential. The /mcp path is part of the address; the domain on its own will not work.

In Claude Code, one command does it:

claude mcp add meetergo --transport http https://mcp.meetergo.com/mcp \
  --header "Authorization: Bearer rgo-YOUR_TOKEN"

In apps with a connector dialog (Claude Desktop, ChatGPT, Cursor), paste the URL and add the header Authorization: Bearer rgo-YOUR_TOKEN.

Claude Desktop, one click

Download meetergo.mcpb from the latest release and open it. Claude Desktop installs it and asks for your token in a dialog, so there is no configuration file to edit.

Run it yourself

If you would rather run the server on your own machine, it is on npm:

{
  "mcpServers": {
    "meetergo": {
      "command": "npx",
      "args": ["-y", "@meetergo/mcp-server"],
      "env": { "MEETERGO_TOKEN": "rgo-your_token_here" }
    }
  }
}

Set up your whole account with one prompt

The server ships a guided flow called onboard. In a client that supports MCP prompts it appears as "meetergo: onboard"; otherwise just ask your assistant to set up meetergo and give it your website address.

The flow:

Looks at what your account already has, so nothing is built twice.
Reads your website and proposes a setup: meeting types, qualification questions, and your Mira website assistant with instructions grounded in your own pages.
Stops and waits for your approval. Nothing is written before you say yes.
Builds what you approved, with the website chat still switched off.
Proves it works by sending scripted visitors through your own assistant and showing you the transcripts.
Gives you the embed snippet and, once you are happy, switches it live.

There is a second prompt, weekly-review, that reports what visitors asked, which questions your assistant could not answer, and helps you fill those gaps.

What your assistant can do

Around 56 tools, grouped roughly as:

Scheduling — availability, book, reschedule, cancel, list appointments, add guests
Meeting types — create and edit, one-time booking links, booking page settings
Contacts — create, update, search, bulk import
Website assistant (Mira) — crawl your site into its knowledge base, write its instructions, build qualification forms, run a test drive, check the widget is installed
Routing forms and webhooks

Anything that changes or deletes something is marked as such, so your client asks you before it happens rather than doing it quietly.

When a plan limit gets in the way

If your plan's allowance for something runs out, the server says which limit you hit and links to the upgrade page instead of returning a bare error. Connecting is never limited by your plan, and your assistant is told not to bring up upgrading unless something you asked for is actually blocked.

Troubleshooting

"MEETERGO_TOKEN is not set" — the token did not reach the server. In a config file, check it is inside the env block; with the hosted endpoint, check the Authorization header reads Bearer rgo-….

401 Unauthorized — the token is wrong, was deleted, or you pasted it with a space. Create a fresh one at my.meetergo.com/integrations.

A tool says a capability is missing — your token was scoped without that group. Create a new token including it.

The test drive says it is rate-limited — it runs several real conversations, so it is capped at a few runs per hour. Your saved setup is unaffected; try again later.

Source and issues

The server is open source at github.com/meetergo/meetergo-mcp-server and published as @meetergo/mcp-server.