Official MCP Server for MeetGeek API

🚀 Self-hosted open source MeetGeek MCP

This open source MCP implementation lets AI tools such as Claude or Cursor access your MeetGeek meetings. Get meeting transcripts, insights, and analytics through a simple interface. Check the docs below or refer to our user guide.

If you’re looking for the MeetGeek public MCP implementation please check this guide instead

.

Features

• List Meetings: Retrieve all meetings with pagination support
• Get Meeting Details: Fetch comprehensive metadata for any specific meeting
• Get Meeting Transcripts: Access full transcriptions with speaker identification and timestamps
• Get Meeting Highlights: Retrieve AI-generated key moments and insights
• Get Meeting Summaries: Access AI-powered meeting summaries and action items
• Team Meetings: Retrieve meetings for specific teams with filtering capabilities
• Upload Recordings: Import meeting recordings directly via download URLs

Prerequisites

• MeetGeek Account: A valid MeetGeek account with API access
• MeetGeek API Key: You need an API key from your MeetGeek account settings
• Node.js & npm: Node.js (v14 or higher) and npm installed on your system
• MCP-Compatible Client: An MCP client like Claude Desktop, Cursor, or similar

Installation and Configuration

This MCP server runs locally using Node.js. Follow these steps to set up and configure it with your MCP client.

Local Installation

1. Clone or download this repository:

   git clone 
   cd meetgeek-mcp-server
   

2. Install dependencies:

   npm install
   

3. Build the server:

   npm run build
   

Configure Your MCP Client

Update your MCP client’s configuration file to include the MeetGeek server.

For Claude Desktop

Update your claude_desktop_config.json file (typically located in ~/Library/Application Support/Claude/ on macOS or %APPDATA%\Claude\ on Windows):

{
  "mcpServers": {
    "MeetGeek": {
      "command": "node",
      "args": ["/absolute/path/to/your/meetgeek-mcp-server/dist/index.js"],
      "env": {
        "MEETGEEK_API_KEY": "your_meetgeek_api_key_here",
        "MEETGEEK_BASE_URL": "https://api.meetgeek.ai"
      }
    }
  }
}

For Other MCP Clients

Refer to your specific MCP client’s documentation for configuration details. The general pattern is:

{
  "mcpServers": {
    "MeetGeek": {
      "command": "node",
      "args": ["/absolute/path/to/MeetGeek-mcp-server/dist/index.js"],
      "env": {
        "MEETGEEK_API_KEY": "your_meetgeek_api_key_here",
        "MEETGEEK_BASE_URL": "https://api.meetgeek.ai"