Docmost Community Bridge
An MCP server that provides a bridge to self-hosted Docmost Community, enabling access to spaces, pages, and search, as well as creating and updating pages via Markdown. It also offers REST endpoints alongside MCP tools.
README
Docmost Community Bridge
An independent, AGPL-3.0 bridge that adds a small REST API and an MCP Streamable HTTP server to a self-hosted Docmost Community installation.
The bridge uses the authenticated routes already available in the AGPL Docmost Community server. It does not contain, copy, or depend on Docmost Enterprise API or MCP code.
Features
- List and create accessible spaces, and list pages.
- Read page content as Markdown, HTML, or JSON.
- Search accessible pages.
- Create pages from Markdown.
- Rename pages or append, prepend, and replace Markdown content.
- Use the same operations through REST or MCP.
- Protect every data endpoint with a static Bearer token.
- Run as a non-root user in Docker.
The bridge intentionally does not expose permanent deletion operations.
Requirements
- A reachable Docmost Community instance.
- A dedicated Docmost user account, preferably restricted to the spaces the automation is allowed to access.
- Docker, or Python 3.12 if running without Docker.
Configuration
| Variable | Description |
|---|---|
DOCMOST_URL |
Internal Docmost URL, such as http://docmost:3000. |
DOCMOST_EMAIL |
Email of the Docmost automation account. |
DOCMOST_PASSWORD |
Password of the Docmost automation account. |
BRIDGE_TOKEN |
Long random Bearer token required by REST and MCP clients. |
BRIDGE_PUBLIC_URL |
Public HTTPS URL used to allow the reverse-proxy host, such as https://docs.example.com. |
Never commit these values. Store them in a local .env file or a secrets
manager.
Docker Compose example
services:
docmost-bridge:
build: .
restart: unless-stopped
environment:
DOCMOST_URL: http://docmost:3000
DOCMOST_EMAIL: ${DOCMOST_EMAIL}
DOCMOST_PASSWORD: ${DOCMOST_PASSWORD}
BRIDGE_TOKEN: ${BRIDGE_TOKEN}
BRIDGE_PUBLIC_URL: https://docs.example.com
ports:
- "127.0.0.1:8000:8000"
Place the bridge on a Docker network shared with Docmost. Keep the published port bound to localhost and expose it through a TLS reverse proxy.
Endpoints
POST /mcp- MCP Streamable HTTP endpoint.GET /bridge/v1/spaces- list accessible spaces.POST /bridge/v1/spaces- create a space fromnameand optionaldescription,slug, orvisible_to_everyone(defaults totrue).DELETE /bridge/v1/spaces/{space_id}- permanently delete a space and its contents.GET|POST /bridge/v1/pages- list or create pages.GET|PATCH /bridge/v1/pages/{page_id}- read or update a page.POST /bridge/v1/pages/{page_id}/move- move a page to another space.GET /bridge/v1/search?q=...- search pages.GET /health- public container health check.
All endpoints except /health require this header:
Authorization: Bearer YOUR_BRIDGE_TOKEN
REST examples
curl -H "Authorization: Bearer $BRIDGE_TOKEN" \
https://docs.example.com/bridge/v1/spaces
curl -X POST \
-H "Authorization: Bearer $BRIDGE_TOKEN" \
-H "Content-Type: application/json" \
-d '{"space_id":"SPACE_UUID","title":"Meeting notes","content":"# Notes"}' \
https://docs.example.com/bridge/v1/pages
MCP client configuration
Configure an MCP client with:
- Transport: Streamable HTTP
- URL:
https://docs.example.com/mcp - Header:
Authorization: Bearer YOUR_BRIDGE_TOKEN
Available MCP tools:
docmost_healthlist_spacescreate_spacelist_pagesget_pagesearch_pagescreate_pageupdate_pagemove_page_to_space
Security notes
- The bridge acts with the permissions of
DOCMOST_EMAIL. - Use a dedicated Docmost account instead of a workspace owner in production.
- Use a long random Bearer token and rotate it if it is disclosed.
- Do not expose port
8000directly to the Internet. - Terminate HTTPS at a trusted reverse proxy.
License
This project is licensed under the GNU Affero General Public License v3.0. See LICENSE.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.