hardly
A generic, content-neutral CLI and MCP server for reading and capturing HAR files and turning them into what a client SDK needs: endpoints, forms and labels, data and media kinds, and how credentials and authentication work.
Why
Browser HAR captures are often tens of megabytes. Agents that read them burn tokens and still miss structure. hardly streams a HAR into SQLite once, then exposes small, redacted, paginated tools over MCP (and a matching CLI). Bodies are truncated, secrets are redacted, lists are paginated: you hardly need the whole file.
hardly knows technologies (HTML forms, ASP.NET WebForms, GraphQL, OAuth/OIDC, cookies/CSRF, bot walls, ArcGIS REST...) and resource kinds (JSON, CSV, HTML tables, PDF, images...), not any particular site. Downstream SDKs keep their own recipes and vocabularies. See docs/scope.md.
Install
pip install hardly # or: pipx install hardly / uv tool install hardly
pip install 'hardly[capture]' && python -m playwright install chromium # optional: record HARs
To work on hardly itself: pip install -e ".[dev]" (CONTRIBUTING.md).
Python 3.10+. Give an output path to save; otherwise nothing is written. Everything lives in
memory unless you pass output_path (hardly session open HAR -o index.db). Python:
with open_session(har) as s: ... (integrating.md).
60-second quick start
hardly guide mode # which of the three modes fits
hardly session overview path/to/capture.har # counts per server, method and status
hardly session site-brief path/to/capture.har # one-screen digest of a server-rendered site
hardly endpoint list path/to/capture.har --host api.example.com
hardly session report path/to/capture.har # one-pass findings with severity
hardly write export path/to/capture.har --format openapi -o api.yaml
hardly write export path/to/capture.har --format client_python --host api.example.com -o client.py
For agents, start with hardly_guide_task_plan(goal, har_path, url) (CLI:
hardly guide task-plan --goal ...): it returns an ordered plan with example calls and the current
environment state.
Names tell the effect
The CLI and the MCP server share one vocabulary: the command is the tool name without hardly_
(hardly_session_open is hardly session open HAR, hardly_send_entry is hardly send entry HAR 12 --confirm).
| First word | Meaning |
|---|---|
send |
sends requests to a real server; needs confirm=true (CLI --confirm), otherwise returns only a plan |
write |
writes a file; refuses to replace one unless overwrite=true (--overwrite) |
browser |
drives or reads a real browser |
| anything else | only reads loaded data |
Merged tools take a sections list, for example hardly_auth_report(sections=['credentials', 'cookies']). Reference: docs/tools.md (71 tools), docs/cli.md
(commands); stability promise: docs/api-stability.md.
Three modes
| Mode | When | Entry |
|---|---|---|
| archive | A HAR file already exists | hardly_session_open(har_path) then hardly_session_site_brief / hardly_endpoint_list |
| headless | Only a URL; an agent can drive the page | hardly_browser_capture_discover(url, analyze=true, confirm=true) (CLI hardly browser capture-discover URL --analyze --confirm) |
| interactive | Bot wall, captcha, MFA, complex UI | hardly_browser_start(headed=true), ask the person, then hardly_browser_stop |
After any capture, continue in archive mode on the returned session_id. hardly never evades
captchas or bot walls: it identifies them and tells you to stop, ask a person, or re-run elsewhere
(docs/gate-policy.md). Details: docs/capture.md.
Install and run without cloning
uvx hardly serve # MCP server over stdio (archive mode)
uvx --from 'hardly[capture]' hardly browser --help # with the Playwright capture extra
pipx install 'hardly[capture]' # or install the CLI permanently
hardly skill install # copy the Agent Skill into ~/.claude/skills/hardly
MCP client config for the published package:
{ "mcpServers": { "hardly": { "command": "uvx", "args": ["hardly", "serve"] } } }
Browser capture needs a local install ([capture] extra, then python -m playwright install chromium;
headed capture needs a display). The container image ghcr.io/b1tninja/hardly (multi-arch, built on each
release) is for archive/headless analysis only; mount your working directory at /workspace.
Release and verification details: docs/releasing.md.
MCP setup (Cursor and others)
Local venv (recommended; headed capture needs a display):
{
"mcpServers": {
"hardly": {
"command": "/path/to/hardly/.venv/bin/python",
"args": ["-m", "hardly"]
}
}
}
On Windows use ...\\.venv\\Scripts\\python.exe. hardly serve starts the same server.
Docker (offline analysis only; mount your working directory):
python scripts/build_image.py # builds hardly-mcp:latest (Windows: scripts\deploy-docker.ps1)
{
"mcpServers": {
"hardly": {
"command": "docker",
"args": ["run", "--rm", "-i",
"-v", "/home/me/work:/workspace",
"-e", "HARDLY_WORKSPACE=/workspace",
"hardly-mcp:latest"]
}
}
}
Host paths under the mount map to /workspace/.... To skip building locally, use the published
image ghcr.io/b1tninja/hardly:latest in place of hardly-mcp:latest.
Agent onboarding
hardly_guide_task_plan,hardly_guide_mode,hardly_server_status(stale MCP? restart the server),hardly_guide_help(topic).- MCP prompts:
analyze_har,discover_apis,capture_portal,document_api,find_auth_flow,reverse_engineer_api,build_client_sdk,diagnose_blocked_capture,verify_client. - MCP resources:
hardly://cheatsheetandhardly://docs/<name>for the bundled docs. - Agent Skill:
hardly skill install [--dest DIR](default~/.claude/skills/hardly), orhardly skill print. Source: skills/hardly.
Documentation
| Doc | Contents |
|---|---|
| docs/README.md | Index of all docs |
| docs/scope.md | What is in and out of scope; change checklist |
| docs/cheatsheet.md | One-page quick reference |
| docs/concepts.md | Sessions, index, redaction, modes |
| docs/sdk-workflow.md | Capture to client SDK, step by step |
| docs/reporting.md | hardly_session_report findings |
| docs/catalog.md | Target catalog, TargetAdapter, batch verify |
| docs/capture.md | Headless and interactive capture, recipes, env vars |
| docs/technologies.md | What is detected, per technology |
| docs/architecture.md | Data flow and design rules |
| docs/troubleshooting.md | Common first-use problems |
| docs/tools.md | Generated reference for every MCP tool |
| docs/cli.md | CLI grammar and every command (generated) |
| docs/api-stability.md | What is public and the v1 compatibility policy |
| docs/api-decisions.md | How the v1 names were chosen; old to new names |
Library use
from hardly import open_session
with open_session("capture.har") as s: # in memory; pass output_path= to save the index
print(s.conn.execute("select count(*) from entries").fetchone()[0])
Development and tests
pytest -q # offline; HARDLY_LIVE_CAPTURE=1 enables live Playwright tests
ruff check .
Live soak against public demo sites (no private HARs): hardly soak live --list, then
hardly soak live (or --ids datatables-ajax,quotes-login,…). Catalog covers loopback
WebForms/token login, HTML/AJAX tables, form logins, GraphQL, and JSON/OpenAPI — see
hardly.live_targets and docs/test-targets.md.
CONTRIBUTING.md, AGENTS.md; release notes in
CHANGELOG.md.
Security
HAR files often contain live passwords and session tokens. hardly redacts by default, but treat captures as secrets: do not commit or share them, and rotate credentials if one leaked. Use hardly only on targets you are authorised to access. See SECURITY.md.
License
MPL-2.0. Generated output (stubs, OpenAPI, reports) is not covered; see NOTICE.md.
Metadata
Release files for hardly 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| hardly-1.0.0.tar.gz | 642.4 kB | With provenance | Details for hardly-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| hardly-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for hardly-1.0.0-py3-none-any.whl |
Total release size: 1.2 MB
Release files / hardly-1.0.0.tar.gz
| Download URL | hardly-1.0.0.tar.gz |
|---|---|
| Size | 642.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
93338604fb2b1035a72732c25690371184435f36f124a59a97288783545c04eb
|
|
BLAKE2b-256 checksum How to use checksums |
40cb88de80c31727e13f822e78f5e09990e5f974cc3979059d76633f14eb5fa7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.
Transparency logRelease files / hardly-1.0.0-py3-none-any.whl
| Download URL | hardly-1.0.0-py3-none-any.whl |
|---|---|
| Size | 559.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ee2e23d8905816c460fa052f6f6df56d44fe68cc7833708b02abd09d12fda6eb
|
|
BLAKE2b-256 checksum How to use checksums |
de27d7b1368c7bdca51cbbff24d04eddd65fc7311ced3b8f5412e8a1788515b2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.
Transparency logSecurity for hardly 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for hardly-1.0.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.