Connect a program to your folder with MCP
Connected programs is an MCP server in Writ. Claude Code, Cursor or another program you connect can search and read the files in Writ's folder and, if you allow it, write them.
1. Switch the app on
Settings, Apps, Connected programs. This starts nothing by itself: the program you connect launches the server when it needs it, over its own input and output. Writ opens no port for it.
2. Add Writ to the program
With the app on, Connect a program has a card for each client. Add runs the client's own command for Claude Code, Codex and Gemini CLI, opens Cursor, VS Code or LM Studio with Writ filled in, and opens a bundle Claude Desktop asks to install. Writ never edits another program's configuration file. When a client's command is not on your computer, its card shows the line to run in a terminal. For Claude Code it is:
claude mcp add --scope user writ -- "/Applications/Writ.app/Contents/MacOS/writ" mcp --scope user adds Writ to every project rather than the folder the command runs in. Test, on any card, starts the same command and reports how many tools Writ lists. For a client that reads a JSON file, the Other programs card copies:
{
"mcpServers": {
"writ": {
"command": "/Applications/Writ.app/Contents/MacOS/writ",
"args": ["mcp"]
}
}
} On Windows and Linux the path is the one Settings shows for your install.
3. Approve the first call
A program's first call waits for you, on its card and where the program is told to look: Settings, Apps, Connected programs, Waiting for you. If Writ is open when it asks, a notice names the program, and the toolbar's programs mark carries a dot while one waits. Choose Approve reading, Approve reading and writing, or Don't allow.
A program you don't allow is turned down on every call without waiting again, and stays under Programs with reading and writing off. Switch either on there, or Forget the program so its next call waits again. A change there or in config.toml applies on the next call.
4. What it can do
With reading approved: list the text files in the folder, search, read a file, read a file's links, backlinks, properties and tags, list the folder's tags, and show a file in Writ. With writing approved: write, create and rename a file, add to its end, replace one passage, and make or add to today's file. A third switch, Open file, lets it see the file open in Writ and the text selected in it. No tool deletes a file. A write is checked against the version the program read, so a write over a newer file is refused and the program's text lands beside the file as a conflict copy. A file the program has not read is not written unless it asks to overwrite it. Writ keeps the text every write replaces, and Revert To, in the File menu, puts it back. Outside Writ's folder, a program with Open file on sees only the name and the selected text of the file in front.
5. See what it did
Program activity, in the View menu and on the toolbar, lists every call: the program, what it asked for, the file, and whether it was allowed, not allowed or left waiting. Repeated reads of one file share a line with a count. The list holds no file text and stays in Writ's data folder on your machine.
Output that arrives as files
If a script writes files rather than calling tools, Settings, Integrations, Folder to watch for new files opens each file as it lands and brings the window forward. Have the program write there, or pipe its output in:
make test 2>&1 | writ --title tests The output is saved as a file in Writ's folder, so search finds it later.