CLI for Agents vs Raven
CLI for Agents is a plugin bundle for AI coding tools published by Eric Zakariasson. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). Raven is an MCP server published by ravenmcp.ai. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-23. 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 |  Raven | |
|---|---|---|
| Cursor: cursor/plugins | Listed Version: 1.0.0 Forks (GitHub): 1 353 Stars (GitHub): 13 601 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.6.0 Downloads/month (npm): 1 717 Downloads/week (npm): 127 Forks (GitHub): 0 Stars (GitHub): 6 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 2.6.0 Downloads/month (npm): 1 717 Downloads/week (npm): 127 Forks (GitHub): 0 Stars (GitHub): 6 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 | CLI for Agents | Raven |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 13 601 (better) | 6 (worse) |
| Forks (GitHub) (differs) | 1 353 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Apache-2.0 |
| Repository (differs) | github.com/cursor/plugins | github.com/rhinocap/raven-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 6 days ago |
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
CLI for Agents
Patterns for designing CLIs that coding agents can run reliably: flags, help with examples, pipelines, errors, idempotency, dry-run.
Raven
Design intelligence for coding agents: audits, design systems, and a taste profile agents consult.
How to run each
CLI for Agents
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Raven As a remote MCP server
claude mcp add --transport http raven-mcp https://mcp.ravenmcp.ai/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Raven 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
Neither one's marketplaces publish the settings it asks for.
What it can do: CLI for Agents · What it can do: Raven · Compare two other plugins
Data comes from the public marketplace file https://github.com/cursor/plugins/blob/HEAD/.cursor-plugin/marketplace.json. 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.