Skip to main content
Glama
lazyants

transkribus-mcp-server

by lazyants
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to transkribus-mcp-server

No user-submitted related servers found.

    Related Servers

    • paperless-mcp

      baruchiro
      A
      license
      B
      quality
      A
      maintenance
      An MCP (Model Context Protocol) server for interacting with a Paperless-NGX API server. This server provides tools for managing documents, tags, correspondents, and document types in your Paperless-NGX instance.
      44
      730 npm
      141
      TypeScript
      ISC

    • MCP REST API Server

      vinaykp
      F
      license
      Not graded
      quality
      D
      maintenance
      A server implementation of the Model Context Protocol (MCP) that provides REST API endpoints for managing and interacting with MCP resources.
      -

    • Devonthink MCP Server

      dvcrn
      A
      license
      Not graded
      quality
      A
      maintenance
      This MCP server provides access to DEVONthink functionality via the Model Context Protocol (MCP). It enables listing, searching, creating, modifying, and managing records and databases in DEVONthink Pro on macOS.
      26 npm
      105
      GPL 3.0

    • Thoth MCP Server

      gethibiki
      A
      license
      A
      quality
      C
      maintenance
      Model Context Protocol (MCP) server for Thoth content creation platform. Enables AI assistants and tools to create and retrieve content through Thoth's API.
      6
      46 npm
      2
      MIT
    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

    C2.4/5.0

    Scored across 304 tools

    Disambiguation1/5

    Many tools have identical or near-identical purposes, e.g. transkribus_coll_remove_doc and transkribus_doc_remove_from_collection both say 'Remove a document from a collection without deleting it'; transkribus_coll_user_remove and transkribus_coll_remove_user duplicate user removal; and multiple metadata update endpoints exist (transkribus_doc_update_metadata vs transkribus_doc_update_metadata_v2). An agent cannot reliably select the correct tool without external knowledge.

    Naming Consistency3/5

    All names use snake_case with a consistent transkribus_ prefix, but action ordering and suffixing are inconsistent: transkribus_coll_list vs transkribus_coll_list_paged vs transkribus_coll_list_xml; transkribus_doc_get_metadata vs transkribus_doc_update_metadata_v2; and legacy/new variants coexist. The pattern is readable but not fully predictable.

    Tool Count1/5

    304 tools is an extreme mismatch for an agent-friendly MCP server. Even accounting for a large underlying API, this vastly exceeds the 50+ threshold where tool selection becomes impractical, and many tools are redundant rather than essential.

    Completeness5/5

    The surface covers collections, documents, pages, transcripts, models, recognition, training, search, jobs, users, admin, credits, crowdsourcing, e-learning, and uploads, with create/get/update/delete operations for most resources. It appears to wrap the entire Transkribus API exhaustively, leaving no obvious domain gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources