String Utility Belt

com.stringutilitybeltPublished by stringutilitybelt.comv1.10.4Updated Nov 3, 2026

MCP server exposing String Utility Belt's utilities and pipelines as tools for AI agents.

VerifiedSTDIODesktop onlyDeveloper ToolsData & Analytics

Overview

AI-generated overview

Runs 248 local string and data transformations — encode, hash, compress, convert formats — as agent tools, including multi-step pipelines.

What you can do
  • Search and inspect utilities: find transformations by keyword and read one utility's parameters, types and worked examples
  • Run a single transformation on text and get the output, with an output encoding where relevant
  • Run ordered multi-step pipelines, including parallel branches, macros and run-on-each steps
  • Detect an unknown input's format (base64, JWT, gzip, JSON, YAML and more) with confidence scores
When to use it
Useful when an assistant needs exact, reproducible encoding, decoding, hashing, compression or format conversion instead of guessing, and when several transformations must be chained in one call.
Requirements
Runs as a local process over stdio, installed from the npm package (for example via npx). Node.js is required; the README states Node.js 20.19+ or 22.12+. No authentication, environment variables or headers are declared, and transformations run on the machine without network access.
Before you install
The tools transform whatever input the assistant passes, so pasted secrets, tokens or private data are processed locally but still travel through the assistant's conversation. Outputs are returned as text or bytes; verify results before relying on them for security-sensitive work such as hashing or encryption.

Installation

In SourceWeft

  1. Open String Utility Belt in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

String Utility Belt

[CI] [License: MIT] [npm: subelt] [smithery badge] [Sponsor on GitHub]

stringutilitybelt.com · Usage guide · All utilities · Integrations

Chain string transformations into visual pipelines with live, per-step previews. 246 utilities — encodings, hashes, ciphers, compression, data formats (JSON/YAML/TOML/CSV/XML), line and text operations, analysis, generators, web/dev helpers, numbers, dates and colours — all running client-side, with the same engine available as a CLI, an HTTP API, an MCP server, a browser extension and a VS Code extension.

[A Base64 token is pasted into String Utility Belt, then three steps are added: Base64 decode, JSON pretty-print and JSON to YAML. Each step shows its own output as soon as it is added, and the result panel ends on the YAML.]

Use it from your agent, terminal or editor

Every utility also runs on your own machine, outside the browser:

bash
# Give Claude Code (or any MCP client) exact hashing, encoding and decoding instead of a guessclaude mcp add subelt -- npx -y @string-utility-belt/mcp
# Pipe text through a pipeline from the shellecho 'eyJ1c2VyIjoiYWRhIn0=' | npx subelt base64_decode json_pretty

Features

  • Pipelines — add, reorder (drag and drop), duplicate, disable/solo steps; undo/redo; per-step previews, diffs, timings and error policies (pass through / stop / empty); conditional steps; parallel branches with concat/zip/json/pick merges; macros (collapse a sub-chain into one step); "run on each" steps (run a sub-chain on every line, delimited piece, JSON array element or object value).
  • Share and save — pipelines (and optionally the input) as compressed #/p/… links, a named pipeline library with JSON import/export, a preset gallery, an embeddable #/embed/… widget.
  • Magic — detects the input's format (base64, JWT, gzip, JSON, …) and suggests or appends the decoding step; "decode until stable" mode.
  • Input/output — file upload (text and binary), fetch-a-URL via the Worker proxy, input history, side-by-side and diff views, hex view for bytes, syntax highlighting, stats bar, smart download names, copy-as (raw / JSON literal / hex / base64).
  • Engine — runs in a Web Worker with cancellation, adaptive debounce, a chunked mode for multi-MB inputs and a preview-first-64 KB option; custom JavaScript steps run in a sandboxed, network-less iframe + worker, and are quarantined when they arrive from someone else's link.
  • App — command palette (Ctrl+K), keyboard shortcuts (?), fuzzy utility search with favourites/recents and type-aware badges, light/dark themes, per-utility doc pages with a live playground, installable PWA with offline support and an OS share target, i18n scaffold.

Using the app

Open stringutilitybelt.com — nothing to install, and every transformation runs in your browser (see the privacy policy for the few features that contact the server). The site sets no cookies and runs no tracking scripts: Cloudflare Web Analytics counts page views without cookies, the site's own server counts clicks on sponsor and tool links, utilities added, editor opens and runs, and page loads that find the browser extension, by id alone, neither ever receives what you paste, and the site's Content-Security-Policy blocks scripts from anywhere else. The how-to guide lives in the app itself: click Docs in the header, or go to /docs/. Each utility's settings and examples are on its own page, listed at /utilities/.

From a terminal, the same engine is one command away:

bash
echo -n hello | npx subelt trim base64_encode hash   # SHA-256 of the base64

Development

Requires Node.js 20.19+ or 22.12+.

bash
git clone https://github.com/String-Utility-Belt/string-utility-belt.gitcd string-utility-beltnpm cinpm run dev          # generates the utility manifest, then starts Vitenpm test             # Vitest (unit, component, golden-example and property tests)npm run lintnpm run typecheck
CommandWhat it does
npm run genRegenerate src/utilities/_generated/* (run automatically before dev/build)
npm run buildProduction build of the web app
npm run check:bundleEnforce the entry-chunk budget in bundle-budget.json
npm run build:seoPre-render utility pages, sitemap, RSS and OG images into dist/ (build:seo:fast skips OG images)
npm run build:sitebuild + build:seo
npm run build:toolsBuild packages/* (core, CLI, MCP server, browser extension, VS Code extension)
npm run test:e2ePlaywright end-to-end tests against a production build
npm run benchLarge-input benchmarks (vitest bench)
npm run deploybuild:site, then wrangler deploy (Cloudflare Workers: static assets + /api/*) — releases normally deploy from CI
npm run release -- planWhat a release from HEAD would ship, and at which versions (RELEASING.md)
npm run readme:demoRe-record this README's demo GIF from the production build (after npm run build; needs ffmpeg)

Other surfaces

SurfaceWhereNotes
Core librarypackages/coreFramework-free engine + all utilities
CLIpackages/cliecho -n hello | subelt base64_encode
MCP serverpackages/mcpUtilities and pipelines as agent tools over stdio
HTTP APIworker/POST /api/run, GET /api/utilities[/:id] (CORS, rate-limited)
Browser extensionpackages/extensionMV3; context menu "run on selection"
VS Code extensionpackages/vscodeTransform selection, run a share link

Support the project

String Utility Belt is free, open source and has no paid tier. If it saves you time, you can support its development through GitHub Sponsors: it pays for hosting and keeps new utilities, presets and fixes coming. Companies can also sponsor a page on the site.

Contributing

Contributions are welcome — bug reports, utility ideas and pull requests. Start with CONTRIBUTING.md (setup, adding a utility, PR checklist) and the Code of Conduct. CLAUDE.md is the detailed architecture reference.

Found a security issue? Please report it privately — see SECURITY.md.

Badges

[M8ven Verified] [LightNow capabilities]

License

MIT

Source: README.md at commit 5489fae

Tools

5

list_utilities

List utilities

Search the string-transformation utilities this server can run (248 total, across categories like Encoding, Hashing, Ciphers, Compression, Data Formats, Analysis, Generators and more). Returns {items: [{id, name, category, description}], total, categories}, best matches first. Use this first to find an id, then call describe_utility for its exact parameters before run_utility. `category` and `query` combine (a utility must match both); omit both to browse the whole catalog. A category that does not exist matches nothing rather than failing, so take one from `categories`. There is no paging: when `total` exceeds the items returned, raise `limit` or narrow the query. Reads the bundled catalog only: no network access and no rate limit.

Parameterslimitquerycategory

describe_utility

Describe utility

Full documentation for one utility: its parameters (kind, default, options/bounds, description), the value types it accepts/produces, tags, aliases, worked examples (input, inputEncoding, params and expected output — byte outputs there use the app's display format, while run_utility returns bytes as base64), and which runtime capabilities it needs. Call this before run_utility to learn the exact parameter names and defaults; skip it for a utility you have already described. `id` must be an exact, case-sensitive utility id: names and aliases are not resolved, so look those up with list_utilities first. An unknown id returns isError ("unknown utility: <id>"). When `unavailable` is set, run_utility and run_pipeline refuse the utility.

Parametersidrequired

run_utility

Run utility

Run a single utility on `input` and return {output, outputEncoding?}. For two or more transformations in a row, make one run_pipeline call instead of chaining run_utility calls; if you do not know the id yet, find it with list_utilities. Plain text output is returned as-is; a JSON-producing utility returns pretty-printed JSON text; a byte-producing utility (e.g. gzip_compress, get_bytes) returns base64 with `outputEncoding: "base64"`. `inputEncoding` controls how `input` itself is decoded first: "text" (default) uses it as-is, "base64" or "hex" decode it to raw bytes, "json" parses it. Params are validated against describe_utility's spec; invalid ones are rejected. Input is capped at 1,000,000 bytes, output text past 1,000,000 characters is cut off (flagged `truncated`, with `fullLength`), and the call is stopped after 20s. A failing utility returns isError with the error message. Utilities that run arbitrary user JavaScript (e.g. "custom_js") are refused, and the few that need a browser DOM parser (e.g. "xml_to_json", "html_table_to_csv") fail here.

ParametersidrequiredinputrequiredparamsinputEncoding

run_pipeline

Run pipeline

Run several transformations on `input` in one call: an ordered list of steps (string-utility-belt v3 schema), each step's output feeding the next. Besides utility steps, a pipeline can hold branches (parallel forks merged back together), macros (named sub-pipelines) and "run on each" steps (a sub-pipeline run on every line, delimited piece, JSON array element or JSON object value). Prefer this to chaining run_utility calls; for a single transformation, run_utility is simpler. Returns {output, outputEncoding?, errors, timings, skipped, halted}: `errors` maps step id to its error message, `timings` maps step id to milliseconds. Provide exactly one of `steps` or `share` (a `#/p/<payload>` share link, a full URL containing one, or the bare payload). Untrusted step data is sanitized first, so malformed entries are dropped rather than rejected. Refused outright: pipelines with more than 100 steps (nested steps counted), unknown utility ids, enabled steps with invalid params, and any step that would run arbitrary user JavaScript (e.g. "custom_js") — LLM-driven code execution is out of scope. Input is capped at 1,000,000 bytes, output text past 1,000,000 characters is cut off (flagged `truncated`, with `fullLength`), and the call is stopped after 20s.

ParametersinputrequiredsharestepsinputEncoding

detect_format

Detect format

Guess what `input` is — JSON, YAML, TOML, XML, HTML, CSV/TSV, base64/base32/hex, URL-encoding, JWT, UUID, data URI, gzip/zlib, email, URL, IP address, unix timestamp, Markdown, SQL, Morse code, ROT13, plain binary — and return {candidates: [{format, confidence, note}]}, best first, confidence 0-1. Use it when you are handed an opaque or unlabelled value and must pick a utility for it; skip it when the format is already known. It only identifies, never transforms: to decode, search list_utilities for the top format (base64 -> base64_decode, JWT -> jwt_decode) and run that with run_utility. Ambiguous input yields several candidates (all-digit text can be a timestamp, JSON and hex at once); treat anything below about 0.45 as a weak guess. Use inputEncoding "base64"/"hex" only to deliver binary data such as gzip bytes: it is decoded before detection, so a base64 string you want identified must stay "text" (the default). Empty input yields an empty list.

ParametersinputrequiredinputEncoding

Version history

11
  1. v1.10.4LatestNov 2, 2026
  2. v1.10.3Nov 1, 2026
  3. v1.10.2Oct 25, 2026
  4. v1.10.0Oct 20, 2026
  5. v1.9.2Oct 17, 2026
  6. v1.9.1Oct 17, 2026
  7. v1.7.0Oct 11, 2026
  8. v1.6.1Oct 9, 2026
  9. v1.6.0Oct 8, 2026
  10. v1.4.0Oct 8, 2026
  11. v1.3.3Oct 6, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts