Fitter turns any website or API into structured JSON — declaratively. One JSON/YAML config describes where the data lives (HTTP request, headless browser, file, static value) and what to extract (JSON paths, CSS selectors, XPath). No code, no brittle scraping scripts.
🚀 Try it in your browser — the real engine compiled to WebAssembly: live examples, a visual config builder, no install.
Because configs are plain data, LLMs can author them. The built-in MCP server lets Claude Code, Claude Desktop, or any MCP client write and run scraping pipelines on your machine, on demand:
"Get the top 5 HackerNews stories with titles and scores" → the model authors a fitter config, validates it, runs it locally, and gets clean JSON back.
One engine, five ways to use it:
| 🤖 Fitter MCP | MCP server exposing fitter to Claude Code, Claude Desktop and any MCP client |
| 🧠 Fitter Agent | AI-powered CLI: natural language → config → executed result |
| 🖥 Fitter CLI | run configs locally for test/debug/home usage |
| 📦 Fitter Lib | embed the engine in your own Go program |
| ⚙️ Fitter | long-running service mode with scheduling & notifications |
Why fitter for AI agents?
- Declarative & auditable — the agent produces a config you can read, save and re-run, not throwaway code
- Local-first — all fetching happens on your machine; no third-party scraping API, no keys, no per-request billing
- Batteries included — HTTP client, headless browser (Playwright/Chromium/Docker), JSON/HTML/XML/XPath/PDF parsing, pagination, cached references, host rate-limits — in a single static binary
- Reusable — what the agent authored today becomes tomorrow's cron job or service config
Fitter MCP is a Model Context Protocol server (stdio transport) which lets any MCP client — Claude Code, Claude Desktop, IDE assistants, custom agents — run Fitter configs and get structured JSON back.