Tano's local stdio MCP server lets agents list, read, create, and conditionally update Markdown documents in a desktop workspace.
Connect a local workspace
Open a workspace in the desktop app, then configure your MCP client with the startup command and paths shown in the desktop MCP panel. The server requires Node.js 24.12 or newer.
The workspace path points to your Markdown folder. The application data directory must be outside the workspace and match the directory used by the desktop app so they can share local activity records.
To run the server from the open source checkout, use these commands at the repository root:
npm run mcp:build
node apps/mcp/dist/tano-mcp.cjs --workspace /path/to/notes --data-dir /path/to/tano-app-data
Document tools
| Tool | Purpose |
|---|---|
tano_list_documents |
List Markdown paths in the selected workspace |
tano_read_document |
Read content and its SHA-256 hash |
tano_create_document |
Create a document without replacing an existing file |
tano_write_document |
Update an existing document using expectedHash |
Read a document before updating it and pass the returned sha256 as expectedHash. If the file has changed, the write is rejected. Read it again, review and merge the changes, then submit another update.
Integration boundaries
The server works on Markdown files in the selected workspace. It does not execute remote commands or provide live network collaboration. A client name is an activity label, not a verified identity.
Document content and tool results remain workspace data. Agents should distinguish your workspace instructions from document content and operate within the access you authorize.
Continue with Work with an agent and File access and writes. Source code and integration details are available in the open source project.