Speaking Bots MCP Server

Created By
Meeting-Baasa year ago
An MCP server that can send speaking bots inside meetings
Overview

What is Speaking Bots MCP?

Speaking Bots MCP is an open-source server that enables the deployment of AI-powered speaking agents in video meetings using the MeetingBaas API. It allows users to connect voice bots to platforms like Google Meet, Zoom, and Microsoft Teams, offering customizable personas and real-time audio streaming.

How to use Speaking Bots MCP?

To use Speaking Bots MCP, clone the repository, install the necessary dependencies, set your environment variables, and run the server locally or deploy it on platforms like Docker or Vercel. You can join meetings as a speaking bot by making API calls to the provided endpoints.

Key features of Speaking Bots MCP?

  • Join meetings as AI speaking bots with customizable personas and voices.
  • Real-time bidirectional audio streaming.
  • Minimalist and extensible API design for easy customization.
  • Support for multiple video conferencing platforms.

Use cases of Speaking Bots MCP?

  1. Enhancing virtual meetings with AI-driven speaking agents.
  2. Providing real-time assistance and information during video calls.
  3. Customizing bot personas for different meeting contexts.

FAQ from Speaking Bots MCP?

  • Can I customize the voice and persona of the speaking bot?

Yes! You can create unique personas with different voices and characteristics.

  • Is the API free to use?

Yes! The API is open-source and free to use.

  • What platforms does it support?

It supports Google Meet, Zoom, and Microsoft Teams.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Meeting-Baas
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Gpt Scrambler

2 days ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

2 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago