Introduction
Get started with Model Context Protocol servers for Meeting BaaS
We provide optimized documentation for both LLMs and recent MCP server updates. For more on our LLM integration, see LLMs and for MCP access, visit auth.meetingbaas.com.
What is Model Context Protocol?
Model Context Protocol (MCP) is a standard that lets AI assistants like Claude connect with other services. For Meeting BaaS, an MCP server helps with:
-
Meeting transcripts and analysis
-
Meeting scheduling
-
AI assistance during meetings
-
Secure connections
-
Enterprise-ready infrastructure
Learn more about Model Context Protocol in Anthropic's technical overview.
Deployment Options
Meeting BaaS offers two robust MCP server implementations to match your specific needs:
MCP on Vercel
A serverless solution optimized for Vercel deployment, offering:
- Zero infrastructure management
- Automatic scaling
- Global edge deployment
- Simplified CI/CD integration
Meeting MCP
A self-hosted solution providing:
- Complete infrastructure control
- Custom deployment options
- Enhanced security configurations
- Local development flexibility
Key Capabilities
Both MCP servers provide access to Meeting BaaS capabilities through standardized tools:
Getting Started
Prerequisites
The following requirements must be met before setting up an MCP server:
Development Tools
- Node.js v16.x or later
- npm or yarn package manager
- Git for version control
- Docker for local development
- VS Code or your preferred IDE
Account Access
- Meeting BaaS account
- Valid API credentials
- Access to deployment platform
Setup Instructions
Follow these steps to get your MCP server up and running:
- Sign up at meetingbaas.com
- Navigate to API section in dashboard
- Generate new API key
- Store credentials securely
Choose your deployment type and set up the codebase:
# Clone repository
git clone https://github.com/meetingbaas/mcp-vercel # For Vercel
# OR
git clone https://github.com/meetingbaas/meeting-mcp # For self-hosted
# Install and configure
cd <repository-name>
npm install
cp .env.example .envFor extended functionality, both deployment options fully support the Meeting BaaS TypeScript SDK.
