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
      403 npm
      148
      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.
      7 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 overlap directly, e.g. transkribus_doc_get_stats vs transkribus_doc_get_stat, transkribus_doc_delete vs transkribus_doc_remove_from_collection vs transkribus_coll_remove_doc, and multiple recognition runners (run_htr_citlab, pylaia_recognize, run_atr, run_ocr, run_trhtr). An agent cannot reliably select the correct tool among these near-duplicates.

    Naming Consistency3/5

    The dominant pattern is transkribus_<domain>_<action>, but there are many deviations: HTTP-verb prefixes (post_, get_), suffixes like _v2, _old, _new, _paged, _xml, _by_type vs _by_id, singular/plural inconsistencies (get_stat vs get_stats), and mixed verbs (add, create, modify, update). The naming is mostly readable but not fully consistent.

    Tool Count1/5

    304 tools is an extreme mismatch for a single MCP server, far beyond the 50+ threshold. The set includes many legacy endpoints, versioned duplicates, and overlapping operations, indicating an uncurated API dump rather than a well-scoped tool surface.

    Completeness5/5

    The surface covers an enormous range of the Transkribus platform: auth, collections, documents, pages, transcripts, models, recognition, jobs, credits, crowdsourcing, e-learning, admin, files, processing, labels, search, uploads, users, and stats. No obvious domain gap is apparent from the tool list.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow

    Resources