Fitter

{
  "mcpServers": {
    "fitter": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "FITTER_PLUGINS",
        "ghcr.io/pxyup/fitter-mcp:v1.8.3"
      ],
      "env": {
        "FITTER_PLUGINS": "your-value"
      }
    }
  }
}

claude mcp add --env FITTER_PLUGINS=your-value --transport stdio fitter -- docker run -i --rm -e FITTER_PLUGINS ghcr.io/pxyup/fitter-mcp:v1.8.3

{
  "mcpServers": {
    "fitter": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "FITTER_PLUGINS",
        "ghcr.io/pxyup/fitter-mcp:v1.8.3"
      ],
      "env": {
        "FITTER_PLUGINS": "your-value"
      }
    }
  }
}

{
  "servers": {
    "fitter": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "FITTER_PLUGINS",
        "ghcr.io/pxyup/fitter-mcp:v1.8.3"
      ],
      "env": {
        "FITTER_PLUGINS": "your-value"
      }
    }
  }
}

Config formats checked against the official docs on Oct 7, 2026: modelcontextprotocol.io (opens in a new tab), code.claude.com (opens in a new tab), cursor.com (opens in a new tab), code.visualstudio.com (opens in a new tab).

• fitter_run

  Run a Fitter config passed inline (JSON or YAML string) and return the extracted data as JSON.

• fitter_run_file

  Same as fitterrun but reads the config from a local .json/.yaml file

• fitter_run_url

  Same as fitterrun but downloads the config from an HTTP(S) URL, e.g. a raw GitHub link

• fitter_inspect_url

  Fetch a URL and return a compact structure outline + candidate selectors/paths (gjson paths for JSON;…

• fitter_validate_config

  Validate a config without executing it (structure, responsetype, connector data source, model).

• fitter_config_reference

  Return a condensed reference of the whole config format (connectors, parsers, model/field schema, placeholders,…

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.

• api
• go
• parsing
• scraper
• scrawler
• golang
• json
• ai-agents
• mcp
• mcp-server