devkit-mcp
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., "@devkit-mcp What's the SHA-256 of 'hunter2'?"
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.
devkit-mcp
A Model Context Protocol server that gives an AI assistant seven everyday developer utilities: sending HTTP requests, inspecting JWTs, hashing, generating UUIDs, testing regular expressions, explaining cron schedules, and encoding text.
No API keys, no accounts, no configuration. Clone it, build it, point a client at it.
┌────────────┐ MCP over stdio ┌──────────────┐
│ AI client │ ◄────────────────► │ devkit-mcp │
│ (Claude) │ JSON-RPC 2.0 │ 7 tools │
└────────────┘ └──────────────┘Why this exists
Language models are bad at exactly the things these tools are good at: computing a SHA-256 by hand,
predicting when 0 9 * * 1-5 next fires in America/New_York, or deciding whether a base64 string
round-trips. Each tool here replaces a plausible-sounding guess with a real answer.
Related MCP server: mcp-dev-utils
Tools
Tool | What it does |
| Sends an HTTP request and returns status, headers, timing, and body. Parses JSON bodies automatically. Redirects are followed manually and re-checked at every hop. |
| Decodes a JWT header and payload, and reports |
| MD5, SHA-1, SHA-256, SHA-384, SHA-512 digests or keyed HMACs, in hex, base64, or base64url. Optionally verifies against an expected digest in constant time. |
| UUIDv4 (random) or UUIDv7 (time-ordered, RFC 9562) from a cryptographically secure source. |
| Runs a regex and returns every match with its offset, positional groups, and named groups. Can preview a replacement. |
| Translates a cron expression to plain English and lists its next runs in a given timezone. Handles 5-field and 6-field syntax. |
| base64, base64url, hex, and URL encoding in both directions, plus JSON formatting and minification. Decoders reject bad input instead of returning garbage. |
Install
Requires Node.js 20 or newer.
git clone https://github.com/lllNuggetslll/devkit-mcp.git
cd devkit-mcp
npm install
npm run buildConnect it to a client
Claude Code
claude mcp add devkit -- node /absolute/path/to/devkit-mcp/dist/index.jsClaude Desktop
Add this to claude_desktop_config.json:
macOS —
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows —
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"devkit": {
"command": "node",
"args": ["/absolute/path/to/devkit-mcp/dist/index.js"]
}
}
}Restart the client, and the seven tools appear.
Anything else
The server speaks MCP over stdio, so any compliant client works:
node dist/index.jsTry it
Once connected, these all work in plain language:
"What's the SHA-256 of
hunter2?""When does
0 */4 * * *next run in Tokyo time?""Decode this JWT and tell me if it's expired."
"Does
^\d{3}-\d{4}$match555-1234?""Generate 5 UUIDv7s for my database seeds."
"GET https://api.github.com/repos/anthropics/claude-code and show me the star count."
Network access and SSRF
http_request refuses requests to loopback, link-local, and RFC 1918 addresses by default.
This matters more for an MCP server than for an ordinary HTTP client. The server takes its
instructions from a model, and a model can be steered by whatever text it just read — a web page, an
issue comment, a log file. An unrestricted fetch tool is therefore a server-side request forgery
primitive aimed at everything the host machine can reach, including cloud metadata endpoints like
169.254.169.254.
The guard resolves hostnames before deciding, so a DNS record pointing at 127.0.0.1 does not get
through, and it re-checks every redirect hop rather than trusting the first URL.
Testing a local API is the legitimate case for this, so it is one variable away:
{
"mcpServers": {
"devkit": {
"command": "node",
"args": ["/absolute/path/to/devkit-mcp/dist/index.js"],
"env": { "DEVKIT_ALLOW_PRIVATE_HOSTS": "1" }
}
}
}Other limits: responses are capped at 256 KB, redirects at 5 hops, and requests time out after 15 seconds by default (60 seconds maximum).
Development
npm test # run the suite
npm run test:watch
npm run typecheck
npm run dev # tsc --watchThe suite has 38 tests in two layers. tests/tools.test.ts covers the pure functions, including
published test vectors — the RFC 4231 HMAC-SHA256 vector, the known SHA-256 of the empty string —
plus the edge cases worth pinning down: zero-length regex matches that would otherwise loop forever,
IPv4-mapped IPv6 addresses like ::ffff:127.0.0.1 that would slip past a naive private-range check,
and encodings that must round-trip exactly.
tests/server.test.ts runs the real server against a real MCP client over an in-memory transport,
so tool registration, schema generation, defaults, and error results are verified through the
protocol rather than around it.
How it is put together
src/
index.ts entry point; stdio transport and signal handling
server.ts builds the McpServer and registers every tool
tools/
types.ts ToolDefinition contract and result helpers
index.ts the tool registry
http.ts http_request, plus the SSRF host policy
jwt.ts hash.ts uuid.ts regex.ts cron.ts text.tsEvery tool is a ToolDefinition: a name, a description, a Zod input schema, MCP annotations, and a
handler. server.ts iterates the registry and registers each one, so adding a tool means writing a
module and adding a line to tools/index.ts — nothing else changes.
Two conventions are worth calling out:
The logic is separate from the protocol. Each module exports a plain function — hashText,
decodeJwt, explainCron — that knows nothing about MCP. The tool wrapper handles argument parsing
and result formatting. That is what lets the unit tests call the real logic directly, with no
transport in the way.
Failures are results, not exceptions. MCP models a tool failure as an ordinary response with
isError: true, which lets the model read the message and correct itself. A thrown protocol error
would just look like a broken server. Every handler catches and returns fail(message) instead.
Tools also declare their side effects through MCP annotations, so a host can decide what needs
approval: everything is readOnlyHint: true except http_request, which is the only one marked
openWorldHint: true.
License
MIT
Available Tools
7 toolscron_explainExplain a cron expressionARead-only
Translates a cron expression into plain English and lists its next scheduled runs in a given timezone. Handles both 5-field and 6-field (seconds) syntax, and reports the interval between runs so an accidentally too-frequent schedule is obvious.
Inputs: expression (required), count, timezone.
decode_jwtDecode a JWTARead-onlyIdempotent
Decodes the header and payload of a JSON Web Token and reports the timing claims (iat, nbf, exp) in both epoch and ISO form, along with whether the token is expired. The signature is returned but NOT verified — this tool inspects tokens, it does not validate them, and the result always says so.
Inputs: token (required).
generate_uuidGenerate UUIDsARead-only
Generates one or more UUIDs using a cryptographically secure random source. Version 4 is fully random; version 7 (RFC 9562) embeds a millisecond timestamp so the values sort chronologically, which makes them well suited to database primary keys.
Inputs: count, version.
hash_textHash textARead-onlyIdempotent
Computes a cryptographic digest (or keyed HMAC) of a string. Supports md5, sha1, sha256, sha384, and sha512 with hex, base64, or base64url output. Can also verify the result against an expected digest using a constant-time comparison.
Inputs: text (required), key, encoding, expected, +1 more.
http_requestSend an HTTP requestA
Sends an HTTP request and returns the status, headers, timing, and body, parsing the body as JSON when the content type says so. Redirects are followed manually so each hop can be re-checked. Responses are capped at 256 KB. Requests to private and loopback addresses are refused unless DEVKIT_ALLOW_PRIVATE_HOSTS=1 is set.
Inputs: url (required), body, method, headers, +2 more.
regex_testTest a regular expressionARead-onlyIdempotent
Runs a JavaScript regular expression against a string and returns every match with its character offset, positional capture groups, and named capture groups. Optionally performs a replacement so you can preview the substituted output.
Inputs: input (required), pattern (required), flags, replacement.
transform_textEncode, decode, or reformat textARead-onlyIdempotent
Applies a reversible text transformation: base64 and base64url, hex, and URL percent encoding in both directions, plus JSON pretty-printing and minification. Decoding operations validate their input and report an error rather than returning garbage.
Inputs: input (required), operation (required), indent.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: HTTP requests, JWT decoding, hashing, UUID generation, regex testing, cron explanation, and text transformations. No overlap or ambiguity exists.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., decode_jwt, hash_text, generate_uuid). The pattern is predictable and easy to understand.
Seven tools is well-scoped for a general developer utility kit. Each tool covers a fundamental, non-overlapping function without being excessive or insufficient.
The tool set covers key developer needs: networking, crypto, identifiers, text processing, regex, and cron. Minor gaps like JSONPath or data format conversion are not critical for the stated purpose.
Maintenance
Related MCP Connectors
Free hosted dev toolkit: uuid, hash, base64, JWT decode, CSV->JSON, time, JSON tools as MCP
MCP server with 5 offline developer tools: UUID, timestamp, unit conversion, JSON tools and QR code.
Developer utilities MCP server: base64, hash, slug, uuid v4, timestamp, urlencode. Free, no key.
Tiny devtools MCP server: slugs, timestamps, case conversion, hashing, base64, UUIDs.
Related MCP Servers
- AlicenseAqualityDmaintenanceZero-auth MCP server with everyday developer utilities: base64, UUID, hash, JWT decode, cron, timestamps, JSON, regex.1776 npm4MIT
- FlicenseAqualityDmaintenanceA lightweight MCP server providing everyday developer utilities such as JSON formatting, UUID generation, Base64 conversion, HTTP status lookup, and Unix timestamp conversion as tools and resources.5-
- AlicenseBqualityDmaintenanceMCP server providing 37 developer tools for hashing, encoding, regex, JSON, SQL, cron, QR codes, UUID, JWT, and more, all powered by bmobot.ai APIs.37MIT
- 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