Skip to main content
Glama
runit-xze

unix-docs-mcp

by runit-xze
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to unix-docs-mcp

No user-submitted related servers found.

    Related Servers

    • mcp-infra

      DerWolk
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides tools for filesystem, database, web, system, and shell operations, along with resources and prompts via SSE transport.
      -

    • emcp

      slezica
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server providing filesystem operations, shell execution, and web search capabilities.
      -

    • MCP Learning Project

      RobertBauer-dev
      F
      license
      Not graded
      quality
      D
      maintenance
      A tutorial MCP server for learning the Model Context Protocol by building file and system tools. Provides hands-on experience creating custom tools that enable AI models to interact with files and execute system commands.
      -

    • mcp-docs

      gmantovani2005
      A
      license
      Not graded
      quality
      D
      maintenance
      Generic MCP server that exposes Markdown documentation to LLMs, enabling them to search and answer questions about any software documentation.
      MIT

    • gopher-mcp

      mrfentmen
      F
      license
      A
      quality
      C
      maintenance
      An MCP server that speaks the Gopher protocol, enabling AI to browse gopherspace, read text files, and search via Veronica-2.
      3
      22 npm
      -
    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.2/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct corpus (documents, manpages, source, syscalls) with distinct actions (list, get, search, read, find). The descriptions clearly differentiate between search_documents, search_manpages, and search_source, so there is no real ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (list_, get_, search_, read_, find_). Even search_all fits the verb+noun pattern with 'all' as the object. No mixed naming conventions are present.

    Tool Count5/5

    13 tools is well-scoped for a multi-corpus documentation server. Each corpus (documents, manpages, source, syscalls) has just the right set of operations, and search_all provides a cross-corpus entry point. No redundant tools exist.

    Completeness4/5

    The tool set covers the full read-only lifecycle for documents (list/get/search/read), manpages (list/search/read), source (search/read/find), and syscalls (list/get). A minor gap is the lack of a directory listing for source files, but search_source and find_symbol partially mitigate this.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources