mc-mod-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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mc_version_infoA | Returns version metadata (Java version, mappings flavor, loader options, build system, metadata file, doc links) for the chosen era. Use this when the user mentions a Minecraft version so you ground the rest of the answer. |
| mc_lookup_classA | Given a class concept or partial name (e.g. 'Block', 'TileEntity', 'EntityPlayerMP', 'Level', 'BlockPos'), returns the fully-qualified name in 1.8.9 (Forge/MCP) and modern 1.21+ (Mojang) along with notes on path or rename differences. Always returns top approximate matches even when the query doesn't hit exactly. |
| mc_lookup_apiA | Given a task description like 'send chat message', 'open gui', 'register block', 'render hud', 'send useitem packet', returns the canonical snippet for both 1.8.9 and modern 1.21+. Searches BOTH the method/API table and the class-name table so partial class queries still surface useful info. Use when the user asks 'how do I X in ?'. |
| mc_translateA | Given a method or class name from one era, suggests the equivalent in the other era. Looks across both classes and method tasks. Useful when porting code between 1.8.9 and 1.21+. |
| mc_eventA | Given a plain-English description of a trigger ('player joins', 'tick', 'right click block'), returns the event class name in 1.8.9, NeoForge 1.21+, and Fabric 1.21+. Also tells you whether the event lives on the mod bus or game bus (NeoForge distinction). |
| mc_mixinA | Returns code examples for Mixin (Sponge/Fabric Mixin) patterns: @Inject HEAD/TAIL, @ModifyArg, @ModifyVariable, @Redirect, @WrapOperation, @Accessor, @Invoker, plus mixin config JSON skeletons for Fabric and NeoForge. Use when the user is wiring up a mixin and you need to remember the exact annotation shape. |
| mc_gotchasA | Returns a list of common mistakes, breaking changes, and surprising behaviors per era. Filter by topic ('mixin', 'nbt', 'packets', 'fabric', 'mappings', etc.). Use proactively when the user starts a non-trivial task in a specific area. |
| mc_gradleB | Returns build.gradle, settings.gradle, and gradle.properties templates for a chosen era + loader combo. Pinned to current versions (NeoForge 21.10, Loom 1.10, Fabric API 0.131, Yarn 1.21.10+build.1, ForgeGradle 2.x for 1.8.9). Tell the user to bump to latest after copying. |
| mc_mappings_translateA | Given a class name from either Yarn (Fabric) or Mojang official (NeoForge / modern Fabric) mappings, returns the equivalent. Useful when porting between Fabric on Yarn and NeoForge on Mojang, or when reading a wiki snippet that uses the other naming. |
| mc_list_scaffoldsA | Enumerate every scaffold template id and its description. |
| mc_scaffoldA | Emits a code snippet (or config file body) for a given scenario, era, and loader. Run |
| mc_docsC | Returns the most relevant doc/wiki links to consult for a given era. |
| mc_list_versionsA | Live call to https://linkieapi.shedaniel.me/api/namespaces. Returns every mappings namespace (yarn, mojang, mojang_raw, quilt-mappings, mcp, legacy-yarn, feather, ...) and which Minecraft versions each one currently has. Use to confirm a version exists before searching it. By default filters to stable releases — pass includeUnstable=true to see snapshots, pre-releases, RCs. |
| mc_mappings_searchA | Live full-text search against linkie's mappings database. Returns class/method/field results for ANY (namespace, version) combination linkie carries — no curation gap, no stale snapshot. Use this whenever the user asks 'what is X called in ?' or 'find all methods named foo in 1.21.11 yarn'. For 26.1.x, linkie currently 500s on the mojang_raw namespace — use mc_mojang_mappings instead for those versions. |
| mc_lookup_fieldA | Convenience wrapper over mc_mappings_search filtered to fields. The curated knowledge tables don't track fields at all, so this is the only way to ask 'what's the field name for X in ?'. |
| mc_mojang_mappingsA | Bypasses linkie and fetches Mojang's client_mappings.txt straight from piston-meta.mojang.com, parses the proguard format, and searches it. Use this for any version linkie can't load — most importantly the 26.1 lineage (26.1, 26.1.1, 26.1.2) which linkie advertises but 500s on. Also useful when you want to verify a name against Mojang directly. First call for a version downloads the mapping (multi-MB) and caches it in-process; subsequent calls are instant. |
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 16 tools
Each tool targets a distinct aspect of modding (docs, events, gotchas, build scripts, scaffolding, mappings, etc.). Although there are similar-looking tools like mc_translate and mc_mappings_translate, their descriptions clearly differentiate between era-based and namespace-based translation. Overlaps are minimal and well-justified.
All tools use the 'mc_' prefix consistently. Most names follow a descriptive noun or verb pattern (e.g., mc_list_scaffolds, mc_lookup_api). However, the pattern is not perfectly uniform, mixing noun_verb (mc_mappings_search) with verb_noun (mc_list_versions), and some are just nouns (mc_mixin). Still, the naming is clear and predictable overall.
With 16 tools, the server's scope is well-scoped for a modding knowledge assistant. Each tool covers a distinct functional area without unnecessary bloat. The count feels appropriate for the domain, allowing both depth and breadth without overwhelming the user.
The tool set covers major modding tasks: version info, documentation, event handling, build scripts, scaffolding, mappings, mixins, and common pitfalls. Minor gaps exist (e.g., no dedicated tool for registry names or mod metadata), but these are often accessible via lookup or scaffold tools. Overall, the surface is quite complete for the server's purpose.