meetstream-ai-meeting-bot-api vs Chamade
meetstream-ai-meeting-bot-api is a plugin bundle for AI coding tools published by meetstream-ai. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Chamade is an MCP server published by chamade.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  meetstream-ai-meeting-bot-api |  Chamade |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 2.2.3 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 5.1.0 Downloads/month (npm): 395 Downloads/week (npm): 57 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | meetstream-ai-meeting-bot-api | Chamade |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp.chamade.io/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 9 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/meetstream-ai/claude-plugin | github.com/chamade-io/mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
meetstream-ai-meeting-bot-api
Build meeting bot integrations without writing boilerplate. MeetStream lets developers programmatically join, record, transcribe, and stream Zoom, Google Meet, and Microsoft Teams meetings via a REST API. This plugin gives Claude full knowledge of the MeetStream API - bot lifecycle, transcription providers, real-time WebSocket streaming, calendar automation, and webhook handling - so it generates complete, production-ready code tailored to your use case.
Chamade
Voice and chat for AI agents — Discord, Teams, Meet, Slack, Zoom, Telegram, WhatsApp, NC Talk, SIP
How to run each
meetstream-ai-meeting-bot-api As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install meetstream-ai-meeting-bot-api@claude-communityChamade As a remote MCP server
claude mcp add --transport http chamade https://mcp.chamade.io/mcp/ --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: meetstream-ai-meeting-bot-api · What it can do: Chamade · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.