Skip to main content
Glama
PageTranslate MCP Server

PageTranslate MCP Server

Official

Related Servers

Alternatives to PageTranslate MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to turn PDFs, scans, photos, Office files, and HTML into readable text through signed-URL uploads and batch jobs, using fast page-level OCR or accurate vision-reconciled transcription. Jobs run independently, support page-by-page reading and downloads, and can be deployed securely with Entra authentication.
      29 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents and users to process documents through natural language, supporting PDF operations like text extraction, redaction, splitting, form filling, annotations, and content search.
      60 npm
      62
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables Claude, Cursor, and other AI agents to read PDFs and scans by submitting documents to an OCR API and saving results as JSON, text, Markdown, or hOCR files. Includes quoting, job status, and human-confirmed budget controls for safe document processing.
      7
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides AI agents with comprehensive document parsing capabilities including PDF text extraction, OCR, HTML-to-markdown conversion, table extraction, and summarization, optimized for agent workflows.
      72 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients such as Claude Desktop, Claude Code and Cursor to OCR local scanned PDFs and images in 100+ languages, returning the extracted text or a searchable PDF. It also lets agents check document status, list recent documents and delete them.
      6
      89 PyPI
      MIT

    TDQS

    A3.9/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool maps to a distinct step in a single linear workflow: upload, quote/inspect status, start/pay, list, and download. The pairs that could overlap (get_translation vs list_translations) are clearly separated by singular-job status versus account-wide listing, and download_translation only applies to completed jobs.

    Naming Consistency4/5

    All names follow a consistent snake_case verb_noun pattern (download/upload/start/get/list + noun). The only minor deviation is the noun choice: four tools use 'translation' while upload_document uses 'document', which is semantically justified but breaks the single-resource naming rhythm.

    Tool Count5/5

    Five tools is exactly the size of the domain: one per workflow stage, with no redundant or filler operations. Nothing feels thin or padded for a file-translation service.

    Completeness4/5

    The full lifecycle is covered: upload with pricing, start with payment fallback, status polling, history listing, and result download. The notable gap is the absence of cancel or delete operations for jobs, so an agent cannot abort a running translation or clean up uploaded files.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues