StreamElements MCP Server and API by Cotlet vs Discord MCP
StreamElements MCP Server and API by Cotlet is an MCP server published by cotlet.dev. Marketplaces we read that list it: 1 (Official MCP Registry). Discord MCP is an MCP server published by cappyeo. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-11. 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 |   StreamElements MCP Server and API by Cotlet |  Discord MCP |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.2 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.34.0 Downloads/month (npm): 1 377 Downloads/week (npm): 227 Forks (GitHub): 22 Stars (GitHub): 187 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.34.0 Downloads/month (npm): 1 377 Downloads/week (npm): 227 Forks (GitHub): 22 Stars (GitHub): 187 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 | StreamElements MCP Server and API by Cotlet | Discord MCP |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 187 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 22 (better) |
| Last release (differs) | 2026-11-10 (better) | 2026-11-09 (worse) |
| Where it runs (differs) | Remote server (cotlet.dev/mcp/v1/streamelements/connect) | On your machine (@discord-mcp/cli) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 1 |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | github.com/cotlet-connect/streamelements-mcp | github.com/cappyeo/discord-mcp |
| Changes in the last 7 days (differs) | 7 | 3 |
| First seen (differs) | 2026-11-09 | 2026-10-11 |
| Endpoint at the last check (differs) | Answered with HTTP 302 (6 h ago) | no remote endpoint we check |
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
StreamElements MCP Server and API by Cotlet
StreamElements live streamer tools MCP server: list chat commands, edit command, edit timer.
Discord MCP
Caller-owned Discord operations for AI agents with 222 typed tools and verifiable guild builds.
How to run each
StreamElements MCP Server and API by Cotlet As a remote MCP server
claude mcp add --transport http streamelements https://cotlet.dev/mcp/v1/streamelements/connectDiscord MCP As a local MCP server: npm package
claude mcp add --env "DISCORD_TOKEN=<YOUR_DISCORD_TOKEN>" --transport stdio discord-mcp -- npx -y @discord-mcp/cliRequires: DISCORD_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only StreamElements MCP Server and API by Cotlet 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
The marketplaces of StreamElements MCP Server and API by Cotlet publish no settings it asks for, so we do not compare settings.
What it can do: StreamElements MCP Server and API by Cotlet · What it can do: Discord MCP · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.