Meeting BaaS MCP Server

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 a fork of the Vercel MCP template with Meeting BaaS-specific modifications.

Note: This fork can be deployed on a traditional server. To deploy on Vercel, you must recreate a vercel.json file.

The server implements the Model Context Protocol (MCP) that integrates with Meeting BaaS services, enabling:

• AI-powered chat interactions
• Meeting automation through LLMs
• Intelligent bot management
• Calendar integration with AI assistance

Features

• Integration with Meeting BaaS SDK for video meeting management
• Calendar integration for automated meeting recordings
• Real-time transcription and audio streaming capabilities
• Comprehensive bot management tools

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 (Google Meet, Zoom, Microsoft Teams)
• Pre-generated MPC tools for easy integration with AI systems
• Strongly typed functions for interacting with the complete Meeting BaaS API

Environment Variables

The following environment variables are required:

• REDIS_URL: URL to your Redis instance (required for session management)

Optional environment variables:

• NODE_ENV: Set to "development" to enable development mode.
• PORT: Port the server listens on (default: 3000).
• BAAS_API_KEY: Meeting BaaS API key (development mode only).

Authentication

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

1. Request headers (in order of precedence):

   • x-meeting-baas-api-key
   • x-meetingbaas-apikey
   • x-api-key
   • Authorization (as a Bearer token)

2. Request body (for POST requests):

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

3. Environment variable (development mode only):

   BAAS_API_KEY=your-api-key

Note: In production, the API key should be provided through request headers or body. The environment variable is only used in development mode for testing purposes.

Usage

Update api/server.ts with your tools, prompts, and resources following the MCP TypeScript SDK documentation.

There is also a Next.js version of this template

Notes for running on Vercel

• Requires a Redis attached to the project under process.env.REDIS_URL
• Make sure you have Fluid compute enabled for efficient execution
• After enabling Fluid compute, create a vercel.json and set maxDuration to 800 if you are using a Vercel Pro or Enterprise account.
• An example of vercel.json:

{
  "rewrites": [{ "source": "/(.+)", "destination": "/api/server" }],
  "functions": {
    "api/server.ts": {
      "maxDuration": 800
    }
  }
}

• Deploy the MCP template

Meeting BaaS Integration

This fork includes several Meeting BaaS-specific tools:

Meeting Management

• Join meetings with AI bots
• Record meetings with transcription
• Leave meetings and clean up resources

Calendar Management

• Create and manage calendar integrations
• Schedule automated recordings
• List and manage calendar events
• Update calendar configurations

Bot Management

• List and monitor active bots
• Get detailed bot metadata
• Manage bot configurations

Sample Client

script/test-client.mjs contains a sample client to try invocations.

node scripts/test-client.mjs https://mcp-on-vercel.vercel.app

Differences from Original Template

This fork adds:

1. Meeting BaaS SDK integration
2. Enhanced bot management capabilities
3. Calendar integration features
4. Improved error handling and logging

Contributing

This is a fork of the Vercel MCP template. For the original template, please visit vercel-labs/mcp-on-vercel.

Documentation

For more information about the Meeting BaaS SDK, visit:

• SDK Documentation
• npm Package
• GitHub Repository