Skip to main content
Glama
HarutuneDavisIBM

hermes-mcp

by HarutuneDavisIBM
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to hermes-mcp

No user-submitted related servers found.

    Related Servers

    • ParseFlow MCP Server

      Libres-coder
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to parse and search documents including PDF, Word, Excel, PowerPoint, and images via OCR, with support for semantic search and batch processing.
      2
      MIT

    • wissens-enablement-agent

      denny98-lab
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to securely search and list internal company documents via MCP tools, so they can answer employee questions based on current internal documentation.
      -

    • linked-docs

      folence
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to intelligently search and reference documentation using hybrid semantic + keyword search via MCP protocol.
      -
    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

    A4.1/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool targets a distinct resource or lifecycle action: products, projects, drafts, published documents, review/approval, search, and metadata lookups. The only potentially overlapping pair (update_draft vs update_document) is clearly separated by WIP status vs published status.

    Naming Consistency4/5

    Tool names follow a consistent hermes_verb_noun pattern (list_*, create_*, update_*, get_*, approve_*, request_*), with a minor deviation in hermes_me which lacks an explicit verb. Overall the naming convention is predictable and readable.

    Tool Count5/5

    Twelve tools is well within the typical well-scoped range and each tool supports a distinct part of the document management workflow. No redundant or filler tools are present.

    Completeness4/5

    The core document lifecycle is covered: create draft, update draft, request review, approve, update published metadata/status, search, and retrieve. Minor gaps exist around rejection/request-changes and explicit deletion, but these are workable given the documented status transitions.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources