mcp-dev-utils
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| format_jsonA | Format and validate a JSON string. Returns pretty-printed JSON or a clear error message. |
| generate_uuidA | Generate one or more random UUID v4 values. |
| base64_convertA | Encode a UTF-8 string to Base64 or decode a Base64 string back to text. |
| http_statusA | Look up an HTTP status code to get its name and description. |
| unix_timestampA | Convert a Unix timestamp (seconds since epoch) to a human-readable UTC datetime, or get the current time. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| all_http_status_codes | A reference list of all HTTP status codes known to this server. |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: JSON formatting, UUID generation, Base64 conversion, HTTP status lookup, and timestamp conversion. There is no overlap or ambiguity between them.
All names use snake_case, but the pattern is mixed: format_json and generate_uuid are verb_noun, while base64_convert is noun_verb and http_status/unix_timestamp are noun_noun. This inconsistency reduces predictability, though the names remain readable.
With exactly 5 tools, the count is well within the ideal range for a focused utility server. Each tool earns its place and there is no bloat or feeling of insufficiency.
The set covers a reasonable spread of common developer utilities, but could be more comprehensive with additions like hashing or URL encoding. However, the current tools are self-contained and do not leave obvious dead ends.