This is the main MCP (Model Context Protocol) server powering chat.meetingbaas.com , providing the LLM integration and AI capabilities for the Meeting BaaS chat interface. It's built on the Vercel MCP template with Meeting BaaS-specific modifications.

Key Features

• Meeting BaaS SDK Integration: Complete integration with the official Meeting BaaS SDK for managing meetings, bots, and calendars

• Fluid Compute: Optimized for Vercel's Fluid compute functionality for efficient execution and scaling

• Redis Session Management: Uses Redis for reliable session management and state persistence

• Flexible Authentication: Multiple authentication methods including headers, request body, and environment variables

SDK Integration

This project uses the official Meeting BaaS SDK (

@meeting-baas/sdk

) which provides:

• Complete type safety with comprehensive TypeScript definitions

• Automatic updates synced with OpenAPI specification

• Simplified access to all meeting automation capabilities

• Cross-platform consistency for all supported meeting providers

• Pre-generated MPC tools for easy integration with AI systems

Environment Setup

Required environment variables:

REDIS_URL=redis://username:password@host:port

Optional variables

NODE_ENV=development

LOG_LEVEL=info

BAAS_API_KEY=your-api-key # Development only

The server supports multiple ways to provide the Meeting BaaS API key:

• Request headers:

  • x-meeting-baas-api-key

  • x-meetingbaas-apikey

  • x-api-key

  • Authorization

(as a Bearer token)

• Request body: For POST requests with

{"apiKey": "your-api-key"}

• Environment variable:

BAAS_API_KEY

(development mode only)

Related MCP Implementations

• meeting-mcp: The main MCP server for managing meeting data, including transcripts, recordings, and calendar events.

• mcp-on-vercel-documentation: MCP server specifically for fetching and serving Meeting BaaS API documentation.