What environment variables are required?
`REDIS_URL` is required for session management. `NODE_ENV` (default "development") and `LOG_LEVEL` (default "info") are optional.
@Meeting-Baas
Basic information
An MCP server to deliver context to the MeetingBaaS chat
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
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.
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.
listCategoriesdocHelpAssistant to prefix assistant messages with a documentation helper label`REDIS_URL` is required for session management. `NODE_ENV` (default "development") and `LOG_LEVEL` (default "info") are optional.
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"}`.
All documentation is fetched from `https://docs.meetingbaas.com/llms/` with categorized endpoints like `/all`, `/api`, `/meetings`, etc.
Requires Redis, enabled Fluid compute, and max duration set to 800 in `vercel.json` (Pro/Enterprise accounts).
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.

Exact, shared memory for AI agents: a hierarchical database where totals always add up, every write is attributed to the agent and person behind it, and any figure traces back to its source file. Agents create databases,
Local MCP server and CLI that keeps a Git-versioned, model-written index of a codebase and its database schema, so coding agents start each task with the whole system in view.

Orcha is a unified context layer for AI tools and agents. It stores and indexes and exposes organizational, team, or individual knowledge. Files, structured databases, and connected sources live in one workspace, and age
Shared, serverless, conflict-free memory for AI agents: a multi-machine drop-in for the MCP memory knowledge graph.

Personal context for every AI: search, read, and write back to your private Markdown library of articles, threads, PDFs, notes, and captured ChatGPT/Claude/Gemini/Grok conversations. Remote server, OAuth 2.1 paste-and-au
Comments