
GoldenFlow
io.github.benseverndev-ossPublished by GitHub account benseverndev-ossv2.2.0Updated Oct 24, 2026
Standardize, reshape, and normalize messy data — CSV, Excel, Parquet, S3, databases.
Overview
GoldenFlow is a data transformation toolkit that lets an assistant clean, standardize and reshape messy CSV, Excel, Parquet, cloud-storage or database data.
- What you can do
- Transform files with zero-config auto-detection or a saved YAML config, with an audit manifest of every change made (R25, R33, R34). Profile columns, learn a config from data patterns, diff before/after files and auto-map schemas between sources (R36, R57, R58). Apply domain packs for healthcare, people/HR, finance, e-commerce and real estate (R62, R63). Normalize phones, dates, names, addresses, emails, categories and numbers through a large built-in transform library (R70, R71). Read and write S3 and GCS paths, stream large files in chunks, and watch or schedule recurring transforms (R41, R43, R46, R49).
- When to use it
- Useful when incoming data is inconsistent — mixed date formats, phone numbers in many styles, mismatched column names or messy categorical values — and you want repeatable, auditable cleaning before analysis, matching or loading into a pipeline (R10, R17, R20).
- Requirements
- Runs as a hosted remote endpoint or as a local process; the local server installs from PyPI with the mcp extra and is started with the mcp-serve command (R195, R196). Cloud connectors need access to the relevant S3 or GCS buckets (R43). LLM-enhanced mode needs an OPENAI_API_KEY or ANTHROPIC_API_KEY environment variable (R166).
Installation
In SourceWeft
- Open GoldenFlow in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.benseverndev-oss%2Fgoldenflow/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"goldenflow": {
"type": "http",
"url": "https://goldenflow-mcp-production.up.railway.app/mcp/"
}
}
}README
Moved. This repo has moved into the
benzsevern/goldenmatchmonorepo atpackages/python/goldenflow (and packages/typescript/goldenflow)/. This repo is archived; new development happens in the monorepo.
GoldenFlow
Data transformation toolkit — standardize, reshape, and normalize messy data before it hits your pipeline. Built by Ben Severn.
Works on files (CSV, Excel, Parquet), cloud storage (S3, GCS), or live databases. Zero-config mode auto-detects what needs fixing. One command to clean what GoldenCheck found and prep what GoldenMatch needs. Available in Python and TypeScript with full feature parity.
[PyPI] [npm] [CI] [codecov] [Downloads] [Python 3.11+] [Node 20+] [License: MIT] [Docs] [DQBench] [Open In Colab]
The Problem
Your data arrives broken in predictable ways:
- Phone numbers come in 15 different formats
- Dates are mixed between MM/DD/YYYY and YYYY-MM-DD
- Addresses have inconsistent abbreviations
- Column names don't match between systems ("fname" vs "first_name" vs "given_name")
- Values have leading whitespace, unicode garbage, smart quotes
- Categoricals are inconsistent ("USA", "US", "United States")
Every data engineer writes throwaway scripts to fix these. Every script is slightly different. None of them are reusable.
GoldenFlow makes the transforms reusable, composable, and automatic.
Quick Start
Python
TypeScript / Node.js
Programmatic (TypeScript)
Zero-Config Mode
GoldenFlow profiles every column and applies safe transforms automatically:
- Strips whitespace and normalizes unicode
- Standardizes phone numbers to E.164 format
- Normalizes email casing
- Parses and standardizes date formats to ISO 8601
- Normalizes zip codes (zero-padding, strip +4)
- Replaces smart/curly quotes with straight quotes
- Auto-corrects categorical misspellings via fuzzy matching
Output: a clean CSV with a sidecar manifest showing every transform applied.
The manifest is an audit trail — what changed, why, and which rows were affected.
CLI Commands
GoldenFlow has 14 commands. The most common ones:
Default Routing
Running goldenflow <file> without a subcommand auto-routes to transform:
Streaming
For files too large to load into memory, use StreamProcessor or the stream command:
Cloud Connectors
GoldenFlow reads from and writes to S3 and Google Cloud Storage transparently:
Cloud paths are detected automatically — no extra flags needed.
Watch Mode
Auto-transform files as they arrive in a directory:
GoldenFlow polls the directory and applies transforms to any new or changed files.
Scheduling
Run transforms on a repeating schedule:
Supported intervals: 30s, 5m, 1h, 2h, etc.
Setup Wizard
Generate a YAML config interactively:
The wizard profiles your data, suggests transforms, and saves a goldenflow.yaml ready to use.
History
GoldenFlow tracks every transform run in ~/.goldenflow/history/:
Each run record captures: source file, row count, transforms applied, errors, and duration.
Schema Mapping
When you need to merge data from different systems:
GoldenFlow auto-maps columns between schemas using name similarity and data profiling:
Ambiguous mappings get flagged for human review. Confident mappings apply automatically.
Domain Packs
Pre-configured transform sets for common industries. All 5 are now implemented:
Transform Library (76 transforms)
Text Transforms (18)
Phone Transforms (5)
Name Transforms (8)
Address Transforms (8)
Date Transforms (13)
Categorical Transforms (6)
Numeric Transforms (9)
Email Transforms (4)
Identifier Transforms (3)
URL Transforms (2)
Special Modes
Strict Mode
Fail immediately if any transform error occurs — useful in CI or production pipelines:
Exits with code 1 and prints the first 5 errors if any transform fails.
LLM Mode
Use an LLM to enhance categorical corrections and handle edge cases that fuzzy matching misses:
Requires OPENAI_API_KEY or ANTHROPIC_API_KEY in your environment. Falls back to standard transforms gracefully.
Auto-Correct
category_auto_correct uses fuzzy matching to fix misspelled categorical values automatically. It is suppressed on high-cardinality columns (>10% unique values) to avoid false positives.
YAML Config
For repeatable pipelines:
Generate a config from your data automatically:
Python API
Jupyter Notebook Support
TransformResult, Manifest, and DatasetProfile all have _repr_html_() — they render as rich HTML tables automatically in Jupyter:
TypeScript / JavaScript
GoldenFlow has a full TypeScript port with feature parity — same 83 transforms, same engine, same config format. The core is edge-safe (runs in browsers, Cloudflare Workers, Vercel Edge) with a Node layer for file I/O and CLI.
Install
CLI
TypeScript API
MCP Server (TypeScript)
REST API (TypeScript)
Public API (34 exports)
Integrations
REST API
POST CSV data, get transformed CSV back. Built with FastAPI.
MCP Server
Exposes GoldenFlow as an MCP tool for Claude Desktop. Configure in your Claude Desktop settings.
TUI
Full-featured terminal UI built with Textual. Browse profiles, apply transforms, preview results.
Remote MCP Server
GoldenFlow is available as a hosted MCP server on Smithery — connect from any MCP client without installing anything.
Claude Desktop / Claude Code:
Local server:
10 tools available: transform files, auto-map schemas, profile columns, generate configs, diff before/after, apply domain packs.
Part of the Golden Suite
Chain them:
Performance
Built on Polars (Rust-backed DataFrames). Transforms use a hybrid approach: native Polars expressions stay in the Rust engine for simple transforms (strip, lowercase), while complex transforms (phone parsing, date parsing) use optimized Python via map_batches.
Benchmarks
GoldenFlow scores 100/100 on the DQBench transform benchmark across all three tiers (customer database, e-commerce, healthcare claims).
Why GoldenFlow?
GoldenFlow is purpose-built for the transform step between validation and matching — not a general ETL tool. It turns messy data into clean, standardized data automatically.
Error Handling
GoldenFlow catches errors at the CLI boundary and shows friendly, actionable messages — no raw stack traces. Individual transform errors are captured in the manifest rather than crashing the run. Use --strict to change this behavior.
Progress Bars
Long-running operations (streaming, watch mode, scheduling) display a Rich progress spinner showing batch count, rows processed, and estimated completion.
GitHub: github.com/benzsevern/goldenflow Author: Ben Severn License: MIT Python: 3.11+ | Node.js: 20+ | npm: goldenflow | PyPI: goldenflow
Source: README.md at commit 7ce97e8
Tools
0Version history
1- v2.2.0LatestSep 16, 2026
Score
85% 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 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts