Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Build, validate and simulate reliability block diagrams (RAM analysis) from an AI assistant.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"raptor-studio": {
"command": "uvx",
"args": [
"raptor-studio-mcp"
]
}
}
}Run this in your terminal
claude mcp add raptor-studio -- uvx raptor-studio-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"raptor-studio": {
"command": "uvx",
"args": [
"raptor-studio-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"raptor-studio": {
"type": "stdio",
"command": "uvx",
"args": [
"raptor-studio-mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account openpowershift, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.9.0) reached the registry 4 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Python MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Local-only Python MCP server for the Files.com API.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
An open-source reliability block diagram (RBD) simulator for Windows, macOS and Linux. Draw a diagram of parts that can fail and be repaired, run thousands of simulated futures, and read availability, reliability, maintenance, spares and cost numbers like an engineer, then find out which part to spend money on.
RAPTOR Studio carries on from Raptor 7, the simulator written at ARINC and released as open source by Booz Allen Hamilton. Its simulation engine was ported from Raptor 7's own source and checked, event by event, against what Raptor 7 itself writes, so the numbers are the ones reliability engineers already trust. Models made in Raptor 7 open here. Around that engine is a new application, a command line, and an AI-assistant server.
Like Raptor 7, it is released under the Booz Allen Public License (BAPL). Anyone may use, modify and share it, but a commercial entity may use it only for its internal business and for services to government and non-profit organisations, and nobody may charge a fee for it without Booz Allen Hamilton's permission. See Licence & credits.
raptor estimate times a few runs and tells you how long a full batch will take before you start it.pip install, on Windows, macOS and Linux.raptor run, sweep, compare, diff, estimate, validate, spf, fev, step, extract, analytic, render and more) with machine-readable results. It fits in a continuous-integration job, a Jupyter notebook or a shell loop.ping) lets an assistant build, edit, validate, simulate, compare and explain models, run long batches in the background, and draw the diagram. The MCP server reference covers install, client setup and every tool, resource and prompt. The recording below is a real run of those tools (the numbers are the engine's; the assistant's narration is scripted):.rbds is one JSON document with friendly field names, and raptor diff (or File ▸ Differences) says in words what changed between two versions of a model. .rbd files open and save exactly as before.Availability says how good the system is. Importance says which block to improve. Switch on Run ▸ Analysis ▸ Importance measures (or raptor run --importance both, or importance on the MCP simulate tool) and RAPTOR Studio re-simulates the model with each block in turn made unable to fail, and with it dead, then ranks every block by how much the system moves. You get:
The equations are on the Formulas page, and the tutorial's weak-link chapter works through an example.
| Importance measures | Rank blocks by Birnbaum, RAW, RRW and Vesely–Fussell importance, with sampling error, a results tab and a canvas overlay. |
| Parallel batches | Runs spread over your cores (-j N on the command line); results are reproducible for a given core count, and one core reproduces Raptor 7's own random sequence exactly. |
| Run-time estimate | Know how long a batch will take before you start it, in the app, on the command line and from an assistant. |
| Check part of a model | Run one hierarchy on its own, with its input assumed available, or save it as a standalone model (raptor extract). The results are labelled as isolated. |
| Parameter sweeps and comparisons | Vary any field over a list of values, or run two or more models side by side, from the application, the command line or an assistant. Differences shows what is different between two models, and runs nothing. |
| AI assistant (MCP) | 66 tools (67 including ping) to build, edit, run, analyse and explain models, over stdio or authenticated HTTP. |
| Stepping debugger | Step a run event by event, pause on a condition, jump to the next run, and see what each step changed. Failure Effects View and the Single Point Failure file are also available headless. |
| Several models at once | Each model opens in its own window with its own undo history and results. |
| Edit while looking at results | Results stay on screen while you edit; undo and redo for edits; spread-banded Weak Link, Cost, Capacity, Spares and Importance colourings. |
| Block labels and rates | Choose what the lines under each block show (mean, standard deviation, rate); keep the derivation of a failure rate in a named, reusable Rate. |
| Reports | Results export as PDF, HTML, AsciiDoc, spreadsheet, CSV or JSON (a versioned schema). |
| Diagram | Light and dark themes, dockable panels, annotations, mini-map, key tips on the commands that have one, and a diagram renderer for documents (raptor render). |
| Safer files | Validation catches the model shapes that crash Raptor 7 on open (a node's declared path count, a stale phase header) before you save them. |
Grab the installer for your platform from the Releases page:
| File | Platform | Install |
|---|---|---|
raptor-studio-*-windows-setup.exe | Windows 10/11 (x64) | Double-click, follow the wizard |
raptor-studio-*-windows-portable.zip | Windows 10/11 (x64) | Unzip anywhere, run raptor-studio.exe |
raptor-studio-*-macos-arm64.dmg | macOS 13+ (Apple Silicon) | Open the DMG, drag RAPTOR Studio to Applications |
raptor-studio-*-macos-x64.dmg | macOS 13+ (Intel) | Open the DMG, drag RAPTOR Studio to Applications |
raptor-studio-*-linux-amd64.deb | Debian/Ubuntu (x64) | Double-click or sudo apt install ./…deb |
raptor-studio-*-linux-x86_64.AppImage | Most Linux distros (x64) | chmod +x the file, then run it |
Verify the checksums against SHA256SUMS.txt in the same release. The installers carry the desktop application only; the raptor command line and the MCP server come with the pip package (below).
File types: the Windows installer, macOS app and .deb register .rbds and .rbd so a double-click opens the model in RAPTOR Studio. On a machine with Raptor 7, .rbd keeps opening Raptor 7 by default and RAPTOR Studio is added under "Open with". The AppImage cannot register file types system-wide; run raptor-studio model.rbds or use File → Open.
macOS note (unsigned build): Gatekeeper will ask for confirmation. Right-click RAPTOR Studio → Open → Open, or run xattr -cr "/Applications/RAPTOR Studio.app" once in Terminal.
Windows note (unsigned build): SmartScreen may show "Windows protected your PC" — click More info → Run anyway.
pip install raptor-studio # the application and command line
pip install "raptor-studio[mcp]" # plus the MCP server for AI assistants
or, isolated from your system Python:
pipx install "raptor-studio[mcp]"
For the assistant server alone, uvx raptor-studio-mcp --workspace ~/raptor-models runs it without an install step.
Then run raptor-studio for the application, raptor --help for the command line, or raptor-studio-mcp for the assistant server. pip puts these three commands in the environment's bin folder (Scripts on Windows), so in a virtual environment either activate it first (source .venv/bin/activate, or .venv\Scripts\activate on Windows) or give the full path, such as `
Only the beginning is shown; read the rest in the repo