Linggen MCP Server

Most knowledge and memory work still happens through a UI a human drives. Linggen MCP server moves it into the conversation instead. Local, privacy-focused RAG service for code search via MCP. https://linggen.dev.

The short version

Curl rather than a browser download on purpose: macOS attaches a quarantine attribute to anything a browser fetches, and these builds are ad-hoc signed rather than notarized, so a downloaded copy would be blocked on first launch. The installer fetches the tarball, checks its sha256, and puts Linggen.app in /Applications.

The tools it exposes

The server publishes 2 tools. What each one is for:

• CFO — personal finances: imports bank and credit exports, builds spend reports, learns your categories
• Memory — durable cross-host memory on the ling-mem daemon

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

How it compares

Among the knowledge and memory options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Linggen's toolset — CFO, Memory — is a fair guide to whether it matches your workflow. It is maintained by linggen; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Linggen's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.