mcp-minecraft-forge
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_forge_docsB | Search Forge Minecraft modding documentation with FTS5 full-text search. |
| get_exampleB | Get code examples for Forge modding topics. |
| explain_forge_conceptC | Get detailed explanation of Forge concepts. |
| list_forge_versionsB | List all available Forge versions. |
| get_database_statsC | Get database statistics. |
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 5 tools
Most tools have distinct purposes: search, get example, explain concept, and list versions are clearly different. However, the get_database_stats tool seems unrelated to Forge modding, potentially causing confusion.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., search_forge_docs, list_forge_versions). The naming is predictable and clear.
With 5 tools, the server is well-scoped for a documentation-focused MCP. Each tool contributes to the core functionality of exploring Forge modding resources.
The set covers key documentation tasks: searching, getting examples, explaining concepts, and listing versions. The get_database_stats tool is a minor outlier, and there is no tool for browsing or summarizing documentation, but core needs are met.