mcp-server-devutils
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 |
|---|---|
| base64_encodeC | Encode a string to Base64 |
| base64_decodeC | Decode a Base64 string |
| uuid_generateB | Generate one or more UUIDs (v4) |
| ulid_generateA | Generate a ULID (Universally Unique Lexicographically Sortable Identifier) |
| hashA | Hash a string using a specified algorithm. Supported: md5, sha1, sha256, sha384, sha512 |
| hash_allC | Hash a string with all supported algorithms at once |
| jwt_decodeA | Decode a JWT token (without verification) and show header, payload, expiry |
| cron_explainA | Explain a cron expression in plain English |
| cron_validateB | Validate a cron expression |
| cron_nextA | Show the next N run times for a cron expression |
| timestamp_to_isoA | Convert a Unix timestamp to ISO 8601 date string |
| iso_to_timestampA | Convert an ISO 8601 date string to Unix timestamp |
| timestamp_nowB | Get the current time in multiple formats |
| json_formatC | Pretty-print / format a JSON string |
| json_minifyA | Minify a JSON string (remove whitespace) |
| json_validateC | Validate a JSON string and report its type |
| regex_testC | Test a regular expression against a string |
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 17 tools
Each tool has a clearly distinct purpose with no ambiguity. For example, base64_encode and base64_decode are complementary but distinct operations, while cron_explain, cron_next, and cron_validate each handle different aspects of cron expressions. The descriptions make it easy to differentiate between tools like json_format, json_minify, and json_validate.
Tool names follow a highly consistent snake_case pattern with clear verb_noun or noun_verb structures throughout. Examples include base64_decode, cron_explain, json_format, and timestamp_to_iso. There are no deviations in naming conventions, making the set predictable and easy to navigate.
With 17 tools, the count is slightly high but reasonable for a developer utilities server covering diverse domains like encoding, time, JSON, and identifiers. Each tool serves a specific function, though some related tools (e.g., hash and hash_all) could potentially be consolidated without loss of functionality.
The toolset provides comprehensive coverage for common developer utility tasks, including encoding/decoding, cron handling, hashing, JSON manipulation, time conversions, and ID generation. There are no obvious gaps; for instance, cron operations include explain, next, and validate, while time tools cover ISO to timestamp, timestamp to ISO, and current time.