Skip to main content
Glama
Sign In
DocuPipe MCP server

DocuPipe MCP server

Official
by DocuPipe
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to DocuPipe MCP server

No user-submitted related servers found.

    Related Servers

    • AnyDoc

      xianhong1208
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables document conversion and processing through MCP, including Office/PDF/Markdown conversions, OCR, and PDF operations like split, rotate, encrypt, and extract.
      MIT
    • FynePDF MCP server

      FynePDF MCP serverofficial

      fynepdf
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to compress, merge, split, convert, OCR, redact, sign, create, and read PDFs with AI-assisted summaries and data extraction, plus local file upload/download and URL imports. Supports file libraries, job tracking, documentation search, and authenticated access via OAuth or API keys.
      1
      MIT
    • Aspose.PDF Cloud MCP Server

      Aspose.PDF Cloud MCP Serverofficial

      aspose-cloud
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables PDF conversion to DOC, merging multiple PDFs, reading document properties, and bundled storage file operations for complete upload-process-download workflows through MCP.
      -

    • Galmuri

      imguno
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to connect document sources, prepare searchable documents, and run RAG-ready lexical, vector, or hybrid search with account-scoped document access.
      40 PyPI
      BSD 3-Clause
    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.6/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools target distinct steps of the pipeline, and descriptions explicitly resolve the main overlaps (extract vs upload_document+standardize, get_standardization vs get_job/wait_for_jobs). Some residual ambiguity remains among the result-fetching tools (get_standardization, get_job, wait_for_jobs, get_excel_conversion), which all 'retrieve job output' in slightly different ways. An agent can still pick correctly by following the stated sequencing guidance.

    Naming Consistency4/5

    All names are lower snake_case, which is consistent and readable. The pattern is mostly verb_noun (upload_document, get_document, list_schemas, run_workflow), with a few bare verbs (extract, standardize, classify) that lack the resource noun but remain unambiguous. Minor deviation only.

    Tool Count4/5

    16 tools for a document-extraction platform covering upload, extraction, schemas, classification, splitting, workflows, Excel conversion and job polling is reasonable and each tool maps to a distinct capability. It sits just above the ideal 3-15 range, and a couple of job-polling tools could arguably be folded together. No obvious filler tools.

    Completeness4/5

    The end-to-end extraction lifecycle is well covered: upload, extract, retrieve text/results, schemas, classify, split, workflows, Excel export and job waiting. Gaps are minor: no delete_document or delete/update schema, and classes are read-only (list_classes with no create_class), but these are manageable via the web console rather than blocking agent workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources