BrewPage vs fmrl
BrewPage is a plugin bundle for AI coding tools published by kochetkov-ma. Marketplaces we read that list it: 1 (Community GitHub marketplaces). fmrl is an MCP server published by toogreatwtf. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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 |  BrewPage |  fmrl |
|---|---|---|
| Community marketplace davepoon/buildwithclaude | Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.17.8 Forks (GitHub): 0 Stars (GitHub): 1 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 | BrewPage | fmrl |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 1 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-11-09 |
| Where it runs (differs) | Remote server (brewpage.app/mcp) | On your machine (fmrl-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 4, secrets among them: 2 |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/kochetkov-ma/brewpage-publish-plugins | github.com/toogreatwtf/fmrl-plugin |
| Changes in the last 7 days (differs) | 2 | 6 |
| First seen | 2026-11-08 | 2026-11-08 |
| Endpoint at the last check (differs) | Status out of date: last check 34 h ago returned HTTP 405 | 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
BrewPage
Publish HTML, Markdown, files and multi-file static sites from Claude Code to BrewPage and get an HTTPS link back, with no account or API key: a brewpage-publish skill plus the BrewPage remote MCP server (https://brewpage.app/mcp). Only content you ask it to publish is uploaded; links are unlisted but readable by anyone who has them (optional password), and content expires (15 days by default, 30 at most).
fmrl
Your agent's outbox. Ask it to publish to fmrl and get a shareable link, no account required.
How to run each
BrewPage As a Claude Code plugin
/plugin marketplace add davepoon/buildwithclaude
/plugin install brewpage@buildwithclaudefmrl As a local MCP server: npm package
claude mcp add --env "FMRL_API_KEY=<YOUR_FMRL_API_KEY>" --env "FMRL_RING=<YOUR_FMRL_RING>" --transport stdio fmrl-mcp -- npx -y fmrl-mcpRequires: FMRL_API_KEY (secret), FMRL_RING (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only BrewPage has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of fmrl nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
The marketplaces of BrewPage publish no settings it asks for, so we do not compare settings.
What it can do: BrewPage · What it can do: fmrl · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.