SoloMD

What SoloMD MCP server does

SoloMD connects MCP clients to Markdown notes stored in one or more local workspaces. It exposes the same vault used by the SoloMD editor, allowing an agent to search and inspect notes without requiring a separate copy or hosted knowledge base.

The endpoint includes 16 tools covering note search, backlinks, tags, tasks, outlines, and Git history. It also includes SoloMD-specific operations for AutoGit logs, diffs, rollback, synchronization status, share URLs, and agent traces. Read access is the default; write access must be explicitly enabled.

How it works

The bundled solomd-mcp executable communicates over stdio unless another transport is selected. MCP clients can therefore launch it as a local process and query the configured workspace directly. Version 4.0 added workspace federation: one MCP session can be started with multiple workspace paths.

For clients that use HTTP instead of stdio, SoloMD supports opt-in Streamable HTTP on loopback. That mode uses a bearer token. The MCP endpoint operates on the same .md files as the desktop editor, while local Git data can provide note history and recovery operations.

Setup and configuration

Install SoloMD on macOS or Linux to obtain the bundled solomd-mcp binary. The command-line interface can print an MCP configuration snippet with solomd mcp-config, or install configuration into AI clients detected on the machine with solomd mcp install.

A single workspace can be passed to the server, or multiple paths can be supplied with repeated --workspace options, such as --workspace path1 --workspace path2. The default stdio transport requires no network listener. Enable HTTP with --transport http; loopback binding and bearer-token authentication apply in that mode. Use --allow-write when an MCP client must modify the vault.

Tools and capabilities

• Search Markdown notes, including semantic search through the SoloMD application.
• Inspect backlinks and linked-note relationships.
• Find tags and tasks across a workspace.
• Read note outlines.
• Review AutoGit history, diffs, and synchronization status.
• Roll back changes when write access is enabled.
• Read replayable agent traces from recipe runs.
• Work across multiple federated workspaces in one MCP session.

Limitations and notes

SoloMD is local-first: notes, API keys, embeddings indexes, and Git history remain on the machine. The MCP server is read-only unless --allow-write is supplied. HTTP access is an opt-in local mode rather than a general public endpoint, and it requires bearer-token authentication.

The server is bundled with the SoloMD desktop application and is intended for Markdown folders managed by SoloMD. Agent recipe writes use AutoGit branches and require acceptance or rejection before reaching the main branch; recipes also refuse to start when the working tree is dirty. SoloMD is released under the MIT license.