B
brazaoo4/helios
A token-budgeted, drift-aware MCP memory engine for AI coding agents.
updated 2026-11-19
View on GitHub ↗Direct link · no redirect page
We have neither an install command nor a public remote endpoint from this repository, so we do not print a config. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 0 ★ · brazaoo4/helios · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
brazaoo4/helios;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# ☀️ Helios
Excerpted from the repository README (abridged)
A token-budgeted, drift-aware MCP memory engine for AI coding agents.
Built for personal use across homelab services and multiple workstations. Open-sourced if you find it helpful.
Why Helios? • Quick Start • 1-Liner Client Setup • How Drift Detection Works • Architecture • MCP Tools
> I built Helios because I was tired of my AI coding agents bloating their context windows with repetitive prompt files and trusting outdated architecture configs after someone pushed code. It runs quietly in my homelab across laptops, headless CLI boxes, and different IDEs—and here it is if you want to use it.
## 💡 Why Helios?
AI coding agents usually suffer from two major pain points: amnesia (forgetting ports, conventions, and architecture choices between sessions) and knowledge drift (relying on stale documentation or outdated configs). Most memory tools either inject giant text dumps into every turn or rely on heavy vector databases that don't know when a git push invalidated a fact.
Helios solves this with a lightweight, token-budgeted approach:
| Approach | Token Overhead | Handles Contradictions? | Detects Code/Config Drift? | Cross-IDE / Multi-Host? |
| Static CLAUDE.md / GEMINI.md | High (loaded every turn) | ❌ Manual edits only | ❌ Silently goes stale | ❌ Per-machine / per-repo |
| Vector / RAG Memory Servers | High (dumps long chunks) | ❌ Keeps old & new facts | ❌ Blind to git push | ⚠️ Usually cloud-locked |
| ☀️ Helios | Ultra-Low (≤ 25 words/fact) | ✅ Deterministic slot supersession | ✅ Git webhooks flag [STALE] | ✅ Shared across IDE, CLI & SSH |
### Core Design Pillars
Strict Token Diet: Enforces atomic, high-density facts (≤ 25 words by default) so agent context windows stay lean, fast, and focused.
Write-Through Architecture (Definition of Done): Replaces fragile deferred end-of-session memory saves with continuous, atomic persistence. Tasks altering infrastructure, ports, schemas, dependencies, or resolving non-obvious bugs are strictly incomplete until recorded in Helios.
Deterministic Lineage (AUDN Protocol): Facts operate on Add, Update, Deprecate, or No-op semantics. Saving a fact to an existing (scope, subject) slot automatically supersedes the old fact and logs the transition in a historical audit trail.
Git-Anchored Drift Detection: Memories can be anchored to repo configuration files (e.g., docker-compose.yml, prisma/schema.prisma). When a git push modifies an anchored file on GitHub, Forgejo, Gitea, or GitLab, Helios automatically flags the memory as [STALE] so your agent inspects the diff before acting.
Dual-Plane Storage: Sub-millisecond SQLite WAL + FTS5 (BM25) full-text search for agents, mirrored into human-readable Markdown files (/data/exports/ .md) and crash-safe .tar.gz online snapshots for developers.
Live Day-2 Control Plane: Change word limits, episodic TTLs, scope aliases, and Git webhooks conversationally from your IDE without restarting containers.
## 🚀 1. Quick Start: Server Deployment
Create a compose.yaml file (or paste directly into Dockhand / Portainer) and run docker compose up -d:
### compose.yaml
yaml
services:
helios:
image: ghcr.io/brazaoo4/helios:latest
# Or to build locally from source:
Built for personal use across homelab services and multiple workstations. Open-sourced if you find it helpful.
Why Helios? • Quick Start • 1-Liner Client Setup • How Drift Detection Works • Architecture • MCP Tools
> I built Helios because I was tired of my AI coding agents bloating their context windows with repetitive prompt files and trusting outdated architecture configs after someone pushed code. It runs quietly in my homelab across laptops, headless CLI boxes, and different IDEs—and here it is if you want to use it.
## 💡 Why Helios?
AI coding agents usually suffer from two major pain points: amnesia (forgetting ports, conventions, and architecture choices between sessions) and knowledge drift (relying on stale documentation or outdated configs). Most memory tools either inject giant text dumps into every turn or rely on heavy vector databases that don't know when a git push invalidated a fact.
Helios solves this with a lightweight, token-budgeted approach:
| Approach | Token Overhead | Handles Contradictions? | Detects Code/Config Drift? | Cross-IDE / Multi-Host? |
| Static CLAUDE.md / GEMINI.md | High (loaded every turn) | ❌ Manual edits only | ❌ Silently goes stale | ❌ Per-machine / per-repo |
| Vector / RAG Memory Servers | High (dumps long chunks) | ❌ Keeps old & new facts | ❌ Blind to git push | ⚠️ Usually cloud-locked |
| ☀️ Helios | Ultra-Low (≤ 25 words/fact) | ✅ Deterministic slot supersession | ✅ Git webhooks flag [STALE] | ✅ Shared across IDE, CLI & SSH |
### Core Design Pillars
Strict Token Diet: Enforces atomic, high-density facts (≤ 25 words by default) so agent context windows stay lean, fast, and focused.
Write-Through Architecture (Definition of Done): Replaces fragile deferred end-of-session memory saves with continuous, atomic persistence. Tasks altering infrastructure, ports, schemas, dependencies, or resolving non-obvious bugs are strictly incomplete until recorded in Helios.
Deterministic Lineage (AUDN Protocol): Facts operate on Add, Update, Deprecate, or No-op semantics. Saving a fact to an existing (scope, subject) slot automatically supersedes the old fact and logs the transition in a historical audit trail.
Git-Anchored Drift Detection: Memories can be anchored to repo configuration files (e.g., docker-compose.yml, prisma/schema.prisma). When a git push modifies an anchored file on GitHub, Forgejo, Gitea, or GitLab, Helios automatically flags the memory as [STALE] so your agent inspects the diff before acting.
Dual-Plane Storage: Sub-millisecond SQLite WAL + FTS5 (BM25) full-text search for agents, mirrored into human-readable Markdown files (/data/exports/ .md) and crash-safe .tar.gz online snapshots for developers.
Live Day-2 Control Plane: Change word limits, episodic TTLs, scope aliases, and Git webhooks conversationally from your IDE without restarting containers.
## 🚀 1. Quick Start: Server Deployment
Create a compose.yaml file (or paste directly into Dockhand / Portainer) and run docker compose up -d:
### compose.yaml
yaml
services:
helios:
image: ghcr.io/brazaoo4/helios:latest
# Or to build locally from source:
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/brazaoo4-helios/)
- Source
- awesome · https://github.com/brazaoo4/helios
- Browse by field
- MCP servers
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.