HIAI_DOCS_URL — Base URL of your running self-hosted DocsMint REST API, for example http://localhost:50700. For Cloud MCP, use the Streamable HTTP remote below.
HIAI_DOCS_API_KEY — Create an API key in your self-hosted DocsMint browser UI. The stdio bridge uses it only with your own API; it does not install the Cloud OAuth server. Prefer workspace-bound or category-scoped credentials.
ปุ่ม Claude ด้านบนจะเปิด Claude พร้อมกรอกชื่อและ URL ให้แล้ว คุณยังต้องยืนยันที่นั่นเอง
Turn your documents into knowledge you and your AI agents can use.
Write and organize notes, guides, and project documentation in one workspace.
Find answers with search that understands related concepts, then give your
agents access to the same documents through MCP, REST, the SDK, or CLI.
Connect DocsMint Cloud to get started without
operating the stack, or to run the
Apache-2.0 application on your own infrastructure.
Open-source knowledge base for people and AI agents. Rich-text editing, hybrid search, GraphRAG, and MCP. Self-host with Docker or use DocsMint Cloud.
Connect DocsMint Cloud instantly or run the self-hosted stdio bridge against
your own DocsMint API. Both paths give agents access to persistent knowledge;
the self-hosted bridge exposes 22 focused tools covering all 31 existing operations plus bounded batch actions and direct workspace-item inspection, with 2 prompts and 3 resources.
Recommended: DocsMint Cloud setup.
No server installation is required. Sign up or log in, choose your workspace,
and follow your client's connection instructions. OAuth-capable clients use
browser consent; API-key clients create an MCP/API credential in the authenticated
browser UI. Hosted MCP follows your plan and workspace permissions. Prefer
workspace-bound or category-scoped credentials.
The Cloud endpoint is https://docsmint.com/mcp (Streamable HTTP). OAuth-capable
clients discover the hosted resource and authorization-server metadata; current
authorization and client-connection methods are described in the
DocsMint Cloud setup guide.
Browser consent binds access to the selected workspaces, optional categories, and requested scopes.
DocsMint Cloud 1.1.9 and later supports hourly access tokens and rotating refresh tokens for up to
30 days from authorization when the client supports renewal. Existing connections need one reconnect
to enable refresh; clients without refresh support still reconnect after access expires.
API-key clients can instead send
Authorization: Bearer <key> with an MCP/API credential created in the authenticated
browser UI. Credentials cannot create or elevate other credentials; lifecycle
management belongs to the signed-in browser session.
Self-hosted alternative: run DocsMint with Docker, create an API
key in its browser UI, and configure HIAI_DOCS_URL and HIAI_DOCS_API_KEY for
npx --yes --package @hiai-gg/docsmint docsmint-mcp. Install Bun 1.4.0 or
later to execute the published binary. The npm package is a stdio bridge to
your own API; it does not install the DocsMint application or Cloud OAuth server.
See the MCP guide
for client configuration. The Glama OSS Server listing
describes this bridge; the hosted DocsMint Cloud Connector
is a separate listing.
Why DocsMint?
Keep knowledge easy to edit. Use a rich visual editor or Markdown;
organize documents with folders, categories, and tags.
Find the document you mean. Search combines keywords, meaning, typo
tolerance, and graph relationships across languages.
Keep agents close to the source. Let your tools search, read, and update
the same knowledge through MCP, REST, a typed SDK, and CLI.
Choose what an integration can access. Category keys grant explicit
read, edit, and write permissions for a defined part of your library.
Keep retrieval up to date. Document edits and metadata changes refresh
the search index automatically in the background.
Choose how you run it. Use managed DocsMint or
self-host the application, database, search, queues, and files.
What's new in 2.0.4?
Hosted MCP integrations can discover granted workspaces, including empty spaces, with
list_workspace_structure(kind="workspaces") and select one with the optional
workspaceId argument. The catalog remains 22 tools. Host authorization hooks preserve
the connection's existing workspace/category boundaries. Multi-scope reads carry labeled
results and independent pagination. Existing single-scope calls remain compatible.
The OSS frontend adopts SvelteKit 3; dependency updates resolve the current security
audit findings. No database migration is required. See the
2.0.4 release notes.
Previous release: 1.0.3
Make MCP tool selection clearer: use a single-document tool for one document
and batch_documents when multiple explicit IDs need the same action.
Keep the 22-tool catalog, all 31 underlying operations, input schemas,
authorization, and stdio behavior unchanged. The LobeHub tool descriptions
match the released MCP catalog.
DocsMint Cloud remains a separate hosted Connector. Cloud descriptions
change only when the hosted service adopts this package version.
Prefer an assisted self-hosted setup? Give your coding agent this prompt.
You will need Docker and a choice of AI provider.
Install DocsMint from https://github.com/HiAi-gg/docsmint.
Verify Docker and Docker Compose v2, clone the repository, and run
`bash scripts/quickstart.sh`. Do not print or commit .env. Ask me to enter only
an OpenRouter key or select Ollama, then run quickstart again. Verify
http://localhost:50701, http://localhost:50700/api/health, and
`docker compose ps`. Do not replace Bun, rewrite migrations, disable GraphRAG,
or delete volumes.
After startup, open http://localhost:50701 and create the first account.
For manual installation, use the Docker quickstart below.
git clone https://github.com/HiAi-gg/docsmint.git
cd docsmint
bash scripts/quickstart.sh
On its first run, the script creates an ignored root .env, generates the
database, authentication, and storage secrets, builds the PostgreSQL image,
applies migrations, and starts the complete application.
Published application images are on
Docker Hub. There is no untagged
latest image; pull the role-specific tags:
Use versioned tags api-v1.0.3, web-v1.0.3, and caddy-v1.0.3 for
reproducible deploys. Caddy is the supporting reverse proxy with rate limiting;
it is separate from the API and web application. The quickstart still builds the Compose stack from this repository so PostgreSQL,
Redis, and SeaweedFS start together with the application.
For OpenRouter, add one value to .env and run the script again:
OPENROUTER_API_KEY=sk-or-your-key
For Ollama, select the local provider instead:
AI_PROVIDER=ollama
OLLAMA_PORT=11434
Then make sure the configured local models are available:
Create a category or folder and add or import a document.
Wait for the document pipeline to finish chunking and embedding.
Search using an exact phrase, a related concept, an alternate language, or
a misspelling.
Open Settings → API when you want to connect a CLI, MCP client, or
external application.
The canonical local ports are:
Service
Port
Web application
50701
REST API
50700
PostgreSQL
5437
Redis
6384
SeaweedFS S3 gateway
50702
SeaweedFS filer UI
50703
See Deployment for domains, TLS, provider tuning,
backups, and production operation.
Embedding provider URLs, models, and credentials are deployment configuration.
They are never stored in browser settings or local storage.
Use DocsMint from the terminal
One public package, @hiai-gg/docsmint, includes the TypeScript SDK,
docsmint CLI, and docsmint-mcp bridge. These clients connect to a running
DocsMint deployment; use the Docker quickstart to install the self-hosted server.
Credentials can also be supplied through HIAI_DOCS_URL and
HIAI_DOCS_API_KEY. See the CLI guide for every
command and configuration precedence.
Connect an MCP client
Give agents a secure path to search, read, and maintain your knowledge without
database or filesystem access. DocsMint publishes MCP tools plus ready-made
research prompts, scoped resources, and a document-manager skill.
Hosted DocsMint
Connect directly to the managed Streamable HTTP endpoint. Keep the API key in
an environment variable rather than writing it into client configuration:
Category keys let you expose only the documents and operations an agent needs.
Use a global key only for trusted owner-wide automation. See the
complete MCP reference for Bun, npm, local
checkout, all tools, prompts, resources, permissions, and REST mappings.
TypeScript SDK
bun add @hiai-gg/docsmint
import { DocsClient } from '@hiai-gg/docsmint';
const docs = new DocsClient({
baseUrl: 'http://localhost:50700',
apiKey: process.env.HIAI_DOCS_API_KEY,
});
const created = await docs.createDoc({
title: 'Meeting notes',
content: '# Agenda',
});
const results = await docs.search('what did we decide?');
console.log(created.id, results.items);
The SDK is a typed fetch client with retries for transient failures and
idempotent document creation retries. See the
SDK reference and REST API.
API keys and integrations
Create and revoke integration keys from Settings → API.
Credential
Intended use
Access
Global API key
Trusted owner-wide CLI, MCP, SDK, or service
All owner content
Category key
Least-privilege agent or product integration
One category with selected permissions
Operator key
Administration and reindex operations
/api/admin/* only
Category permissions are explicit and non-hierarchical:
read permits list, read, search, and export;
edit permits updates to existing content, attachments, and versions;
write permits create, move, delete, share, and publish operations.
Combine permissions when an integration needs more than one capability.
API-key lifecycle operations require the owning browser session; an API key
cannot create or elevate another key. Server-to-server integrations are not
affected by browser CORS. Browser integrations must add their exact origin to
CORS_ORIGINS.
What is included?
Documents use structured TipTap JSON as canonical content. Markdown is the
source-editing, import, and export format. The same document store serves the
web application and public integration interfaces.
frontend/ SvelteKit workspace and TipTap editor
backend/ Elysia REST API, search, workers, and authentication
packages/db/ Drizzle schema and migrations
packages/sdk/ Typed API client
packages/cli/ Terminal client
packages/mcp-server/ MCP stdio server
postgres/ PostgreSQL image with vector and graph extensions
The Docker deployment runs:
Web — document editor, folders, categories, sharing, settings, and search;
API — documents, attachments, versions, keys, search, and administration;
PostgreSQL 18 — relational data, pgvector/pgvectorscale vectors, and the
Apache AGE graph in one database;
Redis 8 — BullMQ queues, caching, retries, and job recovery;
SeaweedFS — S3-compatible attachment storage.
How search works
Every document save schedules background work. Content is chunked, changed
chunks are embedded, and the completed generation is activated atomically. The
previous valid generation remains searchable if a provider call fails.
Search combines exact title matches, multilingual lexical search, typo-tolerant
fuzzy matching, semantic vectors, adaptive query expansion, and Apache AGE
graph neighbors. Reciprocal rank fusion combines the channels without allowing
one weak provider result to dominate. A cross-encoder then reranks the fused
prefix against the original query (Voyage rerank-2.5 by default). On a labeled
24-document corpus that moved MRR 0.969 → 1.000 and nDCG@10 0.958 → 0.986
versus RRF-only. Rerank, expansion, embeddings, and AGE failures keep the
remaining channels. Authorization is applied before retrieval and again before
results are returned.
GraphRAG is part of the normal search path in the reference configuration. It
extracts entities after embeddings are ready and finds related documents beyond
direct keyword or vector similarity. It degrades gracefully when an external
model is unavailable.
ตรวจสอบล่าสุดเมื่อ 2026-11-14 Open-source knowledge base for people and AI agents. Rich-text editing, hybrid search, GraphRAG, and MCP. Self-host with Docker or use DocsMint Cloud.