meetstream-ai-meeting-bot-api vs app.recordist/gateway
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). app.recordist/gateway is an MCP server published by recordist.app. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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 |  app.recordist/gateway |
|---|---|---|
| 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: 0.1.7 Downloads/month (npm): 1 395 Downloads/week (npm): 501 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 | app.recordist/gateway |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-13 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@recordist/gateway) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 0 |
| Parts of the bundle (differs) | 9 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/meetstream-ai/claude-plugin | github.com/recordist-app/gateway |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen | 2026-10-11 | 2026-10-11 |
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.
app.recordist/gateway
Read, search and act on meetings Recordist recorded on your Mac. Listens on loopback by default.
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-communityapp.recordist/gateway As a local MCP server: npm package
claude mcp add --transport stdio gateway -- npx -y @recordist/gatewayCommands 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
The marketplaces of meetstream-ai-meeting-bot-api publish no settings it asks for, so we do not compare settings.
What it can do: meetstream-ai-meeting-bot-api · What it can do: app.recordist/gateway · 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.