Devkits
Give your coding agent twelve local encoders, parsers, and formatters so you can validate payloads and debug strings without leaving the chat.
Overview
io.github.hezeclark/devkits is a Build-phase MCP server that exposes 12 local developer utilities (JSON, Base64, JWT, regex, hash, UUID, Markdown, diff, cron) to your agent over stdio.
What is this MCP server?
- 12 local tools: JSON, Base64, JWT, regex, hash, UUID, Markdown, diff, and cron
- Runs via npm package devkits-mcp-server with stdio MCP transport (v1.0.0)
- No cloud API keys—operations stay on your machine for secrets-sensitive work
- Useful for quick JWT inspection, JSON pretty-print, and text diff while pairing with an agent
- Complements repo workflows when you need deterministic transforms without custom scripts
- 12 bundled local developer tools
- Server version 1.0.0 via npm identifier devkits-mcp-server
- Transport: stdio MCP
What problem does it solve?
You waste context switching between the agent, browser decoders, and ad-hoc scripts whenever you need to parse JWTs, diff configs, or validate JSON.
Who is it for?
Indie builders who want fast, offline-friendly encoding, parsing, and diff tools inside Claude Code or Cursor.
Skip if: Teams that need hosted secrets management, production observability, or browser automation instead of static string utilities.
What do I get? / Deliverables
After you add devkits-mcp-server to MCP, your agent can run those transforms locally in one thread while you keep building.
- Formatted or validated JSON, Base64, JWT, regex, hash, and UUID outputs from agent calls
- Side-by-side text diffs and Markdown rendering without leaving the agent session
- Cron schedule explanations for config and infra snippets
Recommended MCP Servers
Journey fit
Canonical shelf is Build because solo builders wire MCP utilities while implementing APIs, agents, and scripts. agent-tooling fits stdio MCP servers that extend Claude Code, Cursor, and Codex with callable tools during implementation.
How it compares
Local utility MCP server, not a cloud integration or project scaffolding skill.
Common Questions / FAQ
Who is io.github.hezeclark/devkits for?
It is for solo developers and agent users who want JSON, JWT, Base64, regex, hash, UUID, Markdown, diff, and cron helpers without external SaaS decoders.
When should I use io.github.hezeclark/devkits?
Use it during implementation and debugging when you need repeatable encode/decode and format checks while the agent edits your codebase.
How do I add io.github.hezeclark/devkits to my agent?
Install the npm package devkits-mcp-server, add a stdio MCP entry pointing at that binary in Claude Code or Cursor, and restart the client so the 12 tools register.