Minecraft MCP server for viewing and managing mod development documentation support Neoforge and future sources
The MCP Server for Minecraft Mod Documentation is a server implementation designed to provide comprehensive documentation for mod developers working with Minecraft. Currently, it supports Neoforge documents and can be extended to support other docsets like Fabric in the future. Built on top of the Model Context Protocol (MCP), this server allows integration with AI applications such as Claude Desktop, Continue, Cursor, etc., facilitating seamless data access and tool interaction.
This server offers a range of powerful features that are powered by the MCP protocol, enabling advanced interactions between AI systems and documentation repositories:
Version Management: The server efficiently handles different versions of mod provider documents (e.g., Neoforge’s version-1.20.4
, version-1.20.6
, version-1.21.1
).
File Structure & Preview: Users can explore the file structure and get previews of individual document sections, making it easier to navigate and find specific parts of the documentation.
Content Retrieval: Full content retrieval is available for any chosen section or document, ensuring that developers have access to all relevant information necessary for their tasks.
Local Repository Management: The server manages a local repository, only updating remote sources when absolutely necessary (upon initial setup or after 24 hours), thus keeping resource usage low and performance high.
The architecture of the MCP Server is designed to seamlessly integrate with AI applications via the MCP protocol. It consists of multiple components:
Core Module: This module contains the main server logic, handling communication with clients and managing the local repository.
Provider Modules: These modules implement specific document provider interfaces (e.g., Neoforge). Each one is responsible for retrieving relevant documentation from their respective sources.
class NeoforgeProvider:
def __init__(self, repo_dir):
self.repo_dir = repo_dir
def get_document(self, version, section):
# Logic to fetch document content based on version and section
pass
The above example demonstrates how a provider for the Neoforge documentation could be implemented.
To start using this server, ensure you have Python 3.12+ installed. Then follow these steps:
pip install -r requirements.txt
uvicorn main:app --reload
Here are some realistic use cases and technical implementations of how this server can be integrated with various AI workflows:
A developer working on a new mod for Minecraft wants to find detailed information about crafting rules. Using the MCP Server, they can quickly retrieve relevant sections from the Neoforge documentation through an AI-driven prompt.
An AI application that automatically updates and serves documentation based on user actions (such as clicking a button or typing a command) can leverage the MCP Server to ensure accurate and up-to-date information is presented, enhancing user experience while maintaining system efficiency.
To integrate with an MCP client like Claude Desktop, the following configuration should be used:
{
"mcpServers": {
"mcp-server-minecraft-mod-devdoc": {
"command": "uv",
"args": [
"--directory", "${MCP_SERVER_PATH}",
"run", "--with", "mcp", "mcp", "run", "run_server.py"
]
}
}
}
This setup ensures that the MCP client can communicate and interact with the server seamlessly.
The compatibility matrix for different MCP clients is as follows:
MCP Client | Claude Desktop | Continue | Cursor |
---|---|---|---|
Resources | ✅ | ✅ | - |
Tools | ✅ | ✅ | ✅ |
Prompts | ✅ | ✅ | - |
Status | Full Support | Full Support | Tools Only |
For advanced configurations and security practices, refer to the following:
${MCP_SERVER_PATH}
with your local installation path.A: Check for common issues such as missing Git, incorrect repository paths, or unsupported versions.
A: Verify that all dependencies are installed correctly and ensure the necessary ports are not blocked.
A: Yes, by registering additional provider modules following the existing pattern.
A: Automatic management ensures that the repository is only updated when needed to minimize bandwidth usage.
A: File previews are optimized for quick rendering and do not significantly affect overall performance, making this feature particularly useful in interactive development environments.
Contributions are welcomed! To get started:
git checkout -b feature/my-feature
git push origin feature/my-feature
For more information on the Model Context Protocol, visit their official documentation:
The following is an MCP protocol flow diagram illustrating the interaction between AI applications, servers, and documents:
graph TB
A[AI Application] -->|MCP Client| B[MCP Protocol]
B --> C[MCP Server]
C --> D[Data Source/Tool]
style A fill:#e1f5fe
style C fill:#f3e5f5
style D fill:#e8f5e8
And here is the MCP client compatibility matrix:
Client | Resources | Tools | Prompts | Status |
---|---|---|---|---|
Claude Desktop | ✅ | ✅ | ✅ | Full Support |
Continue | ✅ | ✅ | ✅ | Full Support |
Cursor | ❌ | ✅ | - | Tools Only |
For further inquiries, refer to the official MCP documentation and community forums.
Explore community contributions to MCP including clients, servers, and projects for seamless integration
Learn to connect to MCP servers over HTTP with Python SDK using SSE for efficient protocol communication
Python MCP client for testing servers avoid message limits and customize with API key
Next-generation MCP server enhances documentation analysis with AI-powered neural processing and multi-language support
Powerful GitLab MCP Server enables AI integration for project management, issues, files, and collaboration automation
SingleStore MCP Server for database querying schema description ER diagram generation SSL support and TypeScript safety