Summary
The CV gets fixed at the moment you notice it is out of date.
Searching postings and editing the profile they match against are the same session, so a role that wants something you have done but never wrote down can be handled before you apply rather than after you are filtered out. Every write points back at the CV page on lapras.com, which is where you confirm what actually landed.
What it is
A LAPRAS client in two halves: a job search over postings, and write access to the profile those postings are matched against — work experiences, job summary, career aspirations and tech skills.
What you get
- Job search filtered by keyword, position, minimum annual salary, employment type, business type and work style
- The same search narrowed by programming language, framework, database and infrastructure, and by preferred conditions
- Full detail on a posting, including the URL the application goes through
- Work experiences listed, created, updated and deleted, each with organisation, position, a client-work flag and start and end month and year
- Your job summary read and rewritten
- Your stated career aspirations read and rewritten
- The tech skills list read and replaced
Requirements
A LAPRAS account with its API key in LAPRAS_API_KEY, and npx on your PATH.
Setup effort
One command plus a key — npx -y @lapras-inc/lapras-mcp-server, then supply credentials