Local Utilities 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 |
|---|---|
| get_hostnameA | Returns the hostname of the machine running the MCP server. |
| get_public_ipA | Returns the public IP address of the machine running the MCP server. |
| list_directoryD | – |
| get_node_versionA | Returns the Node.js version information of the environment running the MCP server. |
| check_portD | – |
| get_time_and_dateA | Returns the current time, date, day of week, and timestamp in various formats |
| thinkD | – |
| get_thoughtsB | Retrieve all recorded thoughts |
| clear_thoughtsA | Clear all recorded thoughts |
| get_thought_statsC | Get statistics about recorded thoughts |
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 10 tools
Each tool has a distinct name and purpose, even though some lack descriptions. The 'get_*' tools clearly differentiate between hostname, node version, public IP, time/date, and thoughts, while 'list_directory', 'check_port', and the thought management tools are all distinct.
All tool names follow a consistent lowercase_snake_case pattern, predominantly using verb_noun structure (e.g., 'get_hostname', 'list_directory', 'clear_thoughts'). The single verb 'think' is a minor deviation but still fits the pattern.
10 tools is a reasonable number for a local utilities server, covering both system information and a thought management module without overloading the surface.
The thought management tools are complete, but the system utilities are sparse, lacking common operations like disk space, CPU usage, or process listing. This leaves notable gaps for a 'Local Utilities' server.