Local vs Cloud - MeetGeek

Overview

MeetGeek offers two MCP server options. Both expose the same set of tools and meeting data — the difference is in how they run and how they authenticate.

Local MCP
Cloud MCP

The Local MCP server runs as a process on your own machine. Your MCP client (e.g. Claude Desktop, Cursor) spawns it on demand and communicates over stdio.Choose Local MCP if you:

Are a developer or technical user comfortable with Node.js
Want full control over the server process and its environment
Are using a desktop MCP client like Claude Desktop or Cursor
Prefer to authenticate with an API key rather than OAuth


Transport	stdio
Installation	Node.js package on your machine
Authentication	API key
Updates	Manual (`npm update`)
Supported clients	Claude Desktop, Cursor, any stdio MCP client

Get started with Local MCP →

The Cloud MCP server is hosted by MeetGeek. Your AI assistant connects to it over HTTPS using the Streamable HTTP transport. Nothing is installed on your machine.Choose Cloud MCP if you:

Want the simplest possible setup with nothing to install
Are using ChatGPT or Claude through their web or mobile interfaces
Prefer to authenticate with your existing MeetGeek account (Google or Microsoft)
Want automatic updates without managing a local package


Transport	HTTP Streamable
Installation	None
Authentication	OAuth via auth.meetgeek.ai
Updates	Automatic
Supported clients	ChatGPT, Claude (web/mobile), any HTTP MCP client

Get started with Cloud MCP →

Get Started

Local MCP

Cloud MCP

Documentation Index

​Overview

Overview