MCP_Documents
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOCS_API_KEY | No | Bearer token for authenticating HTTP requests to the server when running behind a reverse proxy. | |
| DOCS_TOKENS_FILE | No | Path to a file containing additional bearer tokens for HTTP authentication. | |
| MCP_CONSTRAINED_MODE | No | Set to '1' to tighten resource budgets on small hardware. | 0 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| probeB | Identify a document: format, pages, scanned or digital, what it holds. |
| outlineA | List headings and bookmarks with page anchors. Use before extract. |
| findA | Locate text: page numbers, counts, and a snippet each. Never a page. |
| extractB | Extract clean text for a page range. Bounded; refuses when too big. |
| extract_tablesC | Extract tables as rows. Says whether ruling lines or gaps were used. |
| read_pageC | Read one page: text, tables, and how each was obtained. |
| to_markdownB | Convert a document to markdown. Refuses when over the token budget. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
The tools are mostly distinct: find locates snippets, read_page returns one page, extract handles a page range, extract_tables targets tables, outline exposes structure, probe identifies the document, and to_markdown does full conversion. The only mild ambiguity is between extract and to_markdown, since both return document text and could be selected for similar high-level tasks.
Naming conventions are inconsistent: several bare verbs (find, extract, outline, probe), two verb_noun compounds (read_page, extract_tables), and one prepositional name (to_markdown). There is no shared prefix or pattern, though each name is readable on its own.
Seven tools is appropriate for a document-reading server: each one addresses a distinct need such as search, page reading, range extraction, tables, outline, probe, and conversion. The count feels neither thin nor bloated.
The set covers the main document workflow: identify, outline, search, read single pages, extract text and tables, and convert to Markdown. Minor gaps remain: scanned documents have no explicit OCR path, and to_markdown's token-budget refusal may require manual page-range reconstruction for very large documents.