Skip to main content
Glama
Zhou-Shilin

mcp-server-minecraft-mod-devdoc

by Zhou-Shilin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-server-minecraft-mod-devdoc

No user-submitted related servers found.

    Related Servers

    • MCP SpecNavigator

      kayaozkur
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables intelligent navigation and exploration of the Model Context Protocol specification through dynamic markdown tree generation, section search, content retrieval, and upstream synchronization with the official MCP repository.
      -

    • paradox-toolkit

      JDeffner
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients to research game mods by searching documentation and definitions, inspecting dependencies and playsets, validating saved files with structural and Tiger checks, and preparing or editing mod content with preview and write controls. It also supports starting or previewing the game through a local stdio connection.
      17 npm
      GPL 3.0

    • docs-mcp-server

      DewminK
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that exposes one or more documentation folders (Markdown, MDX, TXT) to AI agents, enabling listing, reading, and searching of documentation files.
      -

    • devdocs-mcp

      madhan-g-p
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides version-pinned, deterministic documentation sourced from DevDocs.io to AI assistants (Claude, RooCode, Cline, Copilot etc.) and also via offline mode. Not via Scraping! But using the supported downloading option from devdocs.
      17 npm
      13
      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

    A3.5/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct, non-overlapping purpose: one lists available providers, one retrieves file structure, and one fetches full content. No ambiguity.

    Naming Consistency5/5

    All tools follow a consistent `get_*` verb-noun pattern, making them predictable and easy to understand.

    Tool Count4/5

    With 3 tools, the set is minimal but covers the core functionality of browsing documentation. It could be expanded, but it is reasonable for a focused read-only server.

    Completeness3/5

    The tools cover browsing (providers, structure, content) but lack search or filtering capabilities, which are common in documentation systems. This is a notable gap for an agent needing specific information.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources