Docmost MCP Server

Docmost MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. MCP server for self-hosted Docmost (Community Edition) — read & write your wiki from Claude, Cursor, and VS Code.

What you get

MCP server for Docmost that is built for self-hosted instances, especially deployments that do not have an enterprise license but still want reliable MCP access from local IDEs and AI tools.

• Works against your own Docmost base URL
• Uses Docmost email/password authentication
• Stores session state locally for reuse
• Opens a local auth flow instead of requiring a separate hosted control plane
• Ships as a simple npx entrypoint for easy IDE integration

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

What the assistant can call

Once Docmost is connected, these are the calls the assistant has available:

• list_spaces — list available Docmost spaces
• get_space — fetch details for a specific space
• search_docs — search documentation, optionally scoped to a space
• search_pages — backward-compatible alias for search_docs
• get_page — fetch a page and return its content as Markdown
• list_pages — list recent pages in a space
• list_child_pages — list child pages for a parent page ID
• get_comments — list comments for a page
• list_workspace_members — list workspace members
• get_current_user — fetch the authenticated user and workspace context
• create_page — create a new page in a space from Markdown content
• update_page — update an existing page's title and/or Markdown content

Configuration and credentials

You will need one environment variable: DOCMOST_BASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js 18 or newer for npx - A reachable Docmost instance - Email/password authentication enabled in that Docmost instance

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Docmost.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the docmost mcp server does with a few real requests.

Choosing this one

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Docmost's toolset — list_spaces, get_space, search_docs and 11 more — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.