# AI use cases for Salt (saltmd/salt.md) Repo: [saltmd/salt.md](https://github.com/saltmd/salt.md) | Use cases: 4 | Page: https://dedupedai.com/use-cases/saltmd-salt-md/ salt.md is a self-hosted, open-source workspace with docs, databases and realtime editing, plus an MCP server so AI agents work in the same workspace under the same permissions. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Run a team workspace on your own server: https://dedupedai.com/use-cases/saltmd-salt-md/self-host-team-workspace/ - Let an AI agent work in your workspace via MCP: https://dedupedai.com/use-cases/saltmd-salt-md/connect-agent-to-workspace/ - Move a Notion export or Markdown folder into Salt: https://dedupedai.com/use-cases/saltmd-salt-md/migrate-notion-and-markdown/ - Load a JSON dataset into a workspace database: https://dedupedai.com/use-cases/saltmd-salt-md/agent-bulk-import-json/ ## How to run a team workspace on your own server with Salt Repo: [saltmd/salt.md](https://github.com/saltmd/salt.md) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Install one binary and get docs, databases and realtime editing on your own machine. **Who it is for:** A team lead or sysadmin who wants shared docs and databases on infrastructure they control, without a separate database server. **The problem:** Shared docs and databases usually live in a hosted service, and running a multi-service stack yourself is heavy. **The outcome:** A running Salt instance on your server, reachable in a browser, backed by a single SQLite file and an uploads directory. ### Steps 1. Run `curl -fsSL https://raw.githubusercontent.com/saltmd/salt.md/main/install.sh | sh` on the server (or `wget -qO- … | sh` if curl is missing). 2. Note the address the installer prints and open it in a browser. 3. Alternatively, run `docker run -d -p 8420:8420 -v salt-data:/data ghcr.io/saltmd/salt.md:latest` if you prefer Docker. 4. Read the self-hosting guide at https://salt.md/wiki/self-hosting/ for reverse proxies, TLS and backups before exposing it to your team. ### Prompt to paste into your agent ```text Using the salt.md repo at https://github.com/saltmd/salt.md, install a self-hosted instance on using the install.sh one-liner from the README. Report the address the installer prints and confirm that the URL responds in a browser. ``` ### Caveat The README says TLS, reverse proxies and backups are covered in the self-hosting guide, so plan those before putting the instance on a public network. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/saltmd-salt-md/self-host-team-workspace/ ## How to let an AI agent work in your workspace via MCP with Salt Repo: [saltmd/salt.md](https://github.com/saltmd/salt.md) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Point Claude, Cursor or another MCP client at /mcp so it edits pages and databases. **Who it is for:** A knowledge worker whose team already runs Salt and who wants an AI assistant to create and update pages and rows on their behalf. **The problem:** Copying content between an AI chat and the workspace by hand is slow and error prone. **The outcome:** An MCP client connected to your instance's /mcp endpoint that can create pages, add database rows and search, on your own access level. ### Steps 1. Make sure the instance is running and note its base address, then append /mcp to it. 2. Add that /mcp address as an MCP server in your client, such as Claude, ChatGPT, Codex, Cursor or Gemini CLI. 3. Authenticate the client with the access you want it to have. An agent's credential carries your person's access and never more. 4. Ask the agent to create a page, then open the workspace to confirm it appears with the same history as your own edits. ### Prompt to paste into your agent ```text Using the salt.md repo at https://github.com/saltmd/salt.md, connect this MCP client to the /mcp endpoint of . Create a test page titled and confirm it appears in the workspace and in the activity log. ``` ### Caveat The README says agents cannot create or delete accounts, issue tokens, take backups, change instance settings or decide workspace membership, so do those steps yourself. Risk, credentials: The MCP client holds a credential for your account, so treat its token as you would a password and only add clients you trust. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/saltmd-salt-md/connect-agent-to-workspace/ ## How to move a Notion export or Markdown folder into Salt with Salt Repo: [saltmd/salt.md](https://github.com/saltmd/salt.md) | Difficulty: Intermediate | Time: 1 hour | Basis: From the README Import Markdown, CSV or Notion export files into a self-hosted workspace in one pass. **Who it is for:** A team leaving a hosted notes tool that needs its pages and tables moved to a self-hosted instance. **The problem:** Re-creating pages and tables by hand from an old workspace takes days and loses structure. **The outcome:** Your pages, CSV tables and Notion content appear in the new workspace, ready to edit and share. ### Steps 1. Export your content from the old tool as a Notion export, Markdown files or CSVs. 2. Install and open your Salt instance using the install.sh one-liner or the Docker command in the README. 3. Open the import option from the workspace menu and choose the Markdown, CSV or Notion export source. 4. Check a few pages and tables against the originals, including links and any database properties. ### Prompt to paste into your agent ```text Using the salt.md repo at https://github.com/saltmd/salt.md, import the export at into the instance at through the workspace import menu. Report how many pages and tables were created and list any that failed. ``` ### Caveat The README names Markdown, CSV and Notion export as supported import sources, so check any other format by testing a small sample first. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/saltmd-salt-md/migrate-notion-and-markdown/ ## How to load a JSON dataset into a workspace database with Salt Repo: [saltmd/salt.md](https://github.com/saltmd/salt.md) | Difficulty: Advanced | Time: 1 hour | Basis: From the README Have an agent bulk-import rows from a JSON source without the content passing through it. **Who it is for:** A ops or research lead with a JSON dataset that should appear as a tracked database in the team workspace. **The problem:** Adding hundreds of records to a database one at a time through a chat is impractical. **The outcome:** A database in the workspace filled with the imported rows, with views you can filter and share. ### Steps 1. Connect your MCP client to the /mcp endpoint of your instance, as described in the README. 2. Ask the agent to create a database with the properties your JSON needs. 3. Point the bulk import at your JSON source so the rows load without the content passing through the agent. 4. Open the database, add a table view with filters, and check the row count against the source file. ### Prompt to paste into your agent ```text Using the salt.md repo at https://github.com/saltmd/salt.md, create a database in the workspace at and bulk import the JSON file at . Report the number of rows created and confirm the count matches the source. ``` ### Caveat The README does not document the JSON format the bulk import expects, so inspect the import result before relying on the data. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/saltmd-salt-md/agent-bulk-import-json/