DocsMint

What DocsMint MCP server does

DocsMint MCP server gives AI agents access to a DocsMint knowledge workspace through the Model Context Protocol. It covers document and workspace-item operations, folder and category organization, search, GraphRAG-related retrieval, and indexing. Agents can work with the same documents that users manage through DocsMint’s web application.

Access is scoped by workspace permissions and, where configured, category permissions. The available permission types include reading, editing, and writing. This makes the server suitable for connecting an agent to a defined portion of a documentation library instead of exposing the entire workspace by default.

The package is an MCP bridge, not the complete DocsMint application. Self-hosting the application requires the DocsMint Docker stack; the bridge then connects to that API.

How it works

The self-hosted bridge communicates with a DocsMint API and exposes 22 focused MCP tools covering 31 underlying operations. It also provides two prompts and three resources. For repeated operations on several explicitly selected documents, the catalog includes a bounded batch action; single-document work uses a separate document operation.

DocsMint MCP server supports stdio for local client connections. DocsMint Cloud offers a separate Streamable HTTP endpoint at https://docsmint.com/mcp, with access controlled by workspace selection, optional category scope, and requested permissions. OAuth-capable clients can use browser consent, while API-key clients can send a DocsMint MCP/API credential as a bearer token.

Search combines keyword, semantic, typo-tolerant, and graph-related retrieval according to the project description. Document and metadata changes update the search index in the background, so the server is intended for knowledge that changes over time.

Setup and configuration

The simplest route is DocsMint Cloud: sign in, choose a workspace, and follow the connection instructions for the MCP client. No local server installation is required. Hosted access follows the selected plan and workspace permissions.

For a self-hosted deployment, run DocsMint with Docker and create an API key in its browser interface. Then configure the bridge with the API URL and key:

• HIAI_DOCS_URL — URL of the DocsMint API.
• HIAI_DOCS_API_KEY — API key used by the bridge.

The published package can be started with npx --yes --package @hiai-gg/docsmint docsmint-mcp. Bun 1.3.14 or later is required to execute the published binary. The npm package does not install the DocsMint application or provide the Cloud OAuth service.

To run the application itself, the documented quickstart requires Docker Engine or Docker Desktop, Docker Compose v2, and either an OpenRouter API key or a local Ollama instance. The application exposes its web interface on port 50701 and its API health endpoint on port 50700 by default.

Tools and capabilities

The DocsMint MCP server catalog supports:

• Reading and changing documents.
• Applying scoped document actions to multiple explicit IDs.
• Inspecting workspace items directly.
• Organizing content with folders and categories.
• Searching the workspace using related concepts and graph relationships.
• Working with indexing and GraphRAG functions.
• Using two prompts and three resources alongside the tools.

The exact tool schemas and authorization behavior remain part of the released MCP catalog. Category keys can restrict credentials to a defined part of the library and grant separate read, edit, or write permissions.

Limitations and notes

DocsMint MCP server does not replace the DocsMint application. Self-hosted users must operate the application, database, search, queues, and file services separately from the MCP bridge. Cloud and self-hosted deployments are distinct paths with different connection methods.

Cloud access does not issue refresh tokens. Browser-managed credential lifecycle remains in the signed-in session, and credentials cannot create or elevate other credentials. Use workspace-bound or category-scoped credentials when narrower access is required.

The bridge requires a reachable DocsMint API and valid credentials. Its published package is designed for stdio; the hosted Cloud service is the Streamable HTTP option.