Everything salt.md does
39 pages covering every screen, every property type, every tool an agent can call and every setting on the server. Written by reading the source, and checked against it on every build, so a name in here is a name that exists.
Hand the whole manual to your assistant.
Every page is available as plain Markdown at the same address with .md on the end, and /wiki/llms.txt is the index of them. Paste this into ChatGPT, Claude, Gemini or whatever you have open.
No login, no JavaScript, no rate limit. If your assistant cannot browse, paste the contents of llms.txt after the question.
Read https://salt.md/wiki/llms.txt in full. It is the index of the salt.md documentation and lists every page with a plain-Markdown URL. Then fetch the pages you need and answer my questions about salt.md from them rather than from memory. Every tool name and API path in that documentation is verified against the source on each build, so you can act on them directly. Start by telling me what salt.md is and what it can do.
Writing, finding and organising — the parts everybody touches.
Getting started
salt.md is one program: a single executable file that contains the server, the web interface, full-text search and the agent endpoint.
Concepts
salt.md is built out of about fifteen nouns, and most questions about how it behaves turn out to be questions about which noun owns which.
The interface
This page describes the frame around your content: the sidebar, the document tabs, the topbar above a page, the account menu, the theme, every keyboard…
Pages
A page is the unit everything in salt.md is made of.
Editor blocks
The body of a document is a stack of blocks. A paragraph is a block, so is a heading, a list item, a table, an image, a callout, a whole two-column layout.
Comments and notes
A page in salt.md carries two separate records beside its text, and they are not variations of one thing.
Search
Search is the fastest way to reach anything in salt.md.
Files
Anything you upload — a PDF, an image, a spreadsheet, a workspace logo — is stored as a file on disk beside the database, referenced from the page it was added…
The library
The library fills the main area with every page of one workspace — a shelf you browse rather than a list you read.
Trash and recovery
No page in salt.md is deleted by clicking one button.
A page whose children are its rows, and everything that grows out of that.
Collections
A collection is a page whose child pages are its rows.
Properties
A property is a typed field on a collection.
Views
A view is a saved way of looking at one collection: a type (table, board, calendar and four more), the conditions a row must meet to appear, the order the rows…
Relations and rollups
Three property types turn separate collections into one connected thing: a relation points at rows in another collection, a backrelation is that same link read…
Formulas
A formula is a property of a collection that holds arithmetic instead of a value: *price times quantity*, *hours minus hours already billed*.
Forms
A form is one of the seven view types a collection can have. It draws the collection's properties as fields to fill in, and submitting it creates a row.
Templates and blueprints
Two ways to start from something instead of from nothing. A template copies one page — with everything filed under it — into a new page.
Who can see what, who did what, and what happens when two people type at once.
Workspaces
A workspace is the boundary around content. Every page in salt.md belongs to exactly one workspace, and you only see pages in workspaces you are a member of.
Permissions
Who may see and do what.
Sharing
salt.md is private by default: every page needs a signed-in account with access to the workspace it lives in. Publishing a page is the one deliberate exception.
Working at the same time
Two people can open the same document and type in it at once. Nothing locks, nothing asks who wins, and there is no save button.
History and audit
salt.md keeps four separate records, and they answer four different questions.
Your account
Everything that belongs to you rather than to a workspace: how the account came into existence, your name, picture and colour, how you sign in, the second…
Language and time
salt.md speaks the language your browser asks for and writes dates the way your region writes them, without anybody configuring anything.
The MCP surface: what an agent may do, with which credential, and every tool it has.
Agents
salt.md carries an MCP server inside the same binary that serves the interface.
MCP tools
salt.md speaks MCP (Model Context Protocol) on one endpoint, /mcp, and offers 33 tools.
Agent access
An agent reaches salt.md with a credential that belongs to a person.
The agent skill
salt.md can write an instruction bundle for itself: a small zip of Markdown that tells an AI agent how this team works here — the address of this instance,…
Everything that reaches outside the instance, in both directions.
Automation
salt.md connects to things outside itself in several ways: it calls an address of yours when a page changes, your calendar app subscribes to a feed of your…
Webhooks
A webhook is a standing instruction to call an address of your choosing when a page is created, changed or thrown away.
Import and export
Getting content into salt.md and back out again.
The REST API
Everything the salt.md interface does, it does over an HTTP API that you can call yourself: create pages, read and write database rows, search, upload files,…
For whoever owns the server: installing, updating, and the setup nobody enjoys.
Self-hosting
This page is for whoever runs the server.
Administration
Running the instance: naming it, deciding who may get an account, inviting people, managing accounts through their whole life, cleaning up workspaces nobody is…
Reaching your instance from outside
A fresh salt.md listens on :8420 and answers on every network interface of the machine it runs on. That is enough for a laptop and for a server on your own network.
Single sign-on
salt.md can hand sign-in to Google or Microsoft.
Sending email
salt.md can send email, and it sends very little of it.
The desktop app
salt.md has a desktop application. It is a window onto a server you run — not a second copy of the product, not a local instance, and not an offline mode.
Troubleshooting
Real failures, what they look like from the outside, and what actually fixes them.
One command. Then it is yours.
Install it, open the browser, create your admin account. If you do not like it, delete one directory and it is gone.
$ curl -fsSL https://raw.githubusercontent.com/saltmd/salt.md/main/install.sh | sh