Meeting BaaS MCP server

Automates meeting management across Zoom, Google Meet, and Microsoft Teams with tools for recording, transcribing, searching, and sharing meeting content without manual note-taking.
Back to servers
Provider
Meeting BaaS
Release date
Mar 08, 2025
Language
TypeScript
Stats
11 stars

The Meeting BaaS MCP server provides a powerful platform for managing meeting data, including automated transcriptions, recordings, calendar integrations, and searchable meeting content through the Model Context Protocol (MCP).

Installation

To install the Meeting BaaS MCP server:

  1. Clone the repository:

    git clone <repository-url>
    cd mcp-baas
    
  2. Install dependencies:

    npm install
    
  3. Build the project:

    npm run build
    

Usage

Start the server with:

npm run start

By default, the server runs on port 7017 and exposes the MCP endpoint at http://localhost:7017/mcp.

Available Tools

Calendar Tools

  • oauthGuidance: Get step-by-step instructions for OAuth setup
  • listRawCalendars: View available calendars before integration
  • setupCalendarOAuth: Integrate a calendar using OAuth
  • listCalendars: View all integrated calendars
  • getCalendar: Get details about a specific calendar
  • deleteCalendar: Remove a calendar integration
  • resyncAllCalendars: Force refresh of connected calendars
  • listUpcomingMeetings: View upcoming meetings
  • listEvents: Search and filter calendar events
  • getEvent: View details about a specific event
  • scheduleRecording: Set up automated recording for a meeting
  • cancelRecording: Cancel a scheduled recording
  • checkCalendarIntegration: Diagnose calendar connection issues

Meeting Tools

  • createBot: Create a meeting bot to join a video conference

    Parameters include meeting_url, name, botImage, entryMessage, etc.
    
  • getBots: List all bots and their meetings

  • getBotsByMeeting: Find bots for a specific meeting

  • getRecording: Get recording information

  • getRecordingStatus: Check recording progress

  • getMeetingData: Get transcript and recording data

Transcript Tools

  • getMeetingTranscript: Get a complete meeting transcript with speaker names
  • findKeyMoments: Automatically identify important meeting moments

QR Code Tools

  • generateQRCode: Create an AI-generated QR code as a bot avatar

Link Sharing Tools

  • shareableMeetingLink: Generate a formatted link to a meeting recording
  • shareMeetingSegments: Create links to multiple moments in a meeting

Example Workflows

Recording a Meeting

  1. Create a bot for your meeting:

    "Create a bot for my Zoom meeting at https://zoom.us/j/123456789"
    
  2. The bot automatically joins and starts recording.

  3. Check recording status:

    "What's the status of my meeting recording for the Zoom call I started earlier?"
    

Calendar Integration

  1. Get OAuth setup guidance:

    "I want to integrate my Google Calendar. How do I get OAuth credentials?"
    
  2. List your available calendars:

    "List my available Google calendars. Here are my OAuth credentials:
    - Client ID: my-client-id-123456789.apps.googleusercontent.com
    - Client Secret: my-client-secret-ABCDEF123456
    - Refresh Token: my-refresh-token-ABCDEF123456789"
    
  3. Set up calendar integration:

    "Integrate my Google Calendar using these credentials:
    - Platform: Google
    - Client ID: my-client-id-123456789.apps.googleusercontent.com
    - Client Secret: my-client-secret-ABCDEF123456
    - Refresh Token: my-refresh-token-ABCDEF123456789
    - Raw Calendar ID: [email protected]"
    
  4. Schedule recording for an upcoming meeting:

    "Schedule a recording for my team meeting with event ID 7a8b9c0d-1e2f-3a4b-5c6d-7e8f9a0b1c2d"
    

Simplified Calendar Integration

You can directly configure your calendar OAuth in the Claude Desktop configuration file:

"botConfig": {
  "calendarOAuth": {
    "platform": "Google",
    "clientId": "YOUR_OAUTH_CLIENT_ID",
    "clientSecret": "YOUR_OAUTH_CLIENT_SECRET", 
    "refreshToken": "YOUR_REFRESH_TOKEN",
    "rawCalendarId": "[email protected]"
  }
}

Analyzing Meeting Content

  1. Get a meeting transcript:

    "Get the transcript from my team meeting with bot ID abc-123"
    
  2. Find key moments:

    "Identify key moments from yesterday's product planning meeting with bot ID xyz-456"
    
  3. Share a specific moment:

    "Create a shareable link to the part of meeting abc-123 at timestamp 12:45 where John was talking about the budget"
    

Integration with Claude Desktop

  1. Edit the Claude Desktop configuration file:

    vim ~/Library/Application\ Support/Claude/claude_desktop_config.json
    
  2. Add the Meeting BaaS MCP server configuration:

    {
      "mcpServers": {
        "meetingbaas": {
          "command": "/bin/bash",
          "args": [
            "-c",
            "cd /path/to/meeting-mcp && (npm run build 1>&2) && MCP_FROM_CLAUDE=true node dist/index.js"
          ],
          "headers": {
            "x-api-key": "YOUR_API_KEY_FOR_MEETING_BAAS"
          },
          "botConfig": {
            "name": "Meeting Assistant",
            "image": "https://meetingbaas.com/static/972043b7d604bca0d4b0048c7dd67ad2/fc752/previewFeatures.avif",
            "entryMessage": "Hello, I'm a bot from Meeting Baas. I'll be taking notes for this meeting."
          }
        }
      }
    }
    
  3. Restart Claude Desktop.

Integration with Cursor

  1. Open Cursor
  2. Go to Settings > Model Context Protocol
  3. Add a new server with:
    • Name: "Meeting BaaS MCP"
    • Type: "sse"
    • Server URL: "http://localhost:7017/mcp"
    • Add any required headers

Accessing Meeting Recordings

Recordings can be accessed through the Meeting BaaS viewer:

https://meetingbaas.com/viewer/{BOT_ID}

All recordings are automatically shared with colleagues who have the same corporate email domain for streamlined team collaboration.

How to add this MCP server to Cursor

There are two ways to add an MCP server to Cursor. The most common way is to add the server globally in the ~/.cursor/mcp.json file so that it is available in all of your projects.

If you only need the server in a single project, you can add it to the project instead by creating or adding it to the .cursor/mcp.json file.

Adding an MCP server to Cursor globally

To add a global MCP server go to Cursor Settings > MCP and click "Add new global MCP server".

When you click that button the ~/.cursor/mcp.json file will be opened and you can add your server like this:

{
    "mcpServers": {
        "cursor-rules-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "cursor-rules-mcp"
            ]
        }
    }
}

Adding an MCP server to a project

To add an MCP server to a project you can create a new .cursor/mcp.json file or add it to the existing one. This will look exactly the same as the global MCP server example above.

How to use the MCP server

Once the server is installed, you might need to head back to Settings > MCP and click the refresh button.

The Cursor agent will then be able to see the available tools the added MCP server has available and will call them when it needs to.

You can also explictly ask the agent to use the tool by mentioning the tool name and describing what the function does.

Want to 10x your AI skills?

Get a free account and learn to code + market your apps using AI (with or without vibes!).

Nah, maybe later