Authentication - MeetGeek

API key

The Local MCP server authenticates using your MeetGeek API key. This key is passed as an environment variable — it is never stored on disk by the server itself.

Obtaining your API key

Log in to app.meetgeek.ai
Go to Integrations → Public API
Generate a new API key and copy it

API keys are region-specific. Make sure the key matches the region you intend to use (api.meetgeek.ai, api-eu.meetgeek.ai, or api-us.meetgeek.ai).

Passing the key to the server

Set the MEETGEEK_API_KEY environment variable in your MCP client configuration:

{
  "env": {
    "MEETGEEK_API_KEY": "<YOUR_MEETGEEEK_API_KEY>"
  }
}

Alternatively, you can export it in your shell profile and reference it from there — but setting it directly in the client config is recommended to avoid accidental exposure.

Scopes

The Local MCP server uses the same permissions as the REST API key. It can access all resources that are visible to the authenticated user, including meetings, transcripts, summaries, highlights, and team data.