MCP Servers
The Model Context Protocol servers that give the model typed access to external systems.
Model Context Protocol (MCP) servers expose typed tools to the model — a structured, validated surface that is stricter and more auditable than shelling out. LisaOS runs a set of them, each covering one external system.
The server set
| Server | Transport | Tool surface | Depended on by |
|---|---|---|---|
| Issue tracker | HTTP | ~32 tools | Task/sprint skills, intelligence ingestion |
| Meeting intelligence | HTTP | 6 tools | Ingestion sweeps, situational monitoring |
| Messaging | Local service | ~12 tools | Ingestion sweeps, the communication-scan job |
| Memory gateway | Local service | Small, stable tool set | Every session and agent — memory, dispatch, sessions |
| Documentation lookup | Stdio | 2 tools | Engineering and writing agents, for library/API docs |
| Sequential reasoning | Stdio | 1 tool | Complex reasoning chains |
| Design tool | HTTP | ~17 tools | Brand-identity extraction, design work |
| Repository host | HTTP | Variable | Pull-request and repository workflows |
Tool counts are approximate and drift as servers version; the vault registry holds the exact current numbers.
Why the memory gateway is the load-bearing one
Most servers are optional — if the design tool is down, design work waits, and everything else proceeds. The memory gateway is different: it is the operational memory, the dispatch controller, and the session registry all at once. Every session opens against it and every dispatch is recorded through it. Its tools are deliberately few and their schemas deliberately stable — a stability discipline documented under raw-twin discipline, which exists precisely because a memory write must never be silently dropped by a stale client schema.
Degradation
MCP servers are checked at session start. A server that fails its pre-flight probe is reported with a one-line remediation hint; the session can wait for a fix or proceed with that capability degraded. No single external server is a hard prerequisite for a session — except that losing the memory gateway means running without persistent memory, which the session will say plainly.
A deprecated surface
At least one messaging transport has been deprecated — its function moved elsewhere and its server retired. Deprecated integrations are recorded rather than erased, so the reason a capability moved is not lost.