mod-dev-mcp
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 |
|---|---|
| build_mod | Runs |
| format_mod | Runs CSharpier ( |
| tail_tmodloader_log | Reads the tail of tModLoader's client or server log for post-playtest error checking. |
| check_environmentA | Reports whether the .NET SDK, ModSources targets file, and mod symlinks are correctly wired up, so a session can tell if the build environment is still in a working state. |
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 1 tool
With only one tool, there is no possibility of confusion between tools. The single tool has a clear, distinct purpose.
The single tool 'check_environment' follows a consistent verb_noun pattern, which is clear and predictable.
A single tool for a mod development server is too few; a server of this scope would typically require multiple tools for building, testing, and managing configurations.
The tool only checks the environment status, leaving out essential operations like building or deploying mods, which are likely needed for the server's purpose.