Minestom MCP Server
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 |
|---|---|
| pingA | Use this when you want to verify that the Minestom MCP server is reachable. |
| get_server_infoA | Use this when you need package metadata, runtime details, tool inventory, or knowledge-catalog coverage for this Minestom MCP server. |
| inspect_minestom_environmentA | Use this when you want a Minestom workspace scan rooted at the current directory or |
| inspect_minestom_buildA | Use this when you want Gradle or Maven specific interpretation for a Minestom workspace, including dependencies, plugins, wrapper commands, and variables from build files or version catalogs. |
| explain_minestom_patternA | Use this when you want a docs-backed explanation of how Minestom typically models bootstrap, instances, events, commands, schedulers, or thread ownership. |
| lookup_minestom_apiA | Use this when you need curated Minestom API matches with package names, why they matter, related APIs, and javadoc links. |
| plan_minestom_featureA | Use this when you want a Minestom feature plan grounded in official patterns for bootstrap, commands, events, instances, schedulers, and threading. |
| review_minestom_designA | Use this when you want Minestom-specific design feedback that checks whether a proposed feature aligns with the platform’s manager, instance, event, scheduler, and threading patterns. |
| suggest_minestom_librariesA | Use this when you want Minestom ecosystem suggestions grounded in the official libraries directory, with optional live GitHub topic lookups. |
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 9 tools
Each tool targets a distinct aspect of Minestom development: explanation, inspection, planning, review, API lookup, library suggestions, server info, and a health check. No two tools have overlapping purposes.
Most tools follow a verb_noun pattern (e.g., explain_minestom_pattern, inspect_minestom_build). The ping tool is a single verb but is a standard health check. Overall consistent and readable.
9 tools is well-scoped for a server focused on Minestom development support. Each tool serves a clear role without redundancy.
The set covers the core needs for Minestom development: pattern explanation, environment/build inspection, API lookup, planning, design review, and library suggestions. Minor gaps exist (e.g., no direct troubleshooting or runtime control), but it aligns with its advisory purpose.