Skip to main content
Glama

Vellum

An MCP server that inspects generated documents (.docx, .pdf) before they reach the user — extracting hard, measurable facts about structure, typography, spacing, and language correctness, so an AI assistant can catch its own formatting mistakes instead of shipping them.

Built against the 2026-07-28 MCP specification. See docs/architecture.md for the full design rationale.

Why

Document-generation skills produce .docx/.pptx/.pdf output, but nothing automatically verifies the result is well-formed: heading levels can be skipped, fonts can be inconsistent, spacing can drift, grammar errors pass through silently. Vellum is a verification layer, not a generator.

Related MCP server: Visual Document Forensics MCP Server

Core principle

The server extracts facts. The model makes judgments.

Vellum never says "this is wrong." It says "here is what is actually true, and here is what is statistically anomalous relative to the rest of the document." Deciding whether a given value is appropriate for a line's role in the document (title vs. caption vs. body) is semantic judgment that stays with the calling model, which has the document's full context — the server does not, and should not try to.

Tools

Tool

Purpose

check_docx_structure

Heading hierarchy, TOC consistency, numbering, captions

check_docx_typography

Per-paragraph resolved font/size/weight/spacing (full style-inheritance chain resolved) + outlier flags

check_pdf_layout

Per-character coordinates, baseline spacing, margin/indent consistency, font inventory, substitution detection, intra-line collision flags

check_language

LanguageTool findings with paragraph/offset anchors

check_filename_consistency

Flags filename tokens (company/role/version/date) absent from the document body

full_report

Runs all applicable checks, returns a report://{file_id} resource

Every tool returns structured facts plus anomaly flags — never a verdict.

Every tool accepts the document either as a filesystem path or as inline content_base64 (with filename required alongside it) — useful when a document only exists in the conversation (e.g. uploaded directly in a chat interface) rather than saved to disk first. Exactly one of the two input forms must be given.

Status

All six tools (check_docx_structure, check_docx_typography, check_pdf_layout, check_language, check_filename_consistency, full_report) are fully implemented, unit-tested, and validated against a golden set of fixtures with known planted defects. The full MCP surface — resources, prompts, elicitation, cache hints, OAuth 2.1 resource-server auth for the HTTP transport, and correct error semantics — is built and tested (163+ tests passing). See docs/architecture.md and PROGRESS.md for the detailed build history and current open items. Packaging/publication (Phase 7) is in progress — not yet released to PyPI.

Install

git clone https://github.com/Nasser9892/vellum-mcp.git
cd vellum-mcp
pip install -e ".[dev]"

Requires a local LanguageTool instance for check_language — see docs/architecture.md for setup.

Usage (Claude Desktop / any MCP stdio client)

Add to your MCP client config (see examples/claude_desktop_config.json):

{
  "mcpServers": {
    "vellum": {
      "command": "vellum-mcp"
    }
  }
}

Development

pip install -e ".[dev]"
pytest                          # unit + integration tests
mcp dev src/vellum_mcp/server.py  # run under MCP Inspector

Golden-set fixtures (sample .docx/.pdf files with deliberately planted defects) live in golden_set/. All checks are validated against these before being trusted — see docs/architecture.md for the discipline.

Validated against MCP Inspector (mcp dev src/vellum_mcp/server.py) and tested against two real MCP clients: Claude Desktop (examples/claude_desktop_config.json) and Cursor (~/.cursor/mcp.json, same {"mcpServers": {"vellum": {"command": "vellum-mcp"}}} shape).

Spec conformance

  • All primitives: tools, resources, prompts (not tools-only)

  • Stateless core — no reliance on Mcp-Session-Id

  • Elicitation via MRTR (InputRequiredResult / inputRequests / inputResponses)

  • OAuth 2.1 resource-server posture for the HTTP transport (RFC 9728, RFC 8707, RFC 9207; CIMD over deprecated DCR)

  • Tasks extension (io.modelcontextprotocol/tasks) for long-running analysis

  • Correct error codes (-32602 for not-found, -32020 for header-bound violations)

  • No use of deprecated roots/sampling/logging primitives

License

MIT — see LICENSE.

Available Tools

6 tools
check_docx_structureA

Extract structural facts from a .docx file: heading hierarchy, TOC consistency, header/footer consistency, page-numbering-field presence, orphaned/empty styles, list-numbering restarts, and image/table caption presence + sequencing. Returns facts and anomaly flags only — never a verdict on correctness (see the server's global instructions).

Accepts the document either as a filesystem path OR as inline content_base64 (with filename required alongside it) — useful when the .docx only exists in the conversation (e.g. a file uploaded directly in chat) rather than saved to disk. Exactly one of the two input forms must be given.

Inputs: path, filename, content_base64. Returns: Output schema for check_docx_structure (brief §4.1).

check_docx_typographyA

Per-paragraph resolved font/size/weight (full style-chain resolved, with provenance per property) plus flags for paragraphs whose resolved combination is statistically unique in the document, and for paragraphs whose runs don't all resolve to the same combination. Facts and anomaly flags only — never a verdict on what formatting should be (see the server's global instructions).

Accepts the document either as a filesystem path OR as inline content_base64 (with filename required alongside it) — for a .docx that only exists in the conversation rather than saved to disk. Exactly one of the two input forms must be given.

Inputs: path, filename, content_base64. Returns: Output schema for check_docx_typography (brief §4.3).

check_filename_consistencyA

Tokenizes the filename (stripping extension, separators, common document-type stopwords, and — heuristically — the document owner's own leading First/Last name tokens), then flags any remaining proper-noun-like token that doesn't appear anywhere in the extracted document text. Facts only: presence or absence — never a verdict on whether a mismatch is intentional (brief §3, §4.4).

Accepts the document either as a filesystem path OR as inline content_base64 (with filename required alongside it — this is exactly the name that gets tokenized, so pass the file's real name here, not a placeholder). Exactly one of the two input forms must be given.

Inputs: path, filename, content_base64. Returns: Output schema for check_filename_consistency (brief §4.4).

check_languageA

Grammar/spelling/punctuation/style findings via a local LanguageTool instance, with paragraph/offset anchors so the model can locate and fix issues precisely. If lang isn't given and the language can't be auto-detected with confidence, asks the client which language it is (MRTR elicitation) rather than guessing. Facts and LanguageTool's own suggestions only — never a rewritten "corrected" version of the text.

Accepts exactly one of: a filesystem path, raw text, or inline content_base64 (with filename required alongside it) for a .docx/.pdf that only exists in the conversation rather than saved to disk.

Inputs: lang, path, text, filename, +1 more. Returns: Output schema for check_language (brief §4.2, §5.3). `language` is a genuine th…

check_pdf_layoutA

Per-character font/size/coordinates, computed baseline spacing, margin/indent consistency, font inventory, declared-vs-embedded font substitution detection, and intra-line horizontal collision flags (tab-stop-overflow signature). Facts and anomaly flags only — never a verdict on correctness (see the server's global instructions).

Accepts the document either as a filesystem path OR as inline content_base64 (with filename required alongside it) — for a .pdf that only exists in the conversation rather than saved to disk. Exactly one of the two input forms must be given.

Inputs: path, filename, content_base64. Returns: Output schema for check_pdf_layout (brief §4.3 PDF half).

full_reportA

Runs every applicable check for the document (format auto- detected from the file extension: .docx or .pdf) and returns an aggregated report as a report://{file_id} resource URI, plus an inline summary. profile selects a subset: "full" (default, every applicable check) or "typography_only" (just the format's typography/layout check — check_docx_typography for .docx, check_pdf_layout for .pdf). The full persisted report can be re-read later via the returned URI without re-running analysis (brief §5.1/§5.2). Facts and anomaly flags only, aggregated from each check's own output — never a merged verdict (brief §3, see the server's global instructions).

Accepts the document either as a filesystem path OR as inline content_base64 (with filename required alongside it) — for a file that only exists in the conversation rather than saved to disk. Exactly one of the two input forms must be given.

Inputs: path, profile, filename, content_base64. Returns: Output schema for full_report (brief §6). This is the inline summary the tool c…

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each check targets a clearly distinct concern: DOCX structure, DOCX typography, PDF layout, language, filename consistency, and the aggregated report. The only potentially overlapping tool, full_report, is explicitly an aggregator rather than a separate analysis, so an agent can reliably select the right tool.

    Naming Consistency4/5

    Five of the six tools follow a consistent check_<target>_<aspect> pattern, making the set highly predictable. The one deviation is full_report, which breaks the check_ prefix but is still descriptive and unlikely to confuse.

    Tool Count5/5

    Six tools is a well-scoped size for a document-inspection server. Each tool covers a distinct aspect of analysis with no redundant or extraneous additions.

    Completeness5/5

    The tool set covers the major inspection needs for DOCX and PDF documents: structure, typography/layout, language, filename consistency, and a full aggregated report. Since the server is explicitly analysis-only and returns facts rather than edits, there are no obvious missing operations within its stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables deterministic visual and structural analysis of PDF and DOCX documents, extracting measurable evidence such as blur, OCR confidence, and image anomalies for auditable forensic workflows.
      1
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to generate format-stable, editable Word DOCX documents from structured content and reusable templates, with document type recognition, schema retrieval, template rendering, validation, and conservative fixes.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables agents to check AI-written documents against a fixed facts file for number accuracy and context, listed skills, blocked phrases, and tone warnings, returning structured reports and exposing allowed facts, skills, and blocked phrases.
      2
      Apache 2.0