Ext Ops Panel
Open dashboard
Comparison

meetstream-ai-meeting-bot-api vs ai.waystation/teams

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). ai.waystation/teams is an MCP server published by waystation.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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

Where each is published
Marketplacemeetstream-ai-meeting-bot-apiai.waystation/teams
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.3.1
Forks (GitHub): 19
Stars (GitHub): 65
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

meetstream-ai-meeting-bot-api vs ai.waystation/teams
Factmeetstream-ai-meeting-bot-apiai.waystation/teams
Marketplaces that list it11
Stars (GitHub) (differs)1 (worse)65 (better)
Forks (GitHub) (differs)0 (worse)19 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (waystation.ai/teams/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)9Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/meetstream-ai/claude-plugingithub.com/waystation-ai/mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 402 (5 days ago)

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

In its own words, on Claude Code: claude-plugins-community:

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.

ai.waystation/teams

In its own words, on Official MCP Registry:

Collaborate, chat, and manage meetings in Microsoft Teams.

How to run each

meetstream-ai-meeting-bot-api As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install meetstream-ai-meeting-bot-api@claude-community

ai.waystation/teams As a remote MCP server

Claude Code
claude mcp add --transport http teams https://waystation.ai/teams/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only ai.waystation/teams has a remote endpoint we check. How we check endpoints

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: ai.waystation/teams · 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.

Where the data comes from: how the catalog is built