MCP Toolkit
Related Servers
Alternatives to MCP Toolkit
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables MCP clients to run seven local text and data utilities, including JSON formatting, CSV inspection, text analysis and diffing, hashing, timestamp conversion, and URL component parsing. Everything runs offline in memory with no API keys, models, or outbound requests.71MIT
- AlicenseBqualityBmaintenanceEnables AI assistants to perform everyday developer utility tasks locally and offline — Base64/URL encoding, hashing, JSON formatting, JWT decoding, timestamp conversion, cron scheduling, regex testing, password generation, and text conversion — with zero dependencies or API keys. Works with Claude Code, Cursor, VS Code, Windsurf, and any MCP client.17MIT
- AlicenseAqualityBmaintenanceEnables users to compute everyday developer and text utilities—including JSON formatting, QR codes, unit and timestamp conversion, hashing, Base64, regex testing, password/UUID generation, and word counting—through read-only tools without AI calls or external lookups.10302 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides 12 local developer tools (JSON format, Base64, JWT decode, regex test, hash, UUID, etc.) for AI assistants like Claude Desktop and Cursor.7 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides deterministic, stateless tools for common data work including JSON, CSV, text, encoding, hashing, IDs, date/time, and number statistics.MIT

utilixofficial
AlicenseNot gradedqualityBmaintenanceEnables AI assistants to run more than 300 deterministic developer utilities locally, covering JSON formatting, encoding, hashing, text diffing, regex testing, token estimation, PII/secrets detection, and related tasks without API keys.MIT
TDQS
Scored across 9 tools
Each tool targets a distinct operation, and the json_* family is reasonably separated into inspect (structure/validation), format (pretty-print/minify), and pointer (value lookup). Minor friction remains between json_inspect and json_format since both parse JSON, and the encode/decode pairs (base64_convert, url_encode) require reading descriptions to know direction is toggled by a flag.
Nearly all names follow a consistent snake_case subject_verb pattern (json_inspect, text_analyze, url_encode, timestamp_convert). The exceptions are json_pointer, which is noun_noun with no verb, and sha256_hash, where the verb is inverted, but both remain readable and unambiguous.
Nine tools is well within the ideal 3-15 range and every tool maps to a distinct, frequently needed utility operation. Nothing feels padded or redundant within the set.
The surface covers common text/JSON/encoding/timestamp/URL chores with both encode and decode directions for Base64 and URL, plus URL and JSON inspection. Gaps exist for adjacent frequent needs like other hash algorithms (MD5/SHA-1), HMAC, UUID generation, or regex operations, but core workflows have no dead ends.