MCP Integration

Use Dev Tools ! with Claude

Dev Tools ! runs a Model Context Protocol (MCP) server so Claude Desktop and other MCP clients can call 9 developer-tool functions directly. It is a remote server reached over Streamable HTTP — there is nothing to install.

Quick Setup — Claude Desktop

Add the following to your Claude Desktop config file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

claude_desktop_config.json
{
  "mcpServers": {
    "devtoolzy": {
      "url": "https://api.devtoolzy.com/devtoolzy/mcp",
      "transport": "streamable-http"
    }
  }
}

Save the file and restart Claude Desktop. The same URL works in any client that speaks Streamable HTTP — Cursor, Cline, Zed, and others use the same two fields under their own config key. No API key or account is needed.

Preview availability. The hosted endpoint is in limited preview while we finish rolling it out, so a client may not be able to reach it yet. If the server does not appear or the connection fails, get in touch and we will confirm access for you.

Available MCP Tools

Nine tools, each a pure function — same inputs, same outputs, no state carried between calls.

base64_transform

Encode text to Base64 or decode Base64 back to text — standard (RFC 4648 §4) or URL-safe (§5) alphabet.

Params:{ text: string, mode: "encode" | "decode", url_safe?: boolean }
format_data

Pretty-print, minify, or convert structured data between JSON, YAML, and XML.

Params:{ text: string, from_format: "json" | "yaml" | "xml", to_format?: same, action?: "format" | "minify" | "convert", indent?: number }
hash_text

Compute an MD5 / SHA-1 / SHA-256 / SHA-384 / SHA-512 digest — or an HMAC when a key is supplied.

Params:{ text: string, algorithm: "MD5" | "SHA-1" | "SHA-256" | "SHA-384" | "SHA-512", key?: string, encoding?: "hex" | "base64" }
decode_jwt

Decode a JSON Web Token and report header, payload, expiry status, and issued-at. Does not verify the signature.

Params:{ token: string }
generate_id

Generate UUID v4, UUID v7, ULID, or NanoID — 1 to 100 at a time.

Params:{ id_type: "uuid-v4" | "uuid-v7" | "ulid" | "nanoid", count?: number }
regex_test

Match a pattern against text, returning positions and named groups. Optionally substitutes. Capped at 5 seconds.

Params:{ pattern: string, text: string, flags?: string, replacement?: string }
unix_timestamp

Convert between Unix epoch and ISO 8601 UTC. Direction and seconds-vs-milliseconds are auto-detected; "now" returns the current time.

Params:{ value?: string }
cron_explain

Explain a 5-field cron expression in plain English and list the next three run times in UTC.

Params:{ expression: string }
cidr_info

Break down an IPv4 CIDR block — network, broadcast, netmask, wildcard mask, and usable host range.

Params:{ cidr: string }

MCP Discovery Endpoint

The MCP manifest — server URL, transport, and the tool list above — is published at:

GET https://devtoolzy.com/.well-known/mcp.json

How it Works

  1. Claude detects a task that matches a Dev Tools ! function (e.g. "decode this JWT").
  2. Claude calls decode_jwt via MCP with your token as input.
  3. The MCP server runs the function and returns structured JSON.
  4. Claude formats the result and presents it in the conversation.

The server is part of the Cosyslabs shared backend, reached at https://api.devtoolzy.com/devtoolzy/mcp. Each call is handled in memory and nothing is written to a data store, so no secrets, tokens, or inputs are retained. Note that the browser tools on this site are a separate, larger set that runs entirely client-side — the MCP surface is the nine functions listed above.