mcmodding-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_fabric_docsA | Search Fabric modding documentation for guides and API information. Use this when you need to find documentation about Fabric modding features, APIs, or tutorials. |
| get_exampleA | Get code examples for Minecraft modding topics. Returns complete, working code snippets with full context including explanations, source documentation, and metadata. Use this when you need concrete code examples for implementing features. |
| explain_fabric_conceptB | Get detailed explanation of a Fabric or Minecraft modding concept. Use this to understand fundamental concepts, terminology, or architectural patterns. |
| get_minecraft_versionB | Get Minecraft version information from the indexed documentation. Returns either the latest version or all available versions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose with no overlap: explain_fabric_concept covers conceptual understanding, get_example provides code snippets, get_minecraft_version handles version data, and search_fabric_docs focuses on documentation retrieval. The descriptions reinforce these boundaries, making misselection unlikely.
All tool names follow a consistent verb_noun pattern (explain_fabric_concept, get_example, get_minecraft_version, search_fabric_docs), using snake_case throughout. This predictability aids agent comprehension and tool selection without confusion.
With 4 tools, the count is reasonable for a modding documentation server, covering key areas like concepts, examples, versions, and search. However, it feels slightly thin—adding tools for specific API queries or troubleshooting could enhance coverage, but the current set is well-scoped.
The tool surface covers core modding documentation needs: conceptual explanations, code examples, version info, and documentation search. Minor gaps exist, such as lack of tools for direct API calls or mod configuration, but agents can work around these using the provided tools effectively.