Ext Ops Panel
Open dashboard
Comparison

tsm vs Speak AI

tsm is a plugin bundle for AI coding tools published by lu-zhengda. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Speak AI is an MCP server published by speakai. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). 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

Where each is published
MarketplacetsmSpeak AI
Claude Code: claude-plugins-community Listed
Version: 0.6.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.19.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Official MCP Registry Not listed Listed
Version: 1.38.2
Downloads/month (npm): 4 063
Downloads/week (npm): 1 641
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

tsm vs Speak AI
FacttsmSpeak AI
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub)00
Forks (GitHub)00
Last release (differs)Not published2026-10-16
Where it runs (differs)Installs as a plugin bundleRemote 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)16
LicenceMITMIT
Repository (differs)github.com/lu-zhengda/tsmgithub.com/speakai/speakai-mcp
Changes in the last 7 days (differs)06
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 days ago, requires a key

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

tsm

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

Manage Transmission BitTorrent client from Claude Code. Add torrents, monitor downloads, set per-file priorities, apply seeding policies by label, bulk-replace trackers, and automate torrent workflows, all through natural language. Supports JSON output for scripting, macOS Keychain auth, multi-server profiles, and advanced filtering (e.g., "ratio>2.0 AND label:movies AND age<7d").

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

tsm As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install tsm@claude-community

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 tsm publish no settings it asks for, so we do not compare settings.

What it can do: tsm · What it can do: Speak AI · 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