Skip to main content
Glama
Zhou-Shilin

mcp-server-minecraft-mod-devdoc

by Zhou-Shilin
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_providersA
        Get a list of available documentation providers and their versions

        Returns:
            A formatted string with providers and their versions
get_structureC
        Get the file structure with previews for a specific version of documentation

        Args:
            provider: The documentation provider (e.g., neoforge, fabric)
            version: The version of the documentation
get_full_contentC
        Get the full content of a documentation file

        Args:
            provider: The documentation provider (e.g., neoforge, fabric)
            version: The version of the documentation
            file_path: The path to the file

Prompts

Interactive templates invoked by user choice

NameDescription
devdoc-usage-example Provides instructions on how to use the Minecraft Mod Documentation MCP server.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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