FluctlightDB

Integrations

One brain, several ways in

The engine is a Python library with a Rust core. The adapters below are the ones that ship in the repository. LangChain, LlamaIndex and the MCP remember/recall pair were re-run from main on 30 September 2026. Docker and the Node HTTP client were not.

On this page

  • FluctlightMemory, and a chat history that returns the session

    The classes are FluctlightMemory and FluctlightChatMessageHistory, in fluctlightdb.integrations.langchain. On main the extra pins langchain-core to at least 0.2 and below 1.0. This run resolved langchain-core 0.3.86, and .messages returned both turns. That fix is not in the published package yet. It ships in the next release.

  • FluctlightLlamaMemory constructs, on main

    FluctlightLlamaMemory lives in fluctlightdb.integrations.llamaindex. On main it constructs, both with a positional brain and through from_defaults. This run used llama-index-core 0.14.25. put() then get() returned the stored turn, on the same brain. That fix is not in the published package yet. It ships in the next release.

  • Two handlers, and no SDK in the process

    FluctlightAgentsMemory does not import the Agents SDK. It wraps a brain and hands back remember_memory and search_memory. Those two callables were run. An Agent from the SDK was not.

  • A memory server for Cursor, Claude and Codex

    The module is fluctlightdb.mcp_server. On main, memory_remember calls checkpoint() after it flushes the turn. A second process then recalled the sentence. That fix is not in the published package yet. It ships in the next release. The server process itself still does not start on the mcp 2.x the extra resolved to.

  • The image the repository publishes

    ghcr.io/voxmastery/fluctlightdb is the image named in the repository. The commands below are copied from docs/DOCKER.md. They were not pulled, built, or started while this page was written. A local image build needs Rust 1.88.

  • HTTP from Node, against a server this page did not start

    There is no native Node binding in the wheel. The TypeScript client in sdks/typescript talks to fluctlight-serve. remember() posts to /api/v1/experience. recall() posts to /api/v1/activate and reshapes the response. Those routes exist in the server source. The round trip was not executed.

The install that everything else sits on

Embedded use, which is the path the rest of this site documents, is the published package. The LangChain, LlamaIndex and MCP fixes re-run below are on main and are not in that package yet. They ship in the next release. Until then, the Python package is the sdks/python directory of the repository. The second command is the one this re-run installed, and import of the three adapters succeeded from it. 

pip install "fluctlightdb[native]"

Main, not the published package. This is the command that was installed.

pip install "fluctlightdb[native,langchain,llamaindex,mcp] @ git+https://github.com/voxmastery/FluctlightDB.git@main#subdirectory=sdks/python"