hum vs Flow Music MCP Server by useapi.net (third-party)
hum is an MCP server published by anzal1. Marketplaces we read that list it: 1 (Official MCP Registry). Flow Music MCP Server by useapi.net (third-party) is an MCP server published by useapi.net. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.0.1 No figure published 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 | hum | Flow Music MCP Server by useapi.net (third-party) |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release (differs) | Not published | 2026-10-18 |
| Where it runs (differs) | On your machine (https://github.com/anzal1/hum/releases/download/v0.2.1/hum.mcpb) | Remote server (api.useapi.net/v1/flowmusic/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/anzal1/hum | Not stated |
| Changes in the last 7 days (differs) | 0 | 3 |
| First seen (differs) | 2026-10-11 | 2026-10-16 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
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
hum
Free music for your coding agent. Play songs, mood stations and Spotify links in your browser.
Flow Music MCP Server by useapi.net (third-party)
Google Flow Music (Lyria): songs, lyrics, extend, cover, remix, effects, stems
How to run each
hum
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Flow Music MCP Server by useapi.net (third-party) As a remote MCP server
claude mcp add --transport http flowmusic https://api.useapi.net/v1/flowmusic/mcp --header "Authorization: Bearer <YOUR_API_TOKEN>"
Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
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 Flow Music MCP Server by useapi.net (third-party) publish no settings it asks for, so we do not compare settings.
What it can do: hum · What it can do: Flow Music MCP Server by useapi.net (third-party) · Compare two other plugins
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.