froggychips
Russia · Moscow Thailand · Bangkok Apple Silicon · local LLMs · SRE automation
Self-taught SRE building small, sharp infrastructure tools for noisy systems: Apple Silicon, local LLMs, Kubernetes, MCP.
Currently shipping
Projects
Froggy ecosystem
- Froggy 8 GB is enough. Local LLM + screen-OCR daemon for memory-constrained Apple Silicon. Swift 6, MLX, ScreenCaptureKit. Runs on the Mac most tools say they need 16+ for.
- FroggyKit Just the plumbing. The seam between Froggy and everything that talks to it. Tiny on purpose — keeps Froggy-MCP and Froggy-SRE from drifting apart.
- Froggy-MCP Cloud model, local eyes. MCP bridge — Claude Code reads your screen, OCRs text, and calls the on-device Froggy daemon. Nothing leaves the box unless you ask.
- Froggy-SRE Triage in your dock. MCP-based SRE incident-response agent for macOS. Kubernetes alert → recon → root cause + proposed fix + risk score, without leaving the laptop.
SRE and MCP infrastructure
- SRE-AI-Copilot Signals first, AI second. KG-first SRE intelligence layer: AlertManager → topology/deploy/pod-event enrichment → Discord incidents with blast radius, NATS impact, pod trail, owners and daily digests. LLM optional; signals decide.
-
MCP-Skills-Vault
Trust, but pin. Supply-chain integrity gate for MCP servers — 112 vetted entries, sha512/Docker-digest pins, offline-first audit, and a browsable public registry. Because
npm installfrom a stranger is stillnpm installfrom a stranger. - MCP Trace Flight recorder for tools. Stdio proxy for MCP servers that captures JSON-RPC metadata into local SQLite. Built for debugging, audits, and “what did this agent actually call?” moments.
- @froggychips/mcp-vault The CLI gate. Audit, scan, install and doctor flows for MCP server manifests. Offline mode means “no network,” not “trust me bro.”