How 1999azzar/hela-mcp-ecosystem works
HeLa MCP Ecosystem combines profile-based setup and client configuration with an HTTP gateway for routing MCP traffic to specialized servers. The main user workflow is selecting a profile and client, generating or installing that configuration, then having an AI client send requests to the selected MCP services (directly or through the gateway). README capabilities are represented from documentation; detailed setup internals and most backend implementations were not sampled, so their wiring is shown only where documented or supported by gateway source.
Main entry points: server.mjs HTTP Gateway · setup.sh Setup & Update · generate-config.mjs Client Config Generator · profiles.json Profile Catalog
Components 21
Profiles & Setup
- Setup & Update
setup.sh - Profile Catalog
config/profiles.json - Server Inventory
config/inventory.json - Pinned Snapshots
config/snapshots - Client Config Generator
scripts/generate-config.mjs - Client Examples
config
Gateway
- HTTP Gateway
gateway/server.mjs - Capability Router
gateway/router.mjs - List Cache
gateway/cache.mjs
MCP Services
- Mitosis Orchestrator
- Genome Memory
- Membrane Filesystem
- Nucleus Execution
- Ribosome PTY
- Enzyme Research
- Cytosol Browser
- Phenotype Design
- Receptor Mobile
- Plastid 3D Modeling
Other components
- Operator
- AI Client
Connections 21
- Operator → Setup & Update: selects profile
- Setup & Update → Profile Catalog: uses profiles
- Setup & Update → Server Inventory: uses inventory
- Setup & Update → Pinned Snapshots: pins snapshot
- Operator → Client Config Generator: requests config
- Client Config Generator → Profile Catalog: reads profiles
- Client Config Generator → Server Inventory: resolves servers
- Client Config Generator → AI Client: emits config
- AI Client → HTTP Gateway: sends MCP requests
- HTTP Gateway → Capability Router: resolves backend
- HTTP Gateway → List Cache: checks lists
- HTTP Gateway → Mitosis Orchestrator: forwards requests
- HTTP Gateway → Genome Memory: forwards requests
- HTTP Gateway → Membrane Filesystem: forwards requests
- HTTP Gateway → Nucleus Execution: forwards requests
- HTTP Gateway → Ribosome PTY: forwards requests
- HTTP Gateway → Enzyme Research: forwards requests
- HTTP Gateway → Phenotype Design: forwards requests
- AI Client → Cytosol Browser: uses by profile
- AI Client → Receptor Mobile: uses by profile
- AI Client → Plastid 3D Modeling: uses by profile