Meeting BaaS API Documentation Server

What is Meeting BaaS API Documentation Server?

An MCP server that fetches and serves Meeting BaaS API documentation from https://docs.meetingbaas.com/llms/. It provides multiple tools to retrieve documentation by category, including API, SDK, Calendars, Meetings, Users, Webhooks, Transcript Seeker, and Speaking Bots docs.

How to use Meeting BaaS API Documentation Server?

Set environment variables REDIS_URL (required) and optionally NODE_ENV and LOG_LEVEL. Authenticate via headers (x-meeting-baas-api-key or others) or request body. Configure Vercel with Redis, Fluid compute, and max duration of 800. Then invoke any of the 16 documentation tools (e.g., listCategories, getAllDocs, getApiDocs) to retrieve documentation content.

Key features of Meeting BaaS API Documentation Server

• 12 category-specific documentation tools
• 4 general utility tools including a help assistant
• Fetches live docs from Meeting BaaS API website
• Supports multiple authentication methods (headers/body)
• Requires Redis for session management
• Configurable log levels and environment modes

Use cases of Meeting BaaS API Documentation Server

• Fetching API documentation for Meetings, Calendars, Users, or Webhooks
• Retrieving TypeScript SDK documentation (common, bots, calendars, webhooks)
• Getting all available documentation categories via listCategories
• Using docHelpAssistant to prefix assistant messages with a documentation helper label
• Building LLM-powered tools that need up-to-date Meeting BaaS API reference

FAQ from Meeting BaaS API Documentation Server

What environment variables are required?

REDIS_URL is required for session management. NODE_ENV (default "development") and LOG_LEVEL (default "info") are optional.

How do I authenticate with this server?

Authentication can be done via headers (x-meeting-baas-api-key, x-meetingbaas-apikey, x-api-key, or Authorization: Bearer <token>) or via POST body with {"apiKey": "your-api-key"}.

Where is the documentation data fetched from?

All documentation is fetched from https://docs.meetingbaas.com/llms/ with categorized endpoints like /all, /api, /meetings, etc.

What are the Vercel deployment requirements?

Requires Redis, enabled Fluid compute, and max duration set to 800 in vercel.json (Pro/Enterprise accounts).

What authentication methods are supported?

Four header-based methods (in order: x-meeting-baas-api-key, x-meetingbaas-apikey, x-api-key, Authorization Bearer token) plus a body-based method with an apiKey field.