mcp-loader
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_NO_HOT_RELOAD | No | Set to 'true' to disable hot reload |
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 |
|---|---|
| context-test_contextInfoB | Get detailed information about the MCP context |
| context-test_trackUsageC | Track tool usage with context information |
| context-test_withTimeoutC | Execute something with timeout using AbortSignal from context |
| demoD | Demo tool with enum and default value |
| math_addA | Add two numbers |
| math_divideC | Divide two numbers |
| math_multiplyA | Multiply two numbers |
| session_infoB | Get information about the current Claude Code session |
| session_notifyC | Send a notification through MCP |
| session_requestC | Make a request through MCP protocol |
| systemB | Get system information and MCP context |
| testC | Test tool to verify MCP loader works |
| test_echoA | Echo back a message |
| test_getTimeB | Get current UTC time |
| test_hotReloadTestD | Test that hot reload is working |
| test_liveTestC | Live reload test - added without restart |
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 16 tools
Several tools overlap in purpose, especially the generic verification tools 'test', 'demo', 'test_hotReloadTest', and 'test_liveTest', which an agent could easily confuse. The context/system information tools also blur together: 'system', 'session_info', and 'context-test_contextInfo' all report similar environment/context details.
Tool naming is mixed: math_, session_, and test_ prefixes are used, but there are bare names like 'demo', 'system', and 'test' alongside hyphens and camelCase in 'context-test_contextInfo' and 'test_hotReloadTest'. The overall pattern is readable but inconsistent.
At 16 tools, the set is borderline heavy for what appears to be a loader/test utility server. Many of the test/demo/verification tools could likely be consolidated without losing functionality.
The set covers math, session, context, echo, time, and reload-testing scenarios, but it feels like a grab bag rather than a complete domain surface. Notable gaps include no math subtraction, no negative/error-case testing tools, and redundant generic test tools that do not clearly advance the loader-testing purpose.