llm-kosh
Allows publishing and verifying artifacts through GitHub Actions workflows.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@llm-koshsearch for notes about the API design"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
llm-kosh
llm-kosh is a local-first memory cartridge for MCP-compatible AI clients.
It gives your agents durable memory without handing your workspace to a hosted
memory service.
Think of it as a structured, inspectable memory layer for agents:
plain files you can back up, diff, and review
a tamper-evident ledger for every mutation
a read-only-by-default MCP server
a background service for intake and maintenance
a CLI for local control and automation
The experimental company-brain foundation adds reference-first multimodal evidence, session and episode understanding, atomic evidence-backed memories, review lifecycles, permission-first retrieval, and structured cited context packs. See Company brain foundation.
Why teams use it
Keep AI context local and auditable.
Separate the cartridge root from the repository root.
Drop receipts or intake files into watched folders and let the service absorb them.
Connect MCP clients with minimal privilege by default.
Publish and verify the same artifact through GitHub Actions.
Related MCP server: mnemo
What works today
The core project is usable now:
the CLI runs locally
the Python package installs and works
the MCP server runs locally
the service can watch intake folders
the GitHub Actions publish path is working
The remaining work is release polish for Windows, macOS, and Linux packaging.
Quick start
Python 3.10 or newer is required.
python -m pip install --upgrade llm-kosh
llm-kosh install --yes
llm-kosh statusThat installs the package, creates the default cartridge at
~/.llmkosh/cartridge, configures local defaults, and registers the supported
desktop integration where possible.
To manage the background service:
llm-kosh service start
llm-kosh service status
llm-kosh service stopIf you want to work in a custom cartridge location, set the root explicitly:
llm-kosh --root ./my-cartridge init --owner "Local User"
llm-kosh --root ./my-cartridge add --kind note --title "First memory" --body "Hello"
llm-kosh --root ./my-cartridge query "Hello"To migrate a cartridge into governed company memory:
llm-kosh --root ./my-cartridge brain migrate --dry-run
llm-kosh --root ./my-cartridge brain migrate
llm-kosh --root ./my-cartridge brain health
llm-kosh --root ./my-cartridge brain context "Prepare the next project decision"Register existing screenshots, documents, worksheets or HTML without copying their source bytes:
llm-kosh --root ./my-cartridge brain register ./report.xlsx --artifact-type worksheet
llm-kosh --root ./my-cartridge brain inspect <evidence-id> \
--locator '{"sheet":"Summary","range":"A1:F25"}'
llm-kosh --root ./my-cartridge brain evaluateBuild a replayable session/episode graph from a registered JSONL export:
llm-kosh --root ./my-cartridge brain register ./session.jsonl --artifact-type structured_data
llm-kosh --root ./my-cartridge brain understand <evidence-id> --dry-run
llm-kosh --root ./my-cartridge brain understand <evidence-id>
llm-kosh --root ./my-cartridge brain episodes --query "what was implemented"Core concepts
There are three folders worth knowing:
the repository root: the code checkout you are reading now
the cartridge root: the live memory store selected by
--rootorLLMKOSH_ROOTwatched intake folders:
receipts/,intake/, and any configured external drop folders
If you drop files into the cartridge’s intake areas, the service can process
them asynchronously. If you configure external folders through
[daemon].watched_directories, the service can absorb those too.
Use with MCP clients
llm-kosh --root ./my-cartridge mcp-serverThe MCP server starts read-only.
Enable stronger capabilities only for clients that should be allowed to write, mutate, or export private context:
llm-kosh --root ./my-cartridge mcp-server --allow-write
llm-kosh --root ./my-cartridge mcp-server --allow-write --allow-mutate
llm-kosh --root ./my-cartridge mcp-server --allow-privateYou can also run MCP over local HTTP:
llm-kosh --root ./my-cartridge mcp-server --http --port 8000
# endpoint: http://127.0.0.1:8000/mcpWhat’s included
Python CLI for creating, searching, packing, importing, and verifying cartridges
read-only-by-default MCP server
local background service for intake and maintenance jobs
optional desktop packaging with a bundled CLI sidecar
plain-file storage that stays inspectable, backupable, and Git-friendly
optional extras for filesystem watching, service integration, semantic search, and ingest helpers
Optional features
python -m pip install "llm-kosh[watch]" # filesystem events
python -m pip install "llm-kosh[server]" # FastAPI service
python -m pip install "llm-kosh[semantic]" # local vector search
python -m pip install "llm-kosh[ingest]" # document conversion helpers
python -m pip install "llm-kosh[all]" # all optional featuresMCP support is included in the base installation.
Developer workflow
python -m pip install -e ".[server,watch,ingest]"
python -m pytest -qIf you are changing packaging or release behavior, also run:
python -m build
python -m twine check dist/*Security model
Storage and search are local by default.
There is no automatic cloud sync or telemetry in the Python package.
MCP starts read-only.
Write, mutation, and private-export capabilities require explicit opt-in.
Context exports are checked for common secret patterns before sharing.
Cartridge files are plaintext; use operating-system disk encryption if local data at rest needs encryption.
See SECURITY.md and docs/SECURITY.md for boundaries and limitations.
Desktop app status
The Electron desktop app is packaged separately from the Python package. Local developer builds and Windows installer smoke tests are supported. Public GA desktop distribution still requires verified Windows code signing and macOS Developer ID signing/notarization.
For the current release posture across package, MCP, service, and desktop, see GA_READINESS.md.
Documentation
Native acceleration
Native C++ math acceleration is optional. Set LLM_KOSH_BUILD_NATIVE=1 and
install pybind11 before building if you want to test it. Release wheels use
the portable pure-Python fallback.
Licensed under the MIT License.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceAn MCP-native, local-first memory server that gives AI agents persistent, structured memory across sessions and tools, enabling them to maintain identity and context without reconfiguration.3MIT
- AlicenseNot gradedqualityCmaintenanceA local-first memory server for AI tools that provides cross-tool, consent-gated, and auditable memory management via MCP.AGPL 3.0
- AlicenseAqualityBmaintenanceMCP server for persistent, cross-session, local-first memory for AI agents, storing memories as Markdown files with SQLite indexing for hybrid search.24Apache 2.0
- AlicenseNot gradedqualityFmaintenanceLocal-first, auditable memory for AI agents. Provides durable context for MCP hosts with SQLite storage, CLI, and MCP tools for memory management.2Apache 2.0
Related MCP Connectors
Person-owned, portable AI memory as a remote MCP server, readable and writable by any MCP client.
Cloud-hosted MCP server for durable AI memory
Shared, governed long-term memory for AI agents across tools and sessions via MCP and REST.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/rastogivaibhav/llm-kosh'
If you have feedback or need assistance with the MCP directory API, please join our Discord server