Cap vs Rampify: Spec-Driven Development
Cap lists no tools and runs locally and Rampify: Spec-Driven Development lists no tools.
| Fact | Capio.github.cap-js/mcp-server | Rampify: Spec-Driven Developmentio.github.rampify-dev/rampify-vscode |
|---|---|---|
| Score | Not checked yet | Not checked yet |
| Status | Not checked yet | Not checked yet |
| Tools | 0 | 0 |
| Can write data | No tools listed | No tools listed |
| Runs | Local | Not known |
| Needs first | Node.js | – |
| Licence | APACHE-2.0 | MIT |
| Latest version | 0.1.0 | 0.11.0 |
| Known advisories | 0 | Not checked yet |
| Works in | Claude Desktop, Claude Code, Cursor, VS Code, Devin Desktop, Zed, Cline, Continue, Goose, LM Studio, Gemini CLI, Codex, mcp-client-cli, oterm, TUUI, BoltAI, Agenvoy, Amp, AnythingLLM, Augment Code, Bob Shell, ECA, Kiro, Kiro CLI | No install config |
| Downloads last week | Not known | Not known |
| Install | Install Cap | Install Rampify: Spec-Driven Development |
Scores and status come with our own checks, which have not run on these servers yet. The rest is from the publishers' registry entries, package registries and advisory databases.
Compare Cap with othersCompare Rampify: Spec-Driven Development with others