THIRI Chord Intelligence vs io.github.dreamrec/livepilot
THIRI Chord Intelligence is an MCP server published by thiri.ai. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.dreamrec/livepilot is an MCP server published by dreamrec. Marketplaces we read that list it: 3 (Official MCP Registry, npm registry (MCP servers), Community GitHub marketplaces). As of our marketplace pass on 2026-11-15. 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 |  THIRI Chord Intelligence |  io.github.dreamrec/livepilot |
|---|---|---|
| Official MCP Registry | Listed Version: 0.5.2 Downloads/month (npm): 264 Downloads/week (npm): 62 Forks (GitHub): 0 Stars (GitHub): 13 Not marked · First seen |
Listed Version: 1.31.0 Downloads/month (npm): 1 749 Downloads/week (npm): 619 Forks (GitHub): 22 Stars (GitHub): 96 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.31.0 Downloads/month (npm): 1 749 Downloads/week (npm): 619 Forks (GitHub): 22 Stars (GitHub): 96 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 | THIRI Chord Intelligence | io.github.dreamrec/livepilot |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 13 (worse) | 96 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 22 (better) |
| Last release (differs) | Not published | 2026-11-12 |
| Where it runs (differs) | Remote server (mcp.thiri.ai/mcp) | On your machine (livepilot) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Parts of the bundle (differs) | Not a bundle | 24 |
| Licence (differs) | Not stated | BSL-1.1 |
| Repository (differs) | github.com/bluesprince/thiri-mcp | github.com/dreamrec/livepilot |
| Changes in the last 7 days (differs) | 0 | 6 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 11 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
THIRI Chord Intelligence
Deterministic music theory for agents: analyze, voice, reharmonize, conduct — computed, not guessed
io.github.dreamrec/livepilot
Ableton Live 12: 474 tools, 57 domains, nested devices, native modulation, and audio analysis.
How to run each
THIRI Chord Intelligence As a remote MCP server
claude mcp add --transport http chord-intelligence https://mcp.thiri.ai/mcpRequires: THIRI_API_KEY (secret)
io.github.dreamrec/livepilot As a local MCP server: npm package
claude mcp add --transport stdio livepilot -- npx -y livepilotCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only THIRI Chord Intelligence 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 io.github.dreamrec/livepilot publish no settings it asks for, so we do not compare settings.
What it can do: THIRI Chord Intelligence · What it can do: io.github.dreamrec/livepilot · 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). Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.