BrandBrain Flow Orchestrator vs Hermoso
BrandBrain Flow Orchestrator is an MCP server published by brandbrain.dev. Marketplaces we read that list it: 1 (Official MCP Registry). Hermoso is an MCP server published by hermoso-ai. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-14. 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 |  BrandBrain Flow Orchestrator |  Hermoso |
|---|---|---|
| Official MCP Registry | Listed Version: 0.4.0 Downloads/month (npm): 232 Downloads/week (npm): 59 Not marked · First seen |
Listed Version: 0.1.539 Downloads/month (npm): 17 432 Downloads/week (npm): 11 518 Forks (GitHub): 0 Stars (GitHub): 7 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.1.539 Downloads/month (npm): 17 432 Downloads/week (npm): 11 518 Forks (GitHub): 0 Stars (GitHub): 7 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 | BrandBrain Flow Orchestrator | Hermoso |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 7 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | Not published | 2026-11-14 |
| Where it runs (differs) | On your machine (brandbrain-flow-orchestrator-mcp) | Remote server or your machine |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 1 | 2, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/skunkworq/brandbrain | github.com/hermoso-ai/hermoso |
| Changes in the last 7 days (differs) | 0 | 20 or more |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 17 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
BrandBrain Flow Orchestrator
Compose BrandBrain asset flows, run mock/live generation, and fetch outputs
Hermoso
AI marketing agent and AI ad generator: 1233 tools, usable alone. No model markup on Starter and up.
How to run each
BrandBrain Flow Orchestrator As a local MCP server: npm package
claude mcp add --env "BRANDBRAIN_FLOW_MCP_BEARER_TOKEN=<YOUR_BRANDBRAIN_FLOW_MCP_BEARER_TOKEN>" --transport stdio flow-orchestrator -- npx -y brandbrain-flow-orchestrator-mcpRequires: BRANDBRAIN_FLOW_MCP_BEARER_TOKEN (secret)
Hermoso
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: HERMOSO_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Hermoso 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
Only BrandBrain Flow Orchestrator asks for
BRANDBRAIN_API_URLBRANDBRAIN_APP_URLBRANDBRAIN_FLOW_MCP_BEARER_TOKEN (secret)BRANDBRAIN_MAX_PROVIDER_SPEND_USD_MICROS
Only Hermoso asks for
HERMOSO_API_BASEHERMOSO_TOKEN (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: BrandBrain Flow Orchestrator · What it can do: Hermoso · 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.