Orion CLI

Create, test, and deploy workflows. Define channels as service endpoints. Send data through channels. Monitor engine health and metrics. Use as a CLI or as an MCP server for Claude Desktop, Cursor, and other AI tools.

brew install GoPlasmatic/tap/orion-cli # or: curl installer, Docker (see Install)

orion-cli config set-server http://localhost:8080

Orion Server v0.2.0 Status: OK Uptime: 2h 30m Components: database OK engine OK

4. Create a workflow and channel, test it, send data:

# Create a workflow from a JSON file orion-cli workflows create -f high-value-order.json # Activate it orion-cli workflows activate <WORKFLOW_ID> # Create a channel that links to the workflow orion-cli channels create -d '{"name":"orders","channel_type":"sync","protocol":"http","workflow_id":"<WORKFLOW_ID>"}' orion-cli channels activate <CHANNEL_ID> # Reload the engine to pick up changes orion-cli engine reload # Dry-run test with sample data orion-cli workflows test <WORKFLOW_ID> -d '{"data":{"order_id":"ORD-9182","total":25000}}' --trace # Send real data through the channel orion-cli send orders -d '{"order_id":"ORD-9182","total":25000}'

--server <URL> Orion server URL (overrides config; env: ORION_SERVER_URL) --output <FORMAT> Output format: table, json, yaml (default: table) --quiet Suppress output, print only IDs or minimal info --verbose Show full response bodies and extra details --no-color Disable colored output (env: NO_COLOR) --yes Skip confirmation prompts

# List workflows with filters orion-cli workflows list --status active --tag fraud # Get full workflow details orion-cli workflows get <ID> # Create from file or inline JSON orion-cli workflows create -f workflow.json orion-cli workflows create -d '{"name":"My Workflow",...}' # Create with a custom ID orion-cli workflows create --id my-custom-id -f workflow.json # Update a workflow (version auto-increments) orion-cli workflows update <ID> -f updated-workflow.json # Change workflow status orion-cli workflows activate <ID> orion-cli workflows archive <ID> # Control rollout percentage orion-cli workflows rollout <ID> -p 50 # Delete (with confirmation prompt) orion-cli workflows delete <ID>

Test any workflow against sample data before activating — with a full execution trace:

orion-cli workflows test <ID> -d '{"data":{"order_id":"ORD-9182","total":25000}}' --trace

Result: MATCHED Trace: parse executed flag executed Output: { "order": { "order_id": "ORD-9182", "total": 25000, "flagged": true, "alert": "High-value order: $25000" } }

Supports input from file (-f), inline JSON (-d), or stdin (--stdin).

GitOps-ready workflows for CI/CD pipelines:

# Export workflows (with optional filters) orion-cli workflows export --status active > workflows.json # Import workflows from file orion-cli workflows import -f workflows.json # Validate the import on the server without applying (reports would_create/would_fail) orion-cli workflows import -f workflows.json --dry-run # Compare local file against server state orion-cli workflows diff -f workflows.json

The diff command shows color-coded changes:+new,~modified,=unchanged,-deleted.

Channels are service endpoints that receive data and route it to workflows:

# List channels orion-cli channels list --status active --protocol rest # Create a channel orion-cli channels create -d '{"name":"orders","channel_type":"sync","protocol":"rest","route_pattern":"/orders/{id}","workflow_id":"process-orders"}' # Activate / Archive orion-cli channels activate <ID> orion-cli channels archive <ID> # Version management orion-cli channels versions <ID> orion-cli channels new-version <ID> # Bulk import (server-side validation with --dry-run) orion-cli channels import -f channels.json --dry-run orion-cli channels import -f channels.json

orion-cli connectors list orion-cli connectors get <ID> orion-cli connectors create -f connector.json orion-cli connectors update <ID> -f connector.json orion-cli connectors delete <ID> orion-cli connectors enable <ID> orion-cli connectors disable <ID> # Circuit breaker management orion-cli connectors circuit-breakers orion-cli connectors reset-breaker <KEY> # Bulk import (server-side validation with --dry-run) orion-cli connectors import -f connectors.json --dry-run orion-cli connectors import -f connectors.json

orion-cli send orders -d '{"order_id":"ORD-001","amount":150}' # Include a server-side execution profile (timing breakdown by phase/handler). # Requires tracing.debug_profile_enabled on the server. orion-cli send orders -d '{"order_id":"ORD-001","amount":150}' --profile

# Fire and forget — returns trace_id orion-cli send orders --async-mode -d '{"amount":100}' # Submit and wait for completion orion-cli send orders --async-mode --wait --timeout 30 -d '{"amount":100}'

# Check trace status orion-cli traces get <TRACE_ID> # Poll until complete (with timeout) orion-cli traces wait <TRACE_ID> --interval 2 --timeout 60

Exit codes:0completed,1failed,2timeout.

# View engine status — version, uptime, workflow counts, channels orion-cli engine status # Hot-reload workflows and channels (zero downtime) orion-cli engine reload

Inspect the workflow task functions registered in the engine, with their input schemas:

# List functions (table view) orion-cli functions list # Full input schemas as JSON orion-cli --output json functions list

Stdio Transport (Claude Desktop / Cursor)

orion-cli mcp serve --server http://localhost:8080

orion-cli mcp serve --http --server http://localhost:8080 orion-cli mcp serve --http --bind 0.0.0.0:9090 --server http://localhost:8080

Add to~/Library/Application Support/Claude/claude_desktop_config.json:

cargo build # Build cargo test # Run tests cargo clippy # Lint cargo fmt # Format

This is a web browser that enables your coding agent, such as Claude Code, to visit websites on your behalf and assist you in identifying bugs or creating UI test cases.

Create crafted UI components inspired by the best 21st.dev design engineers.

Bring agent evaluations, observability, and synthetic test set generation directly into your IDE for free with Galileo's new MCP server

An MCP server to help AI assistants to answer questions and generate AccelByte Extend SDK code more effectively .

MCP server for AI Diagram Maker — generate beautiful software engineering diagrams directly inside Cursor, Claude Desktop, Claude Code, or any MCP-compatible AI agent

ALAPI MCP Tools,Call hundreds of API interfaces via MCP

AI-powered SVG animation generator that transforms static files into animated SVG components using the Allyson platform

MCP server that gives AI assistants on-demand access to 1,500+ amCharts docs, ~300 code examples, and 1000+ class API references.

APIMatic MCP Server is used to validate OpenAPI specifications using APIMatic. The server processes OpenAPI files and returns validation summaries by leveraging APIMatic’s API.

One shared context layer for AI agents and humans — live API specs, DB schemas, and versioned contracts across repos so every agent and teammate works from the same source of truth.