{
  "markdown": "<p align=\"center\">\n  <img src=\"src/assets/images/icon.png\" alt=\"Strings-LE Logo\" width=\"96\" height=\"96\"/>\n</p>\n<h1 align=\"center\">Strings-LE: Zero Hassle String Extraction</h1>\n<p align=\"center\">\n  <b>Pull every string value out of the current file in one keystroke</b><br/>\n  <i>JSON/JSONC, YAML, CSV/TSV, TOML, INI, Environment files, and ten source languages</i>\n</p>\n\n<p align=\"center\">\n  <a href=\"https://marketplace.visualstudio.com/items?itemName=nolindnaidoo.string-le\">\n    <img src=\"https://img.shields.io/badge/Install%20from-VS%20Code-blue?style=for-the-badge&logo=visualstudiocode\" alt=\"Install from VS Code Marketplace\" />\n  </a>\n  <a href=\"https://open-vsx.org/extension/OffensiveEdge/string-le\">\n    <img src=\"https://img.shields.io/open-vsx/dt/OffensiveEdge/string-le?style=for-the-badge&label=Open%20VSX&color=blue\" alt=\"Open VSX downloads\" />\n  </a>\n  <a href=\"https://www.npmjs.com/package/string-le-mcp\">\n    <img src=\"https://img.shields.io/npm/v/string-le-mcp?style=for-the-badge&label=MCP%20server&color=blue&logo=npm\" alt=\"string-le-mcp on npm\" />\n  </a>\n  <a href=\"https://crates.io/crates/string-le\">\n    <img src=\"https://img.shields.io/crates/v/string-le?style=for-the-badge&label=Rust%20CLI&color=blue&logo=rust\" alt=\"string-le on crates.io\" />\n  </a>\n  <a href=\"https://letools.dev/tools/string-le\">\n    <img src=\"https://img.shields.io/badge/LE%20Tools-letools.dev-blue?style=for-the-badge\" alt=\"LE Tools\" />\n  </a>\n</p>\n\n---\n\n<p align=\"center\">\n  <img src=\"src/assets/images/demo.gif\" alt=\"String-LE Demo\" style=\"max-width: 100%; height: auto;\" />\n</p>\n\n> **Useful?** A star or rating is how other developers find it —\n> [★ GitHub](https://github.com/nolindnaidoo/string-le) ·\n> [★ Open VSX](https://open-vsx.org/extension/OffensiveEdge/string-le/reviews) ·\n> [★ Marketplace](https://marketplace.visualstudio.com/items?itemName=nolindnaidoo.string-le&ssr=false#review-details)\n\n## What it does\n\nOpen a file, press `Ctrl+Alt+E` (`Cmd+Alt+E` on Mac), and every string value in the document lands in a new editor — deduplicate and sort it from there. Works in VS Code and in VS Code–based editors like Cursor and VSCodium (installable from Open VSX).\n\n- **i18n prep** — flatten locale files (JSON/YAML) into a clean list of translatable values\n- **Config review** — see every string value in a TOML/INI/.env file at a glance\n- **CSV mining** — pull one column, several, or all of them; stream very large files\n\n## Install\n\n| Where | What you get | Install |\n|---|---|---|\n| **VS Code** | The same extraction, in your editor, on a keystroke | [Marketplace](https://marketplace.visualstudio.com/items?itemName=nolindnaidoo.string-le) |\n| **Cursor, VSCodium, Windsurf** | The same extension | [Open VSX](https://open-vsx.org/extension/OffensiveEdge/string-le) |\n| **A terminal or a CI step** | The same run over a whole tree, with exit codes | `cargo install string-le` · [crates.io](https://crates.io/crates/string-le) |\n| **Any MCP agent, via Node** | `extract_strings` over stdio | `npx string-le-mcp` · [npm](https://www.npmjs.com/package/string-le-mcp) |\n| **Zed** | The MCP server as a context server | [add it by hand](https://zed.dev/docs/ai/mcp) *(no listing yet)* |\n\n## Use it from an AI agent\n\nThe same engine runs as an [MCP](https://modelcontextprotocol.io) server, so an agent can call it directly instead of you running a command.\n\n| Editor | How |\n|---|---|\n| **VS Code** 1.101+ | Nothing to install — the extension registers `extract_strings` with agent mode |\n| **Zed** | No listing yet — [add the MCP server by hand](https://zed.dev/docs/ai/mcp) |\n| **Claude Code** | `claude mcp add string-le -- npx -y string-le-mcp` |\n| **Cursor, Windsurf, anything else** | point it at `npx string-le-mcp` |\n\n```\nextract_strings(content, format?, filename?, dedupe?, maxResults?)\n```\n\nReturns the values in document order, capped at 500 by default with `meta.truncated`. A format is optional — any unrecognised format falls back to quoted strings.\n\nThe server takes content and returns data — it reads no files and makes no network requests of its own. Published as [`string-le-mcp`](https://www.npmjs.com/package/string-le-mcp) on npm and as `io.github.nolindnaidoo/string-le` in the [MCP registry](https://registry.modelcontextprotocol.io).\n\n<details>\n<summary><b>Configuring it by hand</b> — any host with an MCP config file</summary>\n\nMost hosts read a JSON config. Add one entry:\n\n```json\n{\n  \"mcpServers\": {\n    \"string-le\": {\n      \"command\": \"npx\",\n      \"args\": [\"-y\", \"string-le-mcp\"]\n    }\n  }\n}\n```\n\n`-y` skips the install prompt on first run. Pin a version if you would rather not track releases — `string-le-mcp@2.3.1`.\n\nPrefer not to go through `npx` on every launch? Install it once and point at the binary instead:\n\n```bash\nnpm install -g string-le-mcp\n```\n\n```json\n{\n  \"mcpServers\": {\n    \"string-le\": { \"command\": \"string-le-mcp\" }\n  }\n}\n```\n\nIt speaks MCP over stdio and needs no environment variables, no API key and no configuration of its own. To check it before wiring it into anything:\n\n```bash\necho '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"tools/list\"}' | npx -y string-le-mcp\n```\n\nThat prints the tool list and exits — if you see `extract_strings`, the server works.\n\n</details>\n\n## Supported formats\n\n| Format | Language IDs | What gets extracted |\n|---|---|---|\n| JSON | `json` | String values (parsed; keys, numbers, and booleans excluded) |\n| YAML | `yaml` | String values including unquoted plain scalars, block/folded scalars, and multi-document files |\n| CSV | `csv` | Cells, with optional header handling, column selection, and a streaming mode for large files |\n| TOML | `toml` | String values including multiline strings; dates and numbers are excluded as typed values |\n| INI | `ini` | Values (INI is untyped, so numeric-looking values are extracted as strings) |\n| Environment | `dotenv`, `env` | Values (`export` prefixes, quotes, and inline comments handled) |\n| Python | `python` | Triple-quoted docstrings as one string, f-strings, `r`/`b`/`u` prefixes |\n| Rust | `rust` | Raw strings `r\"…\"`, `r#\"…\"#`, `r##\"…\"##` as one string with their inner quotes; byte strings |\n| Go | `go` | Backtick raw strings as one string, across lines |\n| Shell | `shellscript` | Heredocs (`<<EOF`, `<<'EOF'`, `<<-EOF`) as one string |\n| PHP, Ruby, Perl | `php`, `ruby`, `perl` | Heredocs and nowdocs (`<<<EOT`, `<<<'NOW'`, `<<~EOS`) as one string |\n| C# | `csharp` | Verbatim `@\"…\"` where `\"\"` is one quote; interpolated `$\"…\"` |\n| JavaScript, TypeScript | `javascript`, `typescript` (+ the react ids) | Template literals as **one** string, interpolation and nesting included |\n| Markdown, anything else | `markdown` | Fallback scan for `\"double\"`, `'single'`, or `` `backtick` `` quoted strings on a single line |\n\nValues are trimmed; empty values are dropped; keys are never extracted — one rule, shared by every extractor above. The fallback scan cannot see unquoted or multi-line strings, which is why the parsed formats and the source languages get real readers. Parse errors are silent unless `string-le.showParseErrors` is on.\n\n## The CLI\n\nThe same extraction runs from a terminal or a shell pipeline: a Rust CLI\nin [`crate/`](crate/README.md), sharing one corpus with the extension —\n[`crate/fixtures/`](crate/fixtures/) — so the two can never read a\ndocument differently.\n\n```bash\nstring-le .                      # every string in the tree, as JSON\nstring-le --values src/          # just the values, one per line\nstring-le --dedupe --values .    # each distinct string once\nstring-le mcp                    # the same extraction over MCP on stdio\n\n# the point of the whole thing:\nstring-le --values --dedupe src/ | sort > after.txt\ndiff before.txt after.txt        # what changed in the copy this release\n```\n\n**The reader is not the author.** The extension answers for the buffer\nyou have open. Someone still has to read every user-visible string before\na release — a QA lead, a compliance reviewer, a localisation owner — and\nthey do not have the editor open, and several of them cannot be handed a\ncheckout at all. The CLI puts the whole repository into one file they can\nread.\n\n**Source files are the main event there.** A `.ts` or `.py` file is where\nthe user-facing copy lives, so each language is read by its own literal\nsyntax and anything still unrecognised falls through to quoted-string\nextraction rather than being refused.\n\n**Exit codes follow grep** — 0 strings found, 1 none found, 2 the\nquestion was malformed — so finding nothing is an answer rather than an\nerror.\n\n## Commands\n\n| Command | Description |\n|---|---|\n| `String-LE: Extract Strings` (`Ctrl+Alt+E` / `Cmd+Alt+E`) | Extract all string values from the active document |\n| `String-LE: Deduplicate Strings` | Remove duplicate lines from the active document |\n| `String-LE: Sort Strings` | Sort lines alphabetically or by length |\n| `String-LE: Toggle CSV Streaming` | Enable/disable streaming for large CSV files |\n| `String-LE: Open Settings` | Open String-LE settings |\n| `String-LE: Help & Troubleshooting` | Built-in documentation |\n\n## Settings\n\n| Setting | Default | Description |\n|---|---|---|\n| `string-le.openResultsSideBySide` | `true` | Open results beside the current editor |\n| `string-le.postProcess.openInNewFile` | `true` | Post-process commands write to a new file instead of editing in place |\n| `string-le.copyToClipboardEnabled` | `false` | Also copy results to the clipboard (disabled for CSV output) |\n| `string-le.dedupeEnabled` | `false` | Deduplicate results automatically after extraction |\n| `string-le.sortEnabled` | `false` | Sort results automatically after extraction |\n| `string-le.sortMode` | `off` | `alpha-asc`, `alpha-desc`, `length-asc`, `length-desc` |\n| `string-le.csv.streamingEnabled` | `false` | Stream CSV results into the editor incrementally |\n| `string-le.showParseErrors` | `false` | Show parse errors as notifications |\n| `string-le.notificationsLevel` | `silent` | `all` = every notification, `important` = warnings + errors, `silent` = errors only |\n| `string-le.safety.enabled` | `true` | Guardrails for very large files/outputs |\n| `string-le.safety.fileSizeWarnBytes` | `1000000` | Warn before extracting above this file size |\n| `string-le.safety.largeOutputLinesThreshold` | `50000` | Offer Open/Copy/Cancel above this result count |\n| `string-le.safety.manyDocumentsThreshold` | `8` | Confirm before opening this many result documents (CSV multi-column) |\n| `string-le.statusBar.enabled` | `true` | Show the status bar item |\n| `string-le.telemetryEnabled` | `false` | Local-only event log (see Privacy) |\n\n## Languages\n\nTwelve languages besides English:\n\nGerman · Spanish · French · Indonesian · Italian · Japanese · Korean ·\nPortuguese (Brazil) · Russian · Ukrainian · Vietnamese · Chinese (Simplified)\n\nBoth halves are covered — the manifest (command titles, setting names and\ndescriptions) and everything shown while the extension runs (notifications,\nthe status bar, quick-picks and prompts). The extension follows VS Code's\ndisplay language, so it matches whatever the editor is already set to; no\nsetting of its own.\n\n## Privacy & security\n\n- **No network access.** The extension never sends data anywhere. The `telemetryEnabled` setting only writes events to a local Output Channel you can inspect (`String-LE`).\n- **The MCP server holds the same line.** It takes content as an argument and returns data: no filesystem access, no network calls, no telemetry. Your agent already has file-read tools, so duplicating them inside the server would add a path-traversal surface for no capability. `check:mcp-bundle` fails the build if the server ever imports something that could reach either.\n- Error notifications redact home directories and credential-shaped fragments.\n\n## Documentation\n\n| What | Where |\n|---|---|\n| What the tool is allowed to say — scope, output contract, refusals, non-goals | [`crate/SPEC.md`](crate/SPEC.md) |\n| How the extension is built and held together — architecture, invariants, toolchain, release | [AGENTS.md](AGENTS.md) |\n| How the CLI is built and held together | [`crate/AGENTS.md`](crate/AGENTS.md) |\n| What changed | [CHANGELOG.md](CHANGELOG.md) · [`crate/CHANGELOG.md`](crate/CHANGELOG.md) |\n| The tool's page, and the other fifteen | [letools.dev/tools/string-le](https://letools.dev/tools/string-le) |\n\n## Performance\n\n<!-- performance:start -->\n| Input | Size | Found | Time | Rate | Scan speed |\n| --- | --- | --- | --- | --- | --- |\n| JSON locale file | 1.77 MB | 40,000 | 9.53 ms | 4,198,116/sec | 185.9 MB/s |\n| YAML locale file | 1.01 MB | 30,000 | 13.33 ms | 2,250,169/sec | 75.7 MB/s |\n| CSV strings | 1.35 MB | 80,002 | 28.29 ms | 2,827,438/sec | 47.8 MB/s |\n\nMedian of 7 runs after warmup, on Apple M5 Pro, 24 GB RAM, Node 24.3.0. Inputs are generated\nby `scripts/benchmark.ts` rather than checked in, so the sizes above are\nexactly what was measured. Reproduce with `bun run benchmark`.\n\nThese are machine-specific and are not asserted in CI — a benchmark that gates\na build only tells you how busy the runner was.\n<!-- performance:end -->\n\n## Testing\n\n<!-- coverage:start -->\n| Metric | Coverage |\n| --- | --- |\n| Statements | 90.84% |\n| Branches | 83.48% |\n| Functions | 97.24% |\n| Lines | 92.26% |\n\n306 test cases across 24 files, plus an integration suite that runs\nin a real VS Code extension host and an end-to-end test that installs the\nbuilt `.vsix` into a clean profile.\n\nGenerated from a real run — `coverage/coverage-summary.json` and\n`coverage/test-results.json` — by `scripts/coverage-readme.js`; CI fails if\nthis section drifts. Reproduce with `bun run test:coverage`, and the case\ncount is the one vitest prints.\n<!-- coverage:end -->\n\n## More from the LE family\n\nSixteen single-purpose tools for the work in front of every model. Each ships\na Rust CLI and an MCP server. One page: **[letools.dev](https://letools.dev)**\n\n**Get it out**\n\n- **[String-LE](https://letools.dev/tools/string-le)** — Extract every string in a codebase, with its position, so a person can read them\n- **[Numbers-LE](https://letools.dev/tools/numbers-le)** — Extract every hardcoded number in a codebase, so a person can check them\n- **[Units-LE](https://letools.dev/tools/units-le)** — Extract every quantity with its unit, normalized, and refuse the ambiguous ones by name\n- **[Dates-LE](https://letools.dev/tools/dates-le)** — Extract every date and timestamp, and the exact instant each one resolves to\n- **[IDs-LE](https://letools.dev/tools/ids-le)** — Extract every UUID, ULID, NanoID, ObjectId and Snowflake, and decode the time inside\n- **[IPs-LE](https://letools.dev/tools/ips-le)** — Extract every IP address, CIDR block and MAC, normalized and classified by scope\n- **[URLs-LE](https://letools.dev/tools/urls-le)** — Extract every URL in a codebase, with its protocol and exact position\n- **[Paths-LE](https://letools.dev/tools/paths-le)** — Extract every file path in a codebase, and say whether it still points at anything\n- **[Colors-LE](https://letools.dev/tools/colors-le)** — Extract every color in a codebase, and say which ones are not in your palette\n\n**Check it**\n\n- **[Regex-LE](https://letools.dev/tools/regex-le)** — Find every regex in a codebase, and report which can be driven into catastrophic backtracking\n- **[Versions-LE](https://letools.dev/tools/versions-le)** — Find where one dependency is constrained differently across a repository's manifests\n- **[i18n-LE](https://letools.dev/tools/i18n-le)** — Identify the i18n library a project uses, then audit its catalogs by that library's rules\n- **[Scrape-LE](https://letools.dev/tools/scrape-le)** — Check whether a page is scrapeable before the scraper is written, and say when it cannot tell\n\n**Guard it**\n\n- **[Secrets-LE](https://letools.dev/tools/secrets-le)** — Find hardcoded credentials in a codebase, and never print one into the report\n- **[EnvSync-LE](https://letools.dev/tools/envsync-le)** — Compare the dotenv files in a tree, and say which keys are missing from which\n- **[Unicode-LE](https://letools.dev/tools/unicode-le)** — Find the Unicode that hides meaning — bidi controls, invisibles, homoglyphs, mixed scripts\n\nEach stands on its own: no shared crate, no published core. Where two of them\nagree, it is because the same answer was right twice.\n\n**Contact** — [nolindnaidoo.com](https://nolindnaidoo.com) · [GitHub](https://github.com/nolindnaidoo) · [LinkedIn](https://www.linkedin.com/in/nolindnaidoo/)\n\n## Also by nolindnaidoo\n\n**Rust** — pixelcoords and pixelactions are one loop: pixelcoords answers\n*where*, pixelactions *acts* there. Their own tools, their own voice — not\npart of the LE family.\n\n- **[pixelcoords](https://github.com/nolindnaidoo/pixelcoords)** — Freeze your screen, mark regions, get pixel-exact coordinates and crops\n  [pixelcoords.dev](https://pixelcoords.dev) · [crates.io](https://crates.io/crates/pixelcoords) · [docs.rs](https://docs.rs/pixelcoords)\n- **[pixelactions](https://github.com/nolindnaidoo/pixelactions)** — Consume human-verified coordinates, perform the interaction, confirm it landed\n  [pixelactions.dev](https://pixelactions.dev) · [crates.io](https://crates.io/crates/pixelactions) · [docs.rs](https://docs.rs/pixelactions)\n\n## License\n\nMIT © [nolindnaidoo](https://github.com/nolindnaidoo)\n",
  "bytes": 17278,
  "sha": "63e48711c239fa1088acead687ab4a799d354bf8190f1818ad031f15d588826b",
  "repo_slug": "nolindnaidoo/string-le",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_nolindnaidoo_string_le_bed5f746/readme"
}