Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
OPENAI_API_KEYNoSet this instead of ANTHROPIC_API_KEY to use OpenAI models as the model provider.
ANTHROPIC_API_KEYNoYour model provider's key for Claude models (the default provider), e.g. passed with `claude mcp add readanydoc -e ANTHROPIC_API_KEY=your-key -- readanydoc mcp`.
READANYDOC_REFUSAL_READERNoOptional second model used for pages that the model provider declines (content filtering); without it those pages fall back to plain OCR text at low confidence.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

ReadAnyDoc reads PDFs, scans, photos and Office files. Use parse_document to get a document's text, tables and layout as Markdown. Use extract_fields with a JSON Schema to get typed values; every value comes with citations (the text and page box it was read from). Paths must be files on this computer. Confidence is 'high' or 'low'; check warnings before trusting a result.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
parse_documentA

Parse a local document (PDF, image, DOCX, XLSX, PPTX ...) into Markdown.

path: file on this computer. mode: "engine" (default, most accurate) or "model-only" (one model read per
page, faster). pages: 1-based page numbers to read; all pages when omitted.
extract_fieldsB

Extract structured values from a local document into a JSON Schema, with citations.

schema: a JSON Schema object (type "object" with properties). instructions: optional guidance for the
extraction. array_extract: true for long lists or tables that span many pages.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 2 tools

Disambiguation4/5

parse_document converts a document to Markdown, while extract_fields pulls structured values into a JSON Schema, so their outputs and use cases are clearly different. There is mild overlap since extraction implicitly parses the same file, but the descriptions make the boundary (freeform text vs. schema-bound values) reasonably clear.

Naming Consistency5/5

Both tools follow the same snake_case verb_noun convention (parse_document, extract_fields) with no deviations. The naming is predictable and immediately readable.

Tool Count4/5

Two tools is on the thin side, but for a focused document-reading server they cover the two core workflows: raw conversion and structured extraction. Both tools earn their place, though a third (e.g. batch or format listing) could add value.

Completeness4/5

The surface covers the main lifecycle: read a document and extract structured data with citations, across many formats and page ranges. Minor gaps exist, such as no batch/multi-file processing, no remote URL input, and no chunking guidance for very large documents.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues