Skip to main content
Glama
mcp-dev-utils

mcp-dev-utils

by jegor377

mcp-dev-utils

A lightweight Model Context Protocol server that exposes everyday developer utilities as MCP tools and resources.

Built with mcp — the official Python MCP SDK (uses FastMCP for a clean, decorator-based API).

MCP Server in action


Tools

Tool

Description

format_json

Pretty-print and validate a JSON string

generate_uuid

Generate 1–20 random UUID v4 values

base64_convert

Encode or decode Base64 strings

http_status

Look up an HTTP status code name and description

unix_timestamp

Convert a Unix timestamp to UTC or get the current time

Related MCP server: Dev Toolbox MCP Server

Resources

URI

Description

utils://http-status-codes

Full reference list of supported HTTP status codes


Running locally

Requirements: Python ≥ 3.11, uv (or pip)

# Install dependencies
uv sync

# Run over stdio (default — used by most MCP hosts)
uv run python server.py

# Or run as an SSE server on port 8000
uv run python -c "from server import mcp; mcp.run(transport='sse')"

# Test interactively in the browser
uv run mcp dev server.py

Connecting to Claude Desktop

Add the following to your claude_desktop_config.json:

{
  "mcpServers": {
    "dev-utils": {
      "command": "uv",
      "args": ["run", "python", "server.py"],
      "cwd": "/absolute/path/to/mcp-dev-utils"
    }
  }
}

On macOS the config lives at: ~/Library/Application Support/Claude/claude_desktop_config.json

On Windows the config lives at: %APPDATA%\Claude\claude_desktop_config.json


Project structure

mcp-dev-utils/
├── server.py        # All tools, resources, and server definition
├── test_client.py   # Example MCP client for manual testing
├── test_msg.txt     # Raw JSON-RPC messages (educational — use test_client.py for reliable testing)
├── pyproject.toml   # Project metadata and dependencies
└── README.md

Key design decisions

  • Single-file server — keeps the codebase easy to read and audit at a glance; ideal for a portfolio piece where clarity matters.

  • FastMCP — the high-level SDK wrapper that removes boilerplate while still showing the underlying MCP concepts (tools, resources, structured arguments).

  • stdio transport — the default and most universally supported transport; no extra infrastructure needed.

  • No external dependencies — all tools rely only on the Python standard library plus mcp itself.

Available Tools

5 tools
base64_convertA

Encode a UTF-8 string to Base64 or decode a Base64 string back to text.

Inputs: text (required), mode. Returns: result

format_jsonA

Format and validate a JSON string. Returns pretty-printed JSON or a clear error message.

Inputs: json_string (required), indent. Returns: result

generate_uuidA

Generate one or more random UUID v4 values.

Inputs: count. Returns: result

http_statusA

Look up an HTTP status code to get its name and description.

Inputs: code (required). Returns: result

unix_timestampA

Convert a Unix timestamp (seconds since epoch) to a human-readable UTC datetime, or get the current time.

Inputs: timestamp. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4/5.0

    Scored across 5 tools

    Disambiguation5/5

    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.

    Naming Consistency3/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides various developer utilities such as UUID generation, timestamp conversion, Base64 encoding, color conversion, password generation, hash generation, and JSON formatting via MCP.
      13 npm
      1
      ISC
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server offering developer utilities including JSON validation, base64 encoding, timestamp conversion, and hashing, built with a clean architecture for easy extensibility.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A unified developer toolbox MCP server providing utilities for base64, JWT, timestamps, UUID, JSON formatting, hashing, URL handling, case conversion, color conversion, number bases, string operations, and regex.
      5 npm
      MIT