mcp-dev-utils
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-dev-utils format this JSON: {"name":"John","age":30}"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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).

Tools
Tool | Description |
| Pretty-print and validate a JSON string |
| Generate 1–20 random UUID v4 values |
| Encode or decode Base64 strings |
| Look up an HTTP status code name and description |
| Convert a Unix timestamp to UTC or get the current time |
Related MCP server: Dev Toolbox MCP Server
Resources
URI | Description |
| 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.pyConnecting 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.mdKey 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
mcpitself.
Available Tools
5 toolsbase64_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
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.
Maintenance
Related MCP Connectors
Tiny devtools MCP server: slugs, timestamps, case conversion, hashing, base64, UUIDs.
Developer utilities MCP server: base64, hash, slug, uuid v4, timestamp, urlencode. Free, no key.
Free hosted dev toolkit: uuid, hash, base64, JWT decode, CSV->JSON, time, JSON tools as MCP
238+ dev tools via MCP: JSON, QR, PDF, DNS, hash, UUID, code review, JWT, SSL, WHOIS, and more
Related MCP Servers
- AlicenseAqualityDmaintenanceZero-auth MCP server with everyday developer utilities: base64, UUID, hash, JWT decode, cron, timestamps, JSON, regex.1776 npm4MIT
- AlicenseNot gradedqualityDmaintenanceProvides various developer utilities such as UUID generation, timestamp conversion, Base64 encoding, color conversion, password generation, hash generation, and JSON formatting via MCP.13 npm1ISC
- AlicenseNot gradedqualityDmaintenanceAn MCP server offering developer utilities including JSON validation, base64 encoding, timestamp conversion, and hashing, built with a clean architecture for easy extensibility.MIT
- AlicenseNot gradedqualityCmaintenanceA 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 npmMIT