Skip to main content
Glama

Related Servers

Alternatives to ParseRail MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Enables Claude and other MCP-compatible agents to process documents, extract structured data, detect PII, and export LLM-ready datasets through natural language tool calls.
      8
      63 PyPI
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables document ingestion and typed knowledge graph queries through Claude MCP tools, allowing agents to extract, store, and retrieve typed entities and relations from documents.
      2
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI clients like Claude to process documents (invoices, passports, etc.) via the DocuProx API, with tools for submitting jobs, checking status, and retrieving results.
      5
      9 npm
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to access document processing tools for extracting text, generating summaries, and identifying skills via MCP.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables querying enterprise documents (DOCX, PDF, PPTX) using natural language, with hybrid search and MCP integration for Claude Desktop and other agents.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables document parsing into structured, confidence-scored fields via the scan tool, working with any MCP host like Claude Desktop or Cursor.
      1
      92 npm
      MIT

    TDQS

    B3.3/5.0

    Scored across 41 tools

    Disambiguation3/5

    Most tools have distinct target use cases, but there are several overlapping pairs: summarize/minutes, classify/categorize, parse/invoice/receipt, and reply/outreach/review_reply. Reading the descriptions disambiguates them, but an agent is likely to need to compare closely before selecting.

    Naming Consistency3/5

    The parserail_ prefix and snake_case style are consistent, which helps. However, the suffix convention is mixed: bare verbs (parse, split, rewrite), bare nouns (invoice, receipt, memory), and noun-first compounds (po_match, review_reply, product_copy), so there is no predictable verb_noun pattern.

    Tool Count2/5

    At 41 tools, this is far beyond the typical well-scoped 3-15 tool range. Each endpoint may earn its place in the underlying API, but the MCP surface is too heavy for an agent to navigate easily. It feels like a full API dump rather than a curated set.

    Completeness3/5

    For a broad all-purpose AI-processing server, coverage is extensive: documents, audio, images, memory, outreach, finance, and account status are all present. However, because the domain is sprawling and many tools are one-shot generation or dead-end workflows, there is no clear lifecycle for created artifacts. Minor gaps like translation or custom voice selection are noticeable but not severe.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues