Support for Resume Lens

1. Download and build the local package

Install Node.js 24 or later. Download and unzip the source package, open a terminal in the extracted project folder, then run:

npm ci --ignore-scripts
npm run build
npm run demo

The first command downloads locked dependencies. The build prepares the local executable. The last command writes example reports; open outputs/demo/demo-after.html in a browser. Use a different output folder for another run because exports never overwrite an existing report.

For a compatible local plugin host, a portable plugin ZIP is also available. Follow its included README to prepare dependencies and connect the tool.

Portable plugin ZIP · version 0.2.1 · SHA-256a51dbccd44ff27203b0691baa1831be03636594cee1454222ca58ddeead13666

2. Generate a connection snippet

Replace the quoted example folders with folders you own and want this local server to read or write. The command prints a snippet; it does not modify your agent settings.

node dist/cli.js config --client codex --allow-root "C:/My Resumes" --export-root "C:/My Reports"
node dist/cli.js config --client claude --allow-root "C:/My Resumes" --export-root "C:/My Reports"
node dist/cli.js config --client hermes --allow-root "C:/My Resumes" --export-root "C:/My Reports"

Choose a narrow read folder and a separate report folder. Moving the project means you should generate a fresh snippet, because the command uses the real local path to Node and the server.

When a client offers the optional native local package, look for resume-lens-local. That label keeps the local file server distinct from the hosted resume-lensservice.

Codex

Merge the generated server entry into ~/.codex/config.toml.

Claude Code

Merge the generated server entry into the project's .mcp.json.

Hermes

Merge the generated server entry into ~/.hermes/config.yaml.

Keep your other entries. Restart or reload MCP connections as your client requires.

3. Check the source before using the result

Ask the agent to inspect the extracted text, then review the proposed job-description requirements. Confirm only what you actually checked. Keep the as-of date fixed if you compare versions, and do not invent accomplishments to make a percentage move.

Use Resume Lens to review my chosen resume against this JD. Check the extracted text and requirements, show evidence gaps, and export a local report. Do not invent qualifications.

Hosted text mode

The hosted edition works with a compatible MCP client. It accepts resume text and a job description that a person deliberately sends through their agent. It is not a website upload feature.

Use this Streamable HTTP MCP endpoint in a compatible client's connection settings:

https://resume-lens-mcp.sssatsangi97.workers.dev/mcp

The hosted edition is free and requires no account. For longer documents or repeated reviews, use the local package.

The free evaluation service checks the full request before it runs. These are hosted limits, not limits for the local edition:

Resume text

6,000 characters for resume text.

Job description

6,000 characters and 60 lines for a job description.

Requirement structure

30 requirement nodes and 40 term occurrences.

Summary comparison

10,000 total resume characters across both versions.

Evidence or report

5,000 total resume characters.

Additional density limits also apply. Oversized hosted input returns an explicit error. It is never silently truncated. The local edition retains its full offline limits. A rate-limit, CPU, or daily-quota error should stay visible in the agent instead of being treated as a completed review.

Need help with the public package?

Share the command you ran, the non-sensitive error message, and whether you were using the local package or the hosted text mode. Do not send a resume, job description, private report, or local folder path in a public message.

Contact Saran on LinkedIn ↗