Meeting BaaS MCP server for AI agents

Meeting BaaS MCP Server provides tools for managing meeting data, including transcripts, recordings, calendar events, and search functionality through the Model Context Protocol (MCP). This service enables AI assistants like Claude to access meeting information, create recording bots, and search through meeting content.

Installation

To install the Meeting BaaS MCP server:

Clone the repository:
```
git clone <repository-url>
cd mcp-baas
```
Install dependencies:
```
npm install
```
Build the project:
```
npm run build
```

Claude Desktop Integration

Follow these steps to integrate Meeting BaaS with Claude Desktop:

Edit the Claude Desktop configuration file:

vim ~/Library/Application\ Support/Claude/claude_desktop_config.json

Add the Meeting BaaS configuration:

"meetingbaas": {
  "command": "/bin/bash",
  "args": [
    "-c",
    "cd /path/to/meeting-mcp && (npm run build 1>&2) && export MCP_FROM_CLAUDE=true && node dist/index.js"
  ],
  "headers": {
    "x-api-key": "YOUR_API_KEY"
  }
}

For calendar integration, add the calendarOAuth section to your botConfig:

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

Save the file and restart Claude Desktop.

Basic Usage

Start the server:

npm run start

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

Calendar Integration

Setting Up Calendar OAuth

Get OAuth guidance:

"I want to integrate my Google Calendar. How do I get OAuth credentials?"

List available calendars:

"List my Google calendars with these credentials:
- Client ID: my-client-id-123456789.apps.googleusercontent.com
- Client Secret: my-client-secret-ABCDEF123456
- Refresh Token: my-refresh-token-ABCDEF123456789"

Set up integration:

"Integrate my Google Calendar with:
- 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]"

Managing Calendar Events

View upcoming meetings:

"Show my upcoming meetings from calendar 1a2b3c4d-5e6f-7a8b-9c0d-1e2f3a4b5c6d"

Schedule recording for a meeting:

"Schedule recording for event 7a8b9c0d-1e2f-3a4b-5c6d-7e8f9a0b1c2d with:
- Bot name: Team Meeting Bot
- Recording mode: gallery_view
- Entry message: Hello everyone, I'm here to record"

Cancel a scheduled recording:

"Cancel the recording for event 7a8b9c0d-1e2f-3a4b-5c6d-7e8f9a0b1c2d"

Force calendar refresh:
```
"Resync all my connected calendars"
```

Recording Meetings

Creating Meeting Bots

Create a bot for an immediate meeting:

"Create a bot for my Zoom meeting at https://zoom.us/j/123456789"

Configure bot appearance and behavior:

"Join my Teams meeting at https://teams.microsoft.com/l/meetup-join/123 with:
- Bot name: Meeting Recorder
- Bot image: https://example.com/avatar.jpg
- Entry message: Hi everyone, I'll be recording this meeting"

Check recording status:

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

Accessing Meeting Content

Get transcript:

"Get the transcript from my team meeting with bot ID abc-123"

Find key moments:

"Identify key moments from my product planning meeting with bot ID xyz-456"

Share specific moments:

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

QR Code Integration

Generate custom QR codes that can be used as bot avatars:

"Generate a QR code with:
- Type: email
- To: [email protected]
- Prompt: Create a professional QR code with blue abstract patterns
- Style: style_crystal"

You can then use the generated QR code URL as a bot image when creating a meeting bot.

Accessing Recordings

Meeting recordings can be accessed through the Meeting BaaS viewer:

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

For example:

https://meetingbaas.com/viewer/67738f48-2360-4f9e-a999-275a74208ff5

The viewer provides:

Video recording
Synchronized transcript with speaker identification
Navigation by speaker or topic
Direct link sharing with teammates

Cursor Integration

To use with Cursor:

Open Cursor
Go to Settings → Model Context Protocol
Add a server with:
- Name: "Meeting BaaS MCP"
- Type: "sse"
- Server URL: "http://localhost:7017/mcp"
- Add any required authentication headers

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.