Doc Lib MCP Server

Connect Doc Lib MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. A Model Context Protocol (MCP) server for document ingestion, chunking, semantic search, and note management. The doc lib mcp mcp server is what makes that connection.

Installation

The server ships on npm as @modelcontextprotocol/inspector, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• add-note — Add a new note to the in-memory note store
• Arguments — name (string), content (string)
• ingest-string — Ingest and chunk a markdown or plain text string provided via message
• ingest-markdown — Ingest and chunk a markdown (.md) file
• ingest-python — Ingest and chunk a Python (.py) file
• ingest-openapi — Ingest and chunk an OpenAPI JSON file
• ingest-html — Ingest and chunk an HTML file
• ingest-html-url — Ingest and chunk HTML content from a URL (optionally using Playwright for dynamic content)
• smart_ingestion — Extracts all technically relevant content from a file using Gemini, then chunks it using robust markdown logic
• search-chunks — Semantic search over ingested content
• delete-source — Delete all chunks from a given source
• delete-chunk-by-id — Delete one or more chunks by id

Credentials and setup notes

Configuration is passed through the environment: OLLAMA_HOST, RERANKER_MODEL_PATH, UV_PUBLISH_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Doc Lib MCP.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Where it fits

Plenty of planning and project tracking 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. Doc Lib MCP's toolset — add-note, Arguments, ingest-string and 11 more — is a fair guide to whether it matches your workflow. It is maintained by shifusen329; 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.