Docmost Local MCP

What wisflux/docmost-local-mcp MCP server does

wisflux/docmost-local-mcp MCP server gives AI clients a local stdio connection to a self-hosted Docmost installation. It supports both read and write operations across spaces, pages, comments, workspace members, and the authenticated user context. The package is intended for Docmost deployments using the Community Edition and does not require an enterprise license according to the provided project description.

Read operations include listing spaces, retrieving space details, searching documentation, fetching page content as Markdown, listing recent or child pages, reading page comments, listing workspace members, and checking the current user and workspace. Write operations cover creating and updating spaces, creating and updating pages, adding or replacing page-level comments, duplicating pages, copying pages between spaces, and moving pages within or across spaces.

How it works

The npm entrypoint starts a Rust binary that handles MCP stdio traffic, local authentication, session handling, and calls to the Docmost API. On the first authenticated tool call, it starts a local login page on 127.0.0.1. A native authentication window is used when supported; otherwise, the system browser opens. Login uses the Docmost instance URL, email, and password.

After authentication, the server extracts the Docmost authToken cookie and reuses the saved session until the token is near expiration or rejected. The server checks the Docmost version once per session and adjusts behavior for supported version differences. It targets roughly the last year of Docmost releases, with stated support beginning around v0.22.

Setup and configuration

wisflux/docmost-local-mcp MCP server requires Node.js 18 or newer, a reachable Docmost instance, and email/password authentication enabled in that instance. Run it with npx -y @wisflux/docmost-local-mcp. The Docmost URL can be supplied with --base-url=https://docs.example.com or through DOCMOST_BASE_URL. If neither is supplied, the interactive login flow asks for the URL.

MCP clients configure the server as a local stdio process using npx and the package name. Claude Desktop uses its claude_desktop_config.json; Cursor uses a global or project .cursor/mcp.json; and VS Code GitHub Copilot uses .vscode/mcp.json with a top-level servers key. The README also documents a direct Claude Code registration command.

Local state is stored under ~/.docmost-local-mcp/. The state includes the last base URL and email, plus the saved session token and expiry. Credentials use the operating system keychain when available. If that storage is unavailable, the server uses encrypted local credential storage rather than plain-text credentials.

Tools and capabilities

The tool set supports:

• Space discovery and management with list_spaces, get_space, create_space, and update_space.
• Documentation search through search_docs, with search_pages retained as an alias.
• Page retrieval, listing, creation, editing, duplication, copying, and moving.
• Comment listing, creation, and body replacement.
• Workspace member listing and current-user lookup.
• Markdown page and comment bodies, including links, lists, code blocks, and other documented formatting. Pages additionally support tables and external image URLs.
• User and page mentions through user: and page: links in Markdown.

Limitations and notes

Page body updates require Docmost v0.70.0 or newer. On older versions, title changes work, but REST body updates may be ignored; the server reports this behavior and recommends page creation for persisted bodies. Inline comments attached to text selections are outside the REST-based implementation. Uploaded files and images are not supported, although pages can reference external image URLs. Native authentication depends on platform components: Windows needs WebView2, and Linux desktop environments need WebKitGTK. Browser fallback is available when the native webview is unavailable.