String Le logo

String Le

Extracts string values from structured files and source code through one MCP tool over stdio.

Install String Le

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "string-le": {
      "command": "npx",
      "args": [
        "-y",
        "string-le-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 1 tools correctly (Today).

Overview

The string-le MCP server extracts string values from JSON, YAML, CSV, TOML, INI, environment files, and source code. It accepts document content directly through the extract_strings tool and returns values in document order, with options for format, deduplication, multiline parsing, and result limits. It reads no files and makes no network requests, so reach for it when an agent needs to inspect content supplied by the host. The server runs over stdio through the string-le-mcp npm package.

Use cases

  • Extract translatable values from locale files
  • Review string settings in configuration files
  • Mine selected columns from CSV data
  • Inspect quoted strings in source code

Key features

  • Extracts values from structured files and source languages
  • Supports deduplication and multiline parsing
  • Caps results with truncation metadata
  • Processes CSV columns and large inputs
  • Runs over MCP stdio without API keys

Tools1

What String Le lets your agent do. Expand a tool for its parameters.

Verified live~362 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

9/9 checks healthy over the last 47d

What it can do

From the 1 tool this server returned when we ran it.

Read-only tools · 1
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age85 days
Maintainers1

Observed 2026-10-30 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 2d ago via OSV.dev · string-le-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads1.8kPackage downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed1Callable tools this server registers over MCP.

How String Le works

What the string-le MCP server does

The string-le MCP server gives MCP-compatible agents a way to collect string values from configuration files, data files, and source code. Its main use is extracting text for localization preparation, configuration review, or inspection of values in a document without returning keys, numbers, booleans, or other non-string values from parsed formats.

Supported structured formats include JSON and JSONC-style content, YAML, CSV and TSV, TOML, INI, and dotenv or environment files. It also understands string constructs in Python, Rust, Go, shell, PHP, Ruby, Perl, C#, JavaScript, and TypeScript. Markdown and unrecognized formats use a quoted-string fallback.

How it works

The string-le MCP server exposes one tool, extract_strings:

text
extract_strings(content, format?, filename?, dedupe?, multiline?, maxResults?)

The caller supplies the content rather than a path. The optional format selects a parser, while filename can provide context for format detection or reporting. Results preserve document order unless deduplication is requested. Empty values are removed, and results are limited to 500 by default; when the limit is reached, the response includes meta.truncated.

CSV extraction supports optional header handling, selected columns, and streaming behavior for large input. YAML supports plain and block or folded scalars, including multiple documents. Source-language readers handle constructs such as Python docstrings, Rust raw strings, Go backtick strings, shell heredocs, and JavaScript or TypeScript template literals.

Setup and configuration

Install and run the package with Node.js and npx:

Terminal
npx -y string-le-mcp

An MCP host can register it with a stdio configuration:

config.json
{
  "mcpServers": {
    "string-le": {
      "command": "npx",
      "args": ["-y", "string-le-mcp"]
    }
  }
}

You can also install the package globally and invoke string-le-mcp directly. The server needs no environment variables, API key, or server-specific configuration. It is available to Claude Code, Cursor, Windsurf, and other hosts that accept stdio MCP servers. VS Code 1.101 and later can use the related extension's agent-mode registration instead.

Tools and capabilities

The string-le MCP server provides:

  • String extraction from parsed data formats and programming languages
  • Optional deduplication and multiline handling
  • A configurable maximum result count
  • Document-order output
  • A fallback scan for quoted strings in unsupported formats
  • CSV column selection and large-file streaming support

Limitations and notes

The server does not read files from disk and does not make network requests. The host or agent must provide the document content. Parsed formats exclude keys and typed non-string values, while INI values are treated as strings because INI is untyped. The fallback parser only recognizes quoted strings, so it cannot extract unquoted text. Parse errors are silent in the underlying extraction behavior unless the surrounding String-LE tooling enables parse-error reporting. Unrecognized formats fall back to quoted-string extraction.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about String Le

string-le is an MCP server that connects MCP-compatible agents to string extraction for JSON, YAML, CSV, TOML, INI, dotenv, and source-code content. Its main tool, extract_strings, accepts document text and returns string values with options for format selection, deduplication, multiline parsing, and a maximum result count.

Run `npx -y string-le-mcp` and register that command as a stdio MCP server in your host. You can also install it globally with `npm install -g string-le-mcp` and configure the host to invoke `string-le-mcp` directly.

Yes, string-le works with Cursor through its Open VSX extension or by configuring the `npx string-le-mcp` stdio command as an MCP server. The MCP server accepts content from the host and does not require file access or network connectivity.

It supports JSON, YAML, CSV, TSV, TOML, INI, dotenv, Python, Rust, Go, shell, PHP, Ruby, Perl, C#, JavaScript, and TypeScript. Markdown and other unrecognized formats use a fallback scan for quoted strings.

No, it needs neither an API key nor environment variables. The stdio server runs with the `string-le-mcp` command and receives document content directly from the MCP host.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewString Le AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/string-le?style=directory)](https://allmcps.com/mcp/string-le)
HTML Embed
<a href="https://allmcps.com/mcp/string-le"><img src="https://allmcps.com/api/badge/string-le?style=directory" alt="String Le on AllMCPs" /></a>