Docs
/
shared/engines/adapters/

Adapter systems

ALL adapter systems live here, together — added bit by bit, each following ONE contract so the @leumas/middleware loader can discover it, @leumas/mcp-kit can expose it as an MCP tool, and the...

Adapter systems (shared/engines/adapters/)

ALL adapter systems live here, together — added bit by bit, each following ONE contract so the @leumas/middleware loader can discover it, @leumas/mcp-kit can expose it as an MCP tool, and the Knowledge Bank can register it.

  • domain/a. capability packs (physics, embeddings, vision, audio, …). ← leumas-middleware/lib/a.
  • knowledge/b. knowledge banks (animals, medicine, plants, geography, …). ← Knowledge-Banks/adapters/b.
  • hardware/ · surveillance/ · properties/ · patents/ — the managed-domain (CRM) adapter systems.

The contract (per adapter system folder)

<name>/
├─ metadata.json     # { name, description, inputs?, category }
└─ index.js          # export default { metadata, adapters: { <tool>: (args) => result } }

adapterToServer() (from @leumas/mcp-kit) turns any of these into an MCP server automatically — so a new adapter is instantly an API, a form, an MCP tool, and a marketplace listing with no per-adapter UI.

Source shared/engines/adapters/README.md (no-git)markdownjson
Generated from the Leumas repository. Every page cites the file it came from.leumas.techllms.txt