meetgeek

This MCP server provides a bridge between MCP clients (like Claude Desktop, Cursor, or other MCP-enabled assistants) and MeetGeek. It exposes MCP functions to retrieve meetings, fetch detailed meeting metadata, obtain transcripts with speaker labels and timestamps, generate AI-powered highlights and summaries, list team-specific meetings, and upload recordings via a download URL. By configuring your MCP client to point at this server, your AI tools can request data and actions from MeetGeek through a consistent MCP interface.

Once you have the server running and your MCP client configured, you can call functions such as meetings (list meetings with pagination), meetingDetails (get comprehensive metadata for a meeting), transcript (retrieve the full transcription), highlights (AI-generated key moments), summary (actionable meeting summaries), teamMeetings (meetings filtered by team), and uploadRecording (import a recording via a URL). These capabilities enable your AI assistants to answer questions like “Show my recent meetings,” “What were the key moments in meeting ABC123?” and “Upload this recording to MeetGeek.”

Prerequisites:

• Node.js v14 or higher and npm installed on your system
• Access to run npm install and build processes
• MeetGeek API key with the necessary permissions to read meetings, transcripts, and related data

Installation steps:

1. Clone the repository: git clone <repository-url> cd meetgeek-mcp-server

2. Install dependencies: npm install

3. Build the server (if applicable): npm run build

4. Run the server locally to verify: node index.js

5. Configure your MCP client using the provided example configuration, ensuring you replace absolute paths and API keys with your own values. The server expects an environment containing MEETGEEK_API_KEY and MEETGEEK_BASE_URL for API access.

Tips and considerations:

• Ensure the MCP client uses an absolute path to the built server file (as required by configurations in Claude Desktop and similar clients).
• Keep your MEETGEEK_API_KEY secure; do not commit it to public repositories.
• If you modify the server, remember to restart your MCP client to pick up changes.
• Common issues include incorrect absolute paths, invalid API keys, and missing dependencies. Check server logs for details when troubleshooting.
• The provided configuration examples show the standard pattern; adapt the path and environment variables to your environment as needed.