by saltmd
Provides docs, databases, and realtime collaboration within a single binary, allowing AI agents and humans to share the same workspace with unified permissions.
Salt Md delivers a self‑hosted workspace where documentation, structured data, and real‑time editing coexist. It runs as a single Go binary backed by one SQLite file, enabling both people and AI agents (Claude, ChatGPT, Cursor, etc.) to operate on the same pages, databases, and permissions.
curl -fsSL https://raw.githubusercontent.com/saltmd/salt.md/main/install.sh | sh downloads, installs, starts the service, and shows the access URL. Re‑run to upgrade.docker run -d -p 8420:8420 -v salt-data:/data ghcr.io/saltmd/salt.md:latest runs the server in a container./mcp.uploads/ folder.Q: How do I back up my data?
A: Stop the server, copy the SQLite file and the uploads/ directory, then restart.
Q: Can I run Salt Md on Windows? A: Yes, a static Windows amd64 binary is provided.
Q: How do I upgrade? A: For the binary install, re‑run the install script; for Docker, pull the newer image and restart the container.
Q: What license is it under? A: AGPL‑3.0 – you may use, modify, and run it at work, but must publish changes if you provide the service over a network.
Q: How are AI agents authenticated? A: Agents receive a credential that carries the same access rights as the associated user; they cannot exceed those permissions.
Q: Do I need external services like PostgreSQL or Redis? A: No. All data lives in a single SQLite file; the binary includes the embedded frontend.
Q: Where can I find the documentation? A: The full docs are at https://salt.md/wiki/ and are version‑checked against the codebase.
curl -fsSL https://raw.githubusercontent.com/saltmd/salt.md/main/install.sh | sh
One command downloads the binary for your platform, installs it, starts it and
prints the address to open. On a Linux server it sets itself up as a systemd
service, and running it again upgrades it. No curl on the machine?
wget -qO- … | sh does the same.
Or with Docker:
docker run -d -p 8420:8420 -v salt-data:/data ghcr.io/saltmd/salt.md:latest
There is nothing else to install: no database server, no cache, no object store. Reverse proxies, TLS and backups are in the self-hosting guide.
An agent is asked to organise the launch notes. A page appears, a database is created, the rows fill in. A person opens the same board a second later and carries on. Same pages, same permissions, same history.
Connect Claude, ChatGPT, Codex, Cursor, Gemini CLI or any other MCP client to
/mcp and it works on the workspace you use:
And a list it cannot touch. No agent can create or delete accounts, issue tokens, take or restore a backup, change instance settings or decide who is in a workspace, and the server tells every agent that connects. A credential carries its person's access and never more, every workspace decides what agents may do there, and the activity log keeps their changes apart from yours.
MCP tools · Agent access · Permissions
Moving in? Markdown files, CSVs and a Notion export import from the same menu.
One Go process, built with CGO_ENABLED=0: a static binary with a pure-Go
SQLite driver and the frontend embedded. No PostgreSQL, no Redis, no object
store, no separate collaboration server.
install.sh, or the Docker imageThe desktop app for macOS and Linux is a window onto a server you run, not a second copy of the product.
salt.md/wiki covers every screen, every property type,
every tool an agent can call and every setting on the server. It is written next
to this code and checked against it on every build: a tool name that no longer
exists, an API path that is not a route or a screenshot whose screen has changed
fails the build. Every page is also plain Markdown at the same address with
.md on the end, indexed for agents at
/wiki/llms.txt.
Issues and pull requests are welcome. Pull requests need a signed CLA; CONTRIBUTING.md says what that means and why it exists. Security reports go to dev@salt.md, not to a public issue: see SECURITY.md.
AGPL-3.0. Use it, run it at work, change it. If you offer it to others over a network, publish your changes.
The components salt.md is built on, with their licences in full, are in
THIRD-PARTY-NOTICES.md. A running instance serves the
same list at /licenses.
Please log in to share your review and rating for this MCP.
Explore related MCPs that share similar capabilities and solve comparable challenges
by modelcontextprotocol
A basic implementation of persistent memory using a local knowledge graph. This lets Claude remember information about the user across chats.
by topoteretes
Provides dynamic memory for AI agents through modular ECL (Extract, Cognify, Load) pipelines, enabling seamless integration with graph and vector stores using minimal code.
by basicmachines-co
Enables persistent, local‑first knowledge management by allowing LLMs to read and write Markdown files during natural conversations, building a traversable knowledge graph that stays under the user’s control.
by agentset-ai
Provides an open‑source platform to build, evaluate, and ship production‑ready retrieval‑augmented generation (RAG) and agentic applications, offering end‑to‑end tooling from ingestion to hosting.
by smithery-ai
Provides read and search capabilities for Markdown notes in an Obsidian vault for Claude Desktop and other MCP clients.
by chatmcp
Summarize chat messages by querying a local chat database and returning concise overviews.
by dmayboroda
Provides on‑premises conversational retrieval‑augmented generation (RAG) with configurable Docker containers, supporting fully local execution, ChatGPT‑based custom GPTs, and Anthropic Claude integration.
by qdrant
Provides a Model Context Protocol server that stores and retrieves semantic memories using Qdrant vector search, acting as a semantic memory layer.
by doobidoo
Provides a universal memory service with semantic search, intelligent memory triggers, OAuth‑enabled team collaboration, and multi‑client support for Claude Desktop, Claude Code, VS Code, Cursor and over a dozen AI applications.