Azoraqua/minestom-mcp
A stdio MCP server for Minestom, implemented with the Model Context Protocol SDK and TanStack AI tool definitions.
Platform-specific configuration:
{
"mcpServers": {
"minestom-mcp": {
"command": "npx",
"args": [
"-y",
"minestom-mcp"
]
}
}
}Add the config above to .claude/settings.json under the mcpServers key.
A stdio MCP server for Minestom, implemented with the Model Context Protocol SDK and TanStack AI tool definitions.
Preferred package invocation:
npx -y minestom-mcpOften a file like .mcp.json at your project root will be picked up by agents:
{
"mcpServers": {
"minestom-mcp": {
"command": "npx",
"args": ["-y", "minestom-mcp"]
}
}
}Installed command aliases:
minestom-mcp-server
minestom-mcpWhy this shape:
minestom-mcp-server is the npm package name and the safest npx entrypoint.minestom-mcp is the shorter command alias after install.npx resolves the matching bin when one of the bin entries matches the package name, so publishing the package as minestom-mcp-server with a minestom-mcp-server bin keeps npx -y minestom-mcp-server reliable. Source: npm npx docsThe tool surface is grounded in:
Detailed tool documentation lives in docs/tools.md.
The repository also ships a publish-ready static docs site in `docs/` plus a GitHub Pages workflow in `/.github/workflows/deploy-docs.yml`.
Community and contribution docs live in CONTRIBUTING.md, CODE_OF_CONDUCT.md, and SECURITY.md.
ping: verifies that the MCP server is reachable.get_server_info: returns package metadata, runtime details, tool inventory, and knowledge-catalog coverage.inspect_minestom_environment: inspects the current workspace or repoRoot, including subdirLoading reviews...