Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Build and operate declarative REST/Kafka services on Orion: 58 tools over the full admin API.
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.
ORION_SERVER_URL, ORION_API_KEYValues marked secret are keys to your account. Never share them or paste them into a chat.
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": {
"orion": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"ORION_SERVER_URL",
"-e",
"ORION_API_KEY",
"ghcr.io/goplasmatic/orion-cli:1.1.0",
"mcp",
"serve"
],
"env": {
"ORION_SERVER_URL": "your-value",
"ORION_API_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add orion --env ORION_SERVER_URL=your-value --env ORION_API_KEY=your-value -- docker run -i --rm -e ORION_SERVER_URL -e ORION_API_KEY ghcr.io/goplasmatic/orion-cli:1.1.0 mcp serveFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"orion": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"ORION_SERVER_URL",
"-e",
"ORION_API_KEY",
"ghcr.io/goplasmatic/orion-cli:1.1.0",
"mcp",
"serve"
],
"env": {
"ORION_SERVER_URL": "your-value",
"ORION_API_KEY": "your-value"
}
}
}
}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": {
"orion": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"ORION_SERVER_URL",
"-e",
"ORION_API_KEY",
"ghcr.io/goplasmatic/orion-cli:1.1.0",
"mcp",
"serve"
],
"env": {
"ORION_SERVER_URL": "your-value",
"ORION_API_KEY": "your-value"
}
}
}
}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 GoPlasmatic, 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.
You need to fill in: ORION_SERVER_URL, ORION_API_KEY
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 (1.1.0) reached the registry 3 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, EmbeddedCI BenchPod
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.
Drive a BenchPod hardware-in-the-loop bench: power, flash, UART, I2C, CAN, analog and logic.
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.
Build services at AI speed on a consistent, governed foundation.
Define the business logic in JSON. Orion supplies the runtime around it.
Orion is a declarative services runtime. An Orion service consists of a workflow and a channel, with optional connectors to external systems. Post those definitions, activate them, and the service is live—without writing an application server, building a container for each service, or restarting the runtime.
Orion consistently handles the surrounding infrastructure: routing, ingress guards, rate limits, timeouts, retries, circuit breakers, connection pooling, version rollout, rollback, metrics, and tracing. Definitions can be written by a developer or proposed by an AI assistant; they follow the same draft, test, activation, and audit path.
[!NOTE]
Orion is designed for request- and event-shaped work expressible as ordered
task functions and JSONLogic. It is not a general-purpose application runtime
or a durable workflow engine. See When Orion fits before
choosing it for a project.
This tested path uses Docker, curl, and a POSIX-compatible shell. It starts a local Orion instance, deploys an order-processing workflow and channel, and calls the resulting API.
docker run --name orion-quickstart -d -p 8080:8080 \
ghcr.io/goplasmatic/orion:latest
curl --retry 10 --retry-delay 1 --retry-connrefused \ http://localhost:8080/healthz
curl -fsSLo /tmp/orion-quickstart.sh \
https://raw.githubusercontent.com/GoPlasmatic/Orion/main/examples/quickstart.sh less /tmp/orion-quickstart.sh bash /tmp/orion-quickstart.sh
The script makes four administration calls: it creates and activates a workflow, then creates and activates its channel. It finishes with a test request and is safe to run again. From a cloned repository, run ./examples/quickstart.sh instead.
curl -fsS -X POST http://localhost:8080/api/v1/data/orders \
-H 'Content-Type: application/json' \ -d '{ "data": { "order_id": "ORD-0001", "total": 12500 } }'
The response contains the parsed order with "flagged": true. The workflow holds the business logic; the channel exposes it at POST /orders. Routing, validation, tracing, and lifecycle management are supplied by Orion.
For expected output, troubleshooting, Windows-friendly installation paths, and cleanup instructions, follow the complete quickstart.
flowchart LR
Request["HTTP request, Kafka record, or schedule"] --> Channel Channel["Channel route + ingress policy"] --> Workflow Workflow["Workflow ordered business logic"] --> Connector Connector["Connector external system"] Workflow --> Response["Response or stored trace"]
| Primitive | Purpose | Example |
|---|---|---|
| Channel | Receives traffic and applies ingress policy | POST /orders, Kafka topic, 0 15 2 * * * order.placed |
| Workflow | Runs the business logic as an ordered task pipeline | Parse → validate → enrich → respond |
| Connector | Provides a reusable connection to an external system | PostgreSQL, Redis, Kafka, REST API |
The definitions belonging to one service can be shipped together as a package. One Orion instance can run many packages side by side, each with its own lifecycle and rollout.
How Orion works explains request execution, composition, deployment topology, and extension boundaries in one page.
channel_call, while preserving the callee's guards and preventing cycles.Choose a focused path in What are you building?, or deploy a tested package from examples/packages/.
| Area | Included capability |
|---|---|
| Traffic | REST, plain HTTP, synchronous and asynchronous channels, Kafka ingress, cron schedules |
| Safety | Payload validation, API-key/HMAC/JWT channel auth, rate limiting, backpressure, CORS controls |
| Resilience | Timeouts, retries, circuit breakers, idempotency, response caching, dead-letter handling |
| Delivery | Drafts, immutable versions, dry-runs, percentage rollout, rollback, packages, WebAssembly plugins, ONNX models admitted before they serve |
| Observability | Health and readiness endpoints, Prometheus metrics, structured logs, OpenTelemetry traces |
| Data | PostgreSQL, MySQL, SQLite, MongoDB, Elasticsearch, Redis, Kafka, HTTP, SMTP, S3-compatible storage |
| Operations | Embedded SQLite for one node; PostgreSQL/MySQL and Redis for clustered replicas |
Configuration is explicit, and several production controls are permissive or disabled for local development. In particular, data channels are open unless they declare authentication or sit behind an authenticating proxy. Before exposing an instance, work through the production checklist.
flowchart LR
Author --> Draft --> Validate --> DryRun["Dry-run"] --> Activate --> Rollout --> Observe Observe -->|problem| Rollback
Workflow, channel, and connector definitions use the same governed lifecycle regardless of who authored them. A draft serves no traffic. You can validate and dry-run it, approve the exact version, activate it without restarting the server, roll traffic out by percentage, and return to a previous immutable version. Administrative changes are recorded in the audit log.
For AI-assisted authoring, install the Orion agent skill or use the self-contained prompt pack. The Claude Code tutorial walks through a complete assisted workflow.
Orion fits services whose work starts with an HTTP request or Kafka record, completes as a bounded pipeline, and can be expressed with Orion's task functions and JSONLogic. It is especially useful when many small services need the same operational and governance foundation.
Choose another runtime, or pair one with Orion, when:
Read Is Orion right for you? for detailed comparisons with durable execution engines, API gateways, automation platforms, rule engines, and embedded dataflow-rs.
The current workspace release is 1.12.0 and requires Rust 1.98 when built from source. The server and CLI are released in lockstep; use matching versions.
# Homebrew: macOS Apple Silicon and Linux
brew install GoPlasmatic/tap/orion-server brew install GoPlasmatic/tap/orion-cli
cargo install --git https://github.com/GoPlasmatic/Orion --locked orion-server
cargo install --git https://github.com/GoPlasmatic/Orion --locked \ orion-server orion-cli
Release installers are also available for Linux, macOS Apple Silicon, and Windows. See Install & Run for every method, platform support, startup, and verification.
Useful local commands:
orion-server validate-config -c config.toml
orion-server fmt ./definitions orion-server lint workflow.json orion-server clippy ./definitions orion-server dry-run -w workflow.json -i input.json orion-server test examples/workflow-tests orion-server compile ./definitions -o package.json orion-server package apply -s http://localhost:8080 -f package.json
The server command reference and Orion CLI reference list all commands and flags.
The published Orion 1.0.0 benchmark measured 5.1K–5.7K workflow requests per second on one Apple M2 Pro instance, with single-digit-millisecond average latency across the recorded workflow scenarios. These are release- and workload-specific results, not capacity guarantees. Review the benchmark record for hardware, scenarios, tail latency, cluster results, and reproduction steps.
The full manual is at [docs.goplasmatic.io](https://docs.goplasmatic.io/).
| Goal | Start here |
|---|---|
| Try Orion | Quickstart |
| Understand the model | How Orion works |
| Build a complete service | Orders API golden path |
| Find an exact schema | Reference index |
| Deploy and operate | Operate Orion |
| Secure production | Production checklist |
| Upgrade safely | Upgrades |
| Check compatibility | Support & compatibility |
The documentation source lives in docs/src/. Edit that directory, not the generated docs/book/ output. See docs/STYLE_GUIDE.md for its structure and editorial conventions.
orion-cli](crates/orioOnly the beginning is shown; read the rest in the repo