Install

Five local-first ways in. Local workflows run offline; there is no telemetry or background network activity. Outbound source HTTP is denied by default.

Claude Desktop (.mcpb bundle)

Download aurora-agent.mcpb from the GitHub releases (v0.1.1) and double-click it, or add it via Settings → Extensions. The bundle ships with the reference fixtures; the “AURORA data root” setting can point at a full checkout.

The prebuilt bundle is Windows-only. On macOS or Linux, build from source (below) and register the binary with your MCP client directly.

Release integrity — the v0.1.1 bundle's SHA-256:

e987c396a01eb2ae812efa8226f6892fc3f70cb441102217476990816458f025

Claude Code (plugin marketplace)

The repository is itself a Claude Code plugin marketplace:

claude plugin marketplace add AURORA-NEURO/aurora-agent
claude plugin install aurora-agent@aurora

VS Code (extension)

Sideload aurora-agent-0.1.3.vsix from the v0.1.3 release:

code --install-extension aurora-agent-0.1.3.vsix

The extension registers an MCP server with VS Code (1.101+), and Copilot agent mode receives the tool catalogue from the resolved backend binary. The managed download is version-pinned; a backend built from this source revision exposes 983 tools. The extension also adds workflow/autopilot/pipeline views. It can be built from source in editors/vscode with npm install && npm run package.

MCP registry

The server is listed on the official Model Context Protocol registry as io.github.MurariAmbati/aurora-agent (v0.1.1). Verify the listing directly:

curl "https://registry.modelcontextprotocol.io/v0.1/servers?search=aurora-agent"

The registry is metadata: tools that consume it (registry aggregators, editor integrations) can discover the server there, but installation still happens through one of the paths on this page.

Any MCP client (build from source)

The workspace builds offline against pinned dependencies:

git clone https://github.com/AURORA-NEURO/aurora-agent
cd aurora-agent
cargo build --release --offline

Then point any MCP client at the stdio server:

./target/release/bioprism-mcp --root .

The server speaks JSON-RPC 2.0 over newline-delimited stdio and follows the MCP lifecycle (initialize, then notifications/initialized, then tool calls). Paths are confined to --root; absolute paths, .., and symlink escapes are refused. 983 tools are exposed, from fiber_compile / fiber_refine / fiber_verify through the evaluation, oracle, safety, and operations surfaces.

CLI and HTTP gateway

The same build produces bioprism (a CLI with --json envelopes and a ten-exit-code retryability matrix — every failure code carries exactly one retry decision) and bioprism-api, a bounded local HTTP gateway for deployments that need a network boundary. The gateway binds to an address you choose, loopback by default. Explicit source HTTP retrieval needs a repeated --allow-http-origin <host[:port]> startup option and a caller plan that opts in; requests use unencrypted HTTP.