Utilizing LogSeq as an MCP Client

  • In theory all that should be possible, but not easy (not even for a software developer).
    • Should isolate the various challenges and try solving each one individually.
    • For now I’m going to just list some of Kits’ relevant features.
  • Kits is currently the most comprehensive library for modularizing and running client-side code within Logseq.
    • It already performs conditional loading of external libraries, in the cases of Pyodide and WebR.
      • Any other online script could be dynamically imported on demand.
    • It has access to everything Logseq, but not to the operating system.
    • It resides itself in custom.js, but then facilitates running all other code from Logseq pages.
      • Each kit needs only a single Logseq page and most kits are happy with that.
        • Within a page, multiple code-blocks can be utilized.
      • Bigger kits can benefit from breaking their code to multiple Logseq pages.
        • Synthesis is such a kit, as its base libraries reside in multiple pages.
          • Though Synthesis further modularizes code to individual blocks.