query-docsLABSCO SUMMARY
The whole surface is one call with one parameter, and the only setting is the path to your docs.
query-docs is the only tool: there is no listing call, no source selection, and no parameter for scoping a question to a particular set of documents. Answers come from the one local markdown file you name when you launch it, not from anything the caller picks, so this fits a single set of docs you maintain yourself rather than an ad-hoc lookup across several; edits to that file need no rebuild. That narrowness is also what keeps it out of the way — one tool definition in the model's context, not a family of them.
What it is
A single-tool server over your own local markdown documentation: query-docs takes a question and answers it from that file.
What you get
- query-docs takes a question in natural language through its question parameter and returns the answer.
Requirements
No account or key — just the path to your own markdown documentation file, given as the server's last launch argument.
Setup effort
One command — npx -y mcp-docs-provider <YOUR_PATH_TO_DOCUMENTATION>
USE CASES
01
Getting a documentation answer without leaving the editor
Ask the question in the conversation and let the server answer from the documentation it serves.
1 tool
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool when we connected.
Requires
- npx on PATH
- A local markdown documentation file, passed as the last launch argument
CONTEXT COST
Light Standing cost
Rated by the size of the one tool definition that rides along on every turn
INSTALLATION
Connect your client
Server setup
Configuration file
JSON
{
"mcpServers": {
"mcp-docs-provider": {
"command": "npx",
"args": [
"-y",
"mcp-docs-provider",
"<YOUR_PATH_TO_DOCUMENTATION>"
]
}
}
}<YOUR_PATH_TO_DOCUMENTATION> is the path to your own markdown documentation file — the server answers from that file, and no rebuild is needed after you edit it.
npx
TERMINAL
npx -y mcp-docs-provider <YOUR_PATH_TO_DOCUMENTATION>
