Skip to main content
Glama
okrapdf

okraPDF PDF MCP server

Official
by okrapdf
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to okraPDF PDF MCP server

No user-submitted related servers found.

    Related Servers

    • pdf-agent-mcp

      sanhua1
      F
      license
      Not graded
      quality
      D
      maintenance
      A local MCP server that extracts text-layer content from PDF files, enabling AI agents to inspect, extract text, outlines, and page content.
      -

    • dbv-pdf2md

      davidbuenov
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that converts PDFs to Markdown, reconstructing hidden hyperlinks and extracting images in reading order for AI agents.
      MIT

    • pdf-mcp

      I-CAN-hack
      A
      license
      A
      quality
      C
      maintenance
      An MCP server for reading, rendering, and searching PDF files, specifically optimized for LLMs to extract text, tables, and technical diagrams. It enables metadata retrieval, multi-format text extraction, and page-to-image rendering using PyMuPDF.
      5
      77
      MIT

    • MCP PDF Reader

      Saqib-Aziz007
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that enables AI assistants to read, search, and analyze PDF files from local paths or URLs. It provides tools for extracting specific page ranges, searching for terms, and retrieving document metadata.
      4
      20 npm
      1
      MIT

    • flint-slating

      ParkviewLab
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that reads PDFs and exposes them as structured Markdown, metadata, outlines, images, and tables to LLM consumers via tools like pdf_read_markdown and pdf_info.
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 27 tools

    Disambiguation2/5

    Many tools have overlapping purposes: view_document, view_pdf, review_extraction, inspect_html, view_structured, and view_html all present document content in different but easily confusable ways. The distinction between render_ui and create_view is also subtle, and the presence of internal poll/get tools adds noise. Despite verbose descriptions, an agent could pick the wrong tool without deep reading.

    Naming Consistency4/5

    Tool names almost all follow a verb_noun snake_case pattern (e.g., upload_document, verify_source, list_workflows). Minor deviations like 'interact' and the mix of view_/inspect_/review_ prefixes for similar actions slightly reduce consistency, but the overall convention is clear and predictable.

    Tool Count2/5

    27 tools is too many for a single server, especially with three tools explicitly marked as internal (poll_document_view, poll_view_commands, get_render_payload) and several near-duplicate view/render tools. The set feels bloated and would be challenging for an agent to navigate efficiently.

    Completeness4/5

    The server covers the core PDF workflow: upload/resolve, query via SQL/search, visual and structured views, verification and citation, plus workflow creation and monitoring. Missing explicit update/delete document operations, but most gaps can be worked around with execute_code or SQL, so the surface is reasonably complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources