Homespun vs Rebase
Homespun is an MCP server published by homespun.dev. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). Rebase is an MCP server published by rebasepro. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-28. 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 |  Homespun |  Rebase |
|---|---|---|
| Official MCP Registry | Listed Version: 1.6.98 Downloads/month (npm): 2 442 Downloads/week (npm): 453 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.25.1 Downloads/month (npm): 1 231 Downloads/week (npm): 142 Forks (GitHub): 1 Stars (GitHub): 23 Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 1.6.99 Downloads/month (npm): 2 442 Downloads/week (npm): 453 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.25.1 Downloads/month (npm): 1 231 Downloads/week (npm): 142 Forks (GitHub): 1 Stars (GitHub): 23 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 | Homespun | Rebase |
|---|---|---|
| Marketplaces that list it | 2 | 2 |
| Stars (GitHub) (differs) | 1 (worse) | 23 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 1 (better) |
| Last release (differs) | 2026-10-20 (better) | 2026-10-15 (worse) |
| Where it runs (differs) | Remote server or your machine | On your machine (@rebasepro/mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 2 | 4, secrets among them: 1 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/homespunapps/homespun | github.com/rebasepro/rebase |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 5 days 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
Homespun
Deploy a multi-user web app from your agent: hosting, auth, database, and permissions.
Rebase
Schema, database, document, user and dev-server tools for a Rebase backend project.
How to run each
Homespun As a remote MCP server
claude mcp add --transport http homespun https://homespun.dev/mcpRequires: HOMESPUN_API_KEY (secret), HOMESPUN_REGISTER_SECRET (secret)
Rebase As a local MCP server: npm package
claude mcp add --env "REBASE_API_TOKEN=<YOUR_REBASE_API_TOKEN>" --transport stdio rebase -- npx -y @rebasepro/mcpRequires: REBASE_API_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Homespun has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of Rebase nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
Only Homespun asks for
HOMESPUN_AGENT_NAMEHOMESPUN_API_KEY (secret)HOMESPUN_REGISTER_SECRET (secret)HOMESPUN_URL
Only Rebase asks for
REBASE_API_TOKEN (secret)REBASE_BASE_URLREBASE_MCP_ALLOW_REMOTE_WRITESREBASE_PROJECT_DIR
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Homespun · What it can do: Rebase · 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). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.