harvis.dev vs io.github.przemekzur/breezedeploy
harvis.dev is an MCP server published by harvis.dev. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.przemekzur/breezedeploy is an MCP server published by przemekzur. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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 |  harvis.dev | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 0.4.0 Downloads/month (npm): 174 Downloads/week (npm): 39 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 | harvis.dev | io.github.przemekzur/breezedeploy |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (harvis.dev/api/mcp) | On your machine (breezedeploy-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/przemekzur/hosting |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 3 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
harvis.dev
Deploy static sites from AI agents: deploy_site publishes files and returns a live URL in seconds.
io.github.przemekzur/breezedeploy
Deploy a local folder, git repo, or Docker image to a live HTTPS URL from your AI chat.
How to run each
harvis.dev As a remote MCP server
claude mcp add --transport http harvis https://harvis.dev/api/mcpio.github.przemekzur/breezedeploy As a local MCP server: npm package
claude mcp add --env "CONTROL_PLANE_API_KEY=<YOUR_CONTROL_PLANE_API_KEY>" --transport stdio breezedeploy -- npx -y breezedeploy-mcpRequires: CONTROL_PLANE_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only harvis.dev 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 harvis.dev publish no settings it asks for, so we do not compare settings.
What it can do: harvis.dev · What it can do: io.github.przemekzur/breezedeploy · 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.