The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Install
claude mcp add fitter -s user -- "$(pwd)/fitter_mcp"Install command taken from the project's README or registry entry. Always review code before running it.
README excerpt
Read full README on GitHub →Fitter — web data for AI agents
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
How to use Fitter_MCP
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.
Quick start (Claude Desktop — one click)
Download fitter-mcp-<os>-.mcpb from the release page and open it — Claude Desktop installs the server automatically.
Quick start (Claude Code)
# 1. get the binary: download fitter_mcp_<version>-<os>- from the release page
# https://github.com/PxyUp/fitter/releases — or build it from source:
go build -o fitter_mcp ./cmd/mcp
# 2. register it once, available in every project
claude mcp add fitter -s user -- "$(pwd)/fitter_mcp"
Then just ask:
Get the top 5 HackerNews stories with titles and scores using fitter
The model calls fitter_config_reference, authors a config, optionally checks it with fitter_validate_config and executes it via fitter_run — all data fetching happens locally on your machine. For a ready-made pipeline try examples/config_morning_briefing.json:
Run examples/config_morning_briefing.json with fitter and give me the briefing
Register in Claude Desktop
{
"mcpServers": {
"fitter": {
"command": "/path/to/fitter_mcp"
}
}
}
Browser support (Playwright)
Similar plugs
Reverse engineer anything with agents, from app behavior down to native binaries.
Fair-code workflow automation platform with native AI capabilities. Combine visual building with custom code, self-host or cloud, 400+ integrations.
Build Agentic workflows, RAG pipelines, with rich AI model and tool support on one collaborative workspace. Deploy on cloud, VPC, or self-hosted, so teams move from prototype…
User-friendly AI Interface (Supports Ollama, OpenAI API, ...)