meetergo MCP server

meetergo MCP server

Lets an AI agent actually run a calendar: find slots, book, reschedule, cancel, review what is coming up, and keep the contact record straight.

Not to be confused with the docs MCP server at https://developer.meetergo.com/mcp, which searches documentation and cannot change anything. Both are useful and they do different jobs:

Setup

Create a Personal Access Token at my.meetergo.com/integrations — it looks like rgo-… — then either point your client at the hosted server or run this package locally over stdio. The token works on every plan, including Free.

Hosted

https://mcp.meetergo.com/mcp

Streamable HTTP, authenticated with Authorization: Bearer rgo-…. The path matters: mcp.meetergo.com alone is not the endpoint. For clients that take a remote URL and headers:

{
  "mcpServers": {
    "meetergo": {
      "url": "https://mcp.meetergo.com/mcp",
      "headers": { "Authorization": "Bearer rgo-your_token_here" }
    }
  }
}

Local (npx)

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

Works with Claude Desktop, Claude Code, Cursor, or anything else that speaks MCP.

Scope the token

When you create the token you can limit it to the capabilities the agent actually needs (scheduling, contacts and deals, Mira, forms, account). A limited token is refused on everything outside those groups, including reads, so give it every group whose tools you intend to use — a Mira-only token cannot book, and a scheduling-only token cannot read your knowledge base.

Signing in instead of pasting a token

OAuth sign-in is live on the hosted endpoint. Discovery is published at /.well-known/oauth-protected-resource (RFC 9728), so a capable client can start the flow from the MCP URL. Clients are pre-registered rather than created through dynamic client registration. For a Claude custom connector, enter the public client id mcp-claude under Advanced settings and leave the client secret blank. The directory clients for Claude and ChatGPT are configured with their respective providers.

Cursor and Grok Bot

This repository includes the Cursor Marketplace plugin used by both Cursor and Grok Bot. Install meetergo from Settings, Plugins, Marketplace, then finish the browser sign-in. The plugin connects to the hosted endpoint and uses the public PKCE client id mcp-cursor; there is no client secret or token to paste.

For local review before the marketplace listing is published, load this repository as a local Cursor plugin. Its .cursor-plugin/plugin.json manifest points at mcp.json, which contains the same hosted URL and OAuth client id.

A Personal Access Token works in every MCP client, on every plan including Free. That is what the rest of this page assumes.

Acting for another user

A Personal Access Token always acts as its owner. To run an agent across a whole company — an assistant booking on behalf of several colleagues — use a Platform API Key (ak_live::) and name the target user:

"env": {
  "MEETERGO_TOKEN": "ak_live:...",
  "MEETERGO_USER_ID": "the-user-uuid"
}

The two token types have opposite requirements, and the server checks both at startup rather than letting you find out mid-booking:

acting user on nearly every route;

• a Platform API Key must have MEETERGOUSERID — the API demands an

API rejects the header outright.

• a Personal Access Token must not — it always acts as its owner, and the

Shortened. The full README is on GitHub.