Summary
The whole surface is one call with one parameter, so there is nothing to configure and nothing to choose.
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. Which material an answer is drawn from is settled by the server rather than by the caller, so this fits a fixed corpus that the reader already knows and not an ad-hoc lookup across several. 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 documentation endpoint: query-docs takes a question and answers it.
What you get
- query-docs takes a question in natural language through its question parameter and returns the answer.
Requirements
Nothing to supply — no account, no key and no environment variable.
Setup effort
One command — npx -y mcp-docs-provider