Self-hosted MCP server providing persistent memory, governance, and hybrid search for AI coding agents with git-native knowledge capture.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent β or use 1-click editor setup below.
We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag β we're steadily working through the catalog.
π‘ Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by Flaiwheel.
Self-hosted memory & governance layer for AI coding agents. Turn every bug fix into permanent knowledge. Zero cloud. Zero lock-in.
AI coding agents forget everything between sessions. That leads to repeated bugs, lost architectural decisions, and knowledge decay.
Flaiwheel ensures:
Every bug fixed makes the next bug cheaper.
It does not replace your AI assistant. It makes it reliable at scale.
π Whitepaper (PDF) β Vision, architecture, and design in depth.
Flaiwheel is a self-contained Docker service that operates on three levels:
Pull β agents search before they code (search_docs, get_file_context)
Push β agents document as they work (write_bugfix_summary, write_architecture_doc, β¦)
Capture β git commits auto-capture knowledge via a post-commit hook, even without an AI agent
.md, .pdf, .html, .docx, .rst, .txt, .json, .yaml, .csv) into a vector databaseget_file_context(filename) β pre-loads spatial knowledge for any file the agent is about to edit (complements get_recent_sessions for full temporal + spatial context)fix:, feat:, refactor:, perf:, docs: commit as a structured knowledge doc automaticallyGiven, When, Then) for QA automationrelations() and timeline() derive a per-project knowledge graph from optional YAML frontmatter on existing docs (id, replaces, depends_on, fixes, implements, status). No second store β markdown stays canonical and Git history is the validity windowvalidate_doc() checks freeform markdown before it enters the knowledge base, including unknown-relation-key warnings/api/impact-metrics computes estimated time saved + regressions avoided; CI pipelines can post guardrail outcomes to /api/telemetry/ci-guardrail-reportanalyze_codebase(path) scans a source code directory entirely server-side (zero tokens, zero cloud). Uses Python's built-in ast module for Python, regex for TypeScript/JavaScript, the existing MiniLM embedding model for classification and duplicate detection. Returns a single bootstrap_report.md with language distribution, category map, top 20 files to document first ranked by documentability score, duplicate pairs, and coverage gaps. Reduces cold-start token cost by ~90% on legacy codebases.http://host:8081/sse. This is the recommended configuration until the Web UI provides TLS activation, CA download, and operating-system installation instructions. An update preserves its existing mode unless FLAIWHEEL_TLS_AUTO=0 or 1 is set explicitly.FLAIWHEEL_TLS_AUTO=0 now explicitly returns an existing TLS-enabled installation to HTTP while preserving its volumes and other MCP_* settings.FLAIWHEEL_TLS_AUTO unset during an update preserves the currently deployed mode.v3.15.2 corrected endpoint schemes and certificate persistence, but its direct-SSE client guidance was incomplete. An env block containing NODE_EXTRA_CA_CERTS does not necessarily control TLS for a direct Cursor/Electron SSE connection. Direct clients may require the generated CA in the operating-system trust store. Use the default HTTP endpoint unless you have completed that trust step.
192.168.178.230, so the only previous options were openssl by hand or a proxy. Set MCP_SSE_TLS_AUTO=true and Flaiwheel generates a private CA plus a server certificate on first start, covering the configured hosts and loopback./data/tls and reused while it is valid and still covers the requested names β an upgrade does not change the fingerprint, so a client that pinned the CA stays valid. A certificate that has gone stale, stopped covering a host, or lost its matching key is re-issued, with the reason logged.mkcert to run a per-machine step. So the startup log prints the fingerprint and the exact NODE_EXTRA_CA_CERTS=... line for the client's env block. That is the floor, and it is real TLS: encryption and identity, with the CA pinned by trust-on-first-use.NODE_TLS_REJECT_UNAUTHORIZED=0 anywhere in this path. The easy way to "make HTTPS work" is to disable verification, which defends against nothing; it is not offered as an option here.http:// to https://, and doing that unasked during an upgrade would break every existing client β the same class of failure as an installer that refuses to upgrade. It fails closed too: if provisioning fails, startup aborts rather than quietly serving cleartext.200; an untrusting client is rejected. Both directions asserted.Factual signals from GitHub, npm, and our automated checks β not a rating.
No reviews yet β be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/dl4rce-flaiwheel)<a href="https://allmcps.com/mcp/dl4rce-flaiwheel"><img src="https://allmcps.com/api/badge/dl4rce-flaiwheel?style=directory" alt="Flaiwheel on AllMCPs" /></a>