Minecraft 1.21.1 Forge/NeoForge MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MC_DOCS_DIR | No | Path to the directory containing generated documentation files. Required for API browsing and code generation tools. |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_docsB | Full-text search across all Minecraft 1.21.1 + Forge/NeoForge documentation. Supports class names, method names, keywords, CamelCase splitting and fuzzy matching. |
| search_apiA | Structured API search — filter by class name, method name, return type, category, and mod loader. |
| get_api_detailA | Get full documentation for a specific class — method signatures, JavaDoc, annotations, parameters. Pass full class name (e.g. net.minecraft.world.level.block.Block) or simple name (e.g. Block). |
| get_documentA | Read a complete Markdown documentation page. Use list_documents to find available pages. |
| get_document_sectionA | Read a specific section of a documentation page by heading title. |
| search_eventsA | Search for Forge/NeoForge events by name or description. Can filter by event bus (MOD/GAME/FORGE) and mod loader. |
| get_event_detailA | Get full details of a specific event — fields, bus, cancellability, and usage example code. |
| browse_api_categoryA | Browse API categories and their contents. Call with no arguments to list all categories, or specify a category to see its classes. |
| list_documentsA | List all documentation pages in a category, or list all categories if no category specified. |
| get_registry_infoC | Get information about Minecraft/Forge/NeoForge registries (Block, Item, EntityType, etc.). |
| generate_mod_projectA | Scaffold a complete Forge or NeoForge mod project — build.gradle, main class, mods.toml/neoforge.mods.toml. |
| generate_blockB | Generate block code with optional BlockEntity and BlockState properties. |
| generate_itemB | Generate item code with optional food properties. |
| generate_entityB | Generate entity code (LivingEntity, Projectile, or misc). |
| generate_event_handlerB | Generate an event handler class for a specific event. |
| generate_network_packetC | Generate network packet code for client-server communication. |
| generate_data_providerB | Generate DataGen provider code (recipe, loot, tag, model, language). |
| review_mod_codeA | Review Java code for common Forge/NeoForge modding mistakes. Detects 15+ patterns including registration errors, event bus issues, client/server mixing, and more. |
| get_modding_knowledgeB | Get best practices and patterns for a specific modding topic. Covers both Forge and NeoForge patterns. |
| list_knowledge_topicsA | List all available knowledge base topics with descriptions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| modding-instructions | MC 1.21.1 Forge/NeoForge MCP server instructions and modding rules |
| api-index | Complete API index for browsing all available APIs |
TDQS
Scored across 20 tools
Most tools are grouped sensibly by purpose, but there are several overlapping knowledge-access tools: search_api vs search_docs, list_knowledge_topics vs list_documents, and get_modding_knowledge vs get_document/get_document_section. The descriptions help distinguish them, but an agent could still misroute a query among these similar options.
All tool names follow a consistent verb_noun snake_case convention: list_, search_, get_, browse_, generate_, and review_. The generator family in particular follows a predictable generate_<resource> pattern, making the action and target of each tool clear.
At 20 tools, the set is in the 16–25 range that starts to feel heavy, even though the broad modding scope makes the count understandable. Several documentation and search tools could potentially be consolidated without losing much capability.
The server covers the main modding workflow well: discovering knowledge, searching APIs and events, scaffolding projects, generating common code artifacts, and reviewing code. Minor gaps exist for rarer artifacts like configs, GUIs, or capabilities, but agents can work around these.