Numbers-LE
Extract numeric values from JSON, YAML, CSV, TOML, INI, and .env.
What Numbers-LE does
Numbers are the values most likely to be wrong and least likely to be read. Numbers-LE pulls every numeric value out of a config, fixture or data file into a plain list, so ranges and outliers are visible at a glance instead of buried in syntax. It parses JSON, YAML, CSV, TOML, INI and .env, and falls back to scanning plain text for anything else.
What people use it for
Data validation
Pull the numbers out of a config or fixture and eyeball the ranges at a glance.
Config audits
Compare ports, thresholds and limits across INI, TOML and .env files.
CSV work
Extract everything, one column, or several columns into separate documents.
Install Numbers-LE
VS Code
ext install nolindnaidoo.numbers-leOpen Quick Open (Cmd/Ctrl+P) and paste.
Cursor / VSCodium
cursor --install-extension OffensiveEdge.numbers-leVS Code forks pull from Open VSX, where the namespace is OffensiveEdge.
ZedComing soon
npx -y numbers-le-mcpWorks in Zed today — add the command above as a custom MCP server from the agent panel, and extract_numbers appears in its tool list. The one-click listing in Zed's extension registry is a pull request awaiting review. Track the review.
AI agents
npx -y numbers-le-mcpRuns Numbers-LE's engine as an MCP server, so an agent can call extract_numbers with no editor involved. VS Code 1.101+ needs nothing — the extension registers it for you.
Where Numbers-LE lives
- VS Code Marketplacenumbers-le
- Open VSXfor Cursor and VSCodium
- GitHubsource, issues, changelog
- npmnumbers-le-mcp
- MCP registryio.github.nolindnaidoo/numbers-le
The other nine
Extract string values from JSON, YAML, CSV, TOML, INI, and .env — for i18n.
Pull every file path out of JS/TS imports, JSON, HTML, CSS, TOML, CSV, and .env files.
Extract and analyze colors from CSS, SCSS, LESS, Stylus, HTML, JS/TS, and SVG.
Extract URLs from documentation, configs, and code.
Extract date and time data from logs, configs, and code.
Find, test, and validate the regular expressions in any file — match reports and built-in ReDoS screening.
Check whether a page is actually scrapeable before you burn hours debugging.
Detect and sanitize credentials, tokens, API keys, and private keys locally — before you commit.
Spot missing keys across your .env files — automatic checks, a status bar counter, and a markdown report.