SPEC_01 // OVERVIEW
EN ID
GitHub
SPEC_01 // Hela-Ecosystem-MCPDOSSIER: OVERVIEW_AND_INSTALL

HeLa Cellular MCP Workbench

A reproducible, 10-server MCP distribution suite for AI agents. Dual-backbone orchestration (reasoning + memory), deterministic stdio transport, and per-profile client configuration across 8 agent harnesses.

Blotcat Cellular Developer Workbench
FIG.PLATE 01 · blotcat-hero.jpg · Workbench overview

What this is

Ten specialized servers, each a biological cell with one job. Two backbones coordinate them: HeLa Mitosis (task reasoning and routing) and HeLa Genome (persistent memory graph). The remaining eight cells provide filesystem, execution, processes, research, browser, design, mobile, and 3D capabilities.

TABLE 1.1 — THE TEN CELLS
CellIDScopeRole
Mitosishela-mitosiscoreOrchestration backbone
Genomehela-genomecoreState & memory backbone
Membranehela-membranecoreWorkspace filesystem
Nucleushela-nucleuscoreExecution boundary
Ribosomehela-ribosomecoreProcess harness
Enzymehela-enzymecoreKnowledge synthesis
Cytosolhela-cytosolcoreBrowser interaction
Phenotypehela-phenotypespecializedDesign & tokens
Receptorhela-receptorspecializedMobile automation
Plastidhela-plastidspecialized3D Blender modeling

Full tool catalogs, entries, and repositories: 04 Architecture. Named in recognition of Henrietta Lacks (1920–1951): modular specialization, deterministic replicability, longevity.

Installation

Requirements: Node.js 20+ LTS, Git 2.25+, SQLite3. Optional per cell: Playwright Chromium (cytosol), ADB (receptor), Blender 4+ (plastid).

SHELL // CLONE_AND_INSTALL
git clone https://github.com/Hela-Ecosystem/hela-mcp-ecosystem.git
cd hela-mcp-ecosystem
./setup.sh --profile dev-workspace --client opencode

setup.sh clones, builds, and writes the client configuration for the chosen profile. Useful flags: --system gui|headless, --reconfigure (config only), --dev (track branches instead of pins), --with-runtime (also build the HeLa Runtime daemon), doctor (diagnostics).

Single-endpoint alternative: ./setup.sh --profile runtime --client opencode builds all 10 cells plus the HeLa Runtime daemon — your client connects to one MCP server instead of ten. The runtime provides lazy ignition, crash recovery, opt-in namespacing, and in-process hela.pipe chaining.

Verify

Three gates, all expected green before use:

SHELL // VERIFICATION_GATES
./setup.sh doctor     # 10/10 [READY] Stdio JSON-RPC OK
npm test              # 13 passed: 10 handshakes + 3 synergies
npm run test:matrix   # 70 passed: profile × client schema accuracy
EXPECTED RESULT
Doctor reports all ten cells READY; integration suite passes 13/13 in ~2.5s; matrix passes 70/70. Anything else: 08 Diagnostics.

Next steps

  1. Understand the organism. Read 04 Architecture for the dual-backbone model and per-server tool catalogs.
  2. Pick a profile. Eight pre-configured stacks (full desktop to headless CI) in 06 Profiles & Config — generate the client file with the configurator.
  3. Run a workflow. Six cross-MCP pipelines (feature engineering, research, UI verification, mobile QA, PTY orchestration, 3D) in 05 Workflows.
MIT LICENSE · AZZARARCHIVAL_RECORD_SEALED // HELA_MCP_ECOSYSTEM