Ext Ops Panel
Open dashboard
Comparison

reaper-mcp-server vs Speak AI

reaper-mcp-server is an MCP server published by bonfire-systems. Marketplaces we read that list it: 1 (PyPI (MCP servers)). Speak AI is an MCP server published by speakai. Marketplaces we read that list it: 3 (Official MCP Registry, Claude Code: claude-plugins-community, npm registry (MCP servers)). As of our marketplace pass on 2026-11-09. 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
Marketplacereaper-mcp-serverSpeak AI
PyPI (MCP servers) Listed
Version: 0.4.0
Downloads/month (PyPI): 6 243
Downloads/week (PyPI): 426
Forks (GitHub): 38
Stars (GitHub): 183
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.41.1
Downloads/month (npm): 4 341
Downloads/week (npm): 199
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 1.19.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 1.41.1
Downloads/month (npm): 4 341
Downloads/week (npm): 199
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

reaper-mcp-server vs Speak AI
Factreaper-mcp-serverSpeak AI
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)183 (better)0 (worse)
Forks (GitHub) (differs)38 (better)0 (worse)
Last release (differs)2026-10-26 (worse)2026-10-30 (better)
Where it runs (differs)On your machine (reaper-mcp-server)Remote server or your machine
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Parts of the bundle (differs)Not a bundle6
LicenceMITMIT
Repository (differs)github.com/bonfire-systems/reaper-mcpgithub.com/speakai/speakai-mcp
Changes in the last 7 days00
First seen (differs)2026-10-132026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 7 h ago, requires authentication

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

reaper-mcp-server

In its own words, on PyPI (MCP servers):

MCP server for controlling REAPER DAW with AI agents

Speak AI

In its own words, on Official MCP Registry:

Search recordings, summarize meetings, create clips, and automate workflows from your AI assistant.

How to run each

reaper-mcp-server

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Speak AI As a remote MCP server

Claude Code
claude mcp add --transport http speak-ai https://api.speakai.co/v1/mcp

Requires: SPEAK_API_KEY (secret)

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

Only Speak AI 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 reaper-mcp-server publish no settings it asks for, so we do not compare settings.

What it can do: reaper-mcp-server · What it can do: Speak AI · Compare two other plugins

Package data comes from the Python Package Index (pypi.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.

Where the data comes from: how the catalog is built