FreeApply
OfficialFreeApply is a local MCP server for AI-assisted job applications: it finds/evaluates jobs, applies through your browser with truthfulness and pacing checks, tracks applications and replies, and keeps data on your computer.
Check readiness, Terms/setup status, signed workflows, and open the local dashboard.
Read/update profile, targets, eligibility, résumé text, cover-letter settings, Gmail, and AI-model preferences.
Fetch and trim job postings, score fit, claim/skip jobs, and enforce duplicate, site, pay-floor, and repost rules.
Check cover letters/answers for unsupported claims and save passing cover letters as PDFs.
Manage reusable answers and find whether you already have an employer-site account.
Get submit clearance with pace/daily-cap/auto-run checks, then update job status through applied, blocked, needs-info, etc.
Report job sites that are signed out or rate-limited.
Start/finish unattended auto-runs that keep applying while your AI app is open.
List jobs and get stats on applications, replies, interviews, offers, and response rates.
Run Gmail reply checks: plan, read, mark, finish, and record employer outcomes.
Preview or sync only the data-sharing choices you enabled.
Uses the Gmail connector to watch for employer replies to job applications, checking every 4 hours by default and optionally starring and/or labeling incoming replies.
FreeApply
Free AI job applications that run on your computer. FreeApply finds jobs that fit your settings, applies through the AI app you already use, tracks every application in a local dashboard and checks Gmail for employer replies. Any role, any field.
Website: https://www.mybotsai.com · Install: https://www.mybotsai.com/install/ · Downloads: https://www.mybotsai.com/appserver/ · Release notes: release-notes/ · Source: https://github.com/FreeApply/freeapply
Current version: 1.0.6 (notes). The app and its legal documents share one version number.
What it does
Finds jobs that fit: roles, pay floor and locations from your settings, on the job sites you choose. Duplicates and reposts it has already tracked are skipped.
Applies for you on employer sites and job boards with your real details, your résumé and answers you saved once, at a measured pace.
Never invents experience. Cover letters and answers are checked against your résumé and settings before they are used.
Knows when to stop. CAPTCHAs, new accounts, passwords and questions your settings don't answer go to the Issues tab for you.
Tracks everything in a dashboard at
http://127.0.0.1:7878, reachable only from your computer.Watches for replies: with the Gmail app password you connect in setup, new employer emails show up in the dashboard within about 15 minutes, and your AI app sorts them every 4 hours by default (the Gmail connector works too).
Keeps going on its own once setup is done, while your AI app is open; Start and Stop are at the top of the dashboard, with what it's working on right now.
Related MCP server: cv-job-assistant
Install
App | How |
Claude Desktop | Download |
Claude Code, Cursor, VS Code, Windsurf | Windows: |
Claude Code, from this repository |
|
Any other MCP app | Unpack |
To update, install the new version the same way. To uninstall, see https://www.mybotsai.com/install/#uninstall. Your
data in ~/.freeapply stays until you delete that folder.
First run
Restart your AI app and say "Set up FreeApply". The dashboard opens.
Read and accept the Terms of Service and Privacy Policy there yourself (18+). Until you do, every agent tool except
freeapply_get_statusandfreeapply_open_dashboardrefuses to run, and the agent can never accept for you.Fill in Settings: résumé (PDF, DOCX, TXT or MD), name and email, desired roles, minimum pay, locations, work authorization and the job sites you use. The agent applies nowhere until these are filled.
Sign in to your job sites in the browser your AI app uses, then say "Find me jobs and apply".
Setup ends with that conversation applying on its own until you press Stop in the dashboard; it also checks your email for replies every few hours and stars them, labels them, or both (your choice in Settings).
Guarantees
Facts about you come only from your résumé, your settings and what you tell the agent. It never invents experience.
It never types passwords, creates accounts or solves CAPTCHAs. Those jobs are flagged for you.
Signed workflow. The procedures, server instructions and hard limits ship in
agent/workflow.signed.json, signed with our release key. Any edit fails verification and locks the tools until the official copy is restored. Pacing, duplicate checks, the pay floor and the truthfulness check are enforced in the tool code, not just asked of the AI.Your data stays on your computer, except what your data-sharing choices send. The dashboard accepts only local requests that carry its own header.
Data sharing
Choice | United States | Everywhere else, or with Global Privacy Control |
Anonymous usage statistics | On by default, one-click opt-out | Opt-in |
Job-market data (no name or contact details; sold only as totals covering 5+ installations) | On by default, one-click opt-out | Opt-in |
Recruiter Talent Pool (contact details and résumé, sold to recruiters) | Opt-in | Opt-in |
Product update emails | Opt-in | Opt-in |
The region comes from your profile country, otherwise your computer's language and time zone; unknown counts as outside the US. In Settings → Data sharing you can preview exactly what is sent, sync now, and delete everything already shared. Details: Privacy Policy.
The dashboard shows one card labeled "Sponsored", chosen on your computer from a signed pack. No ad scripts, no trackers, and no data is sent to show it.
Dashboard
Overview, Applications, Replies, Issues and Settings, with the Terms, Privacy Policy, Disclosures and Recruiter Terms linked in the footer. The Needs you tab collects what needs you, in plain words:
Questions: what a form asked that your settings don't answer, each as a simple question you answer by typing, from a dropdown or by picking options. A question several jobs ask is shown once, and one answer goes to all of them; questions you already answered aren't asked again. The jobs then go back in the queue.
Accounts to make: one card per sign-up page, however many jobs wait on that account, with its link and a FreeApply Autofill bookmarklet that fills your name, email, phone and location on sign-up pages. Passwords stay with your browser or password manager.
Stuck: what the site asked for in plain words (a "prove you're a person" check, a code, a warning, a document FreeApply doesn't have, a question only you can answer), with "I applied myself", "Try again later" and "Skip this job".
Configuration
What | Where |
Data folder |
|
Use an existing database in place |
|
Dashboard port |
|
Dashboard only |
|
Flags |
|
Tools
18 tools, each with a title, annotations (read-only, destructive, idempotent) and a description of every parameter:
freeapply_get_status (can FreeApply run, plus the signed procedure for a task), freeapply_open_dashboard,
freeapply_get_settings (all settings or just the sections a step needs), freeapply_update_settings (settings, the
résumé text and profile, and the AI models scan that picks a model for each part of the work),
freeapply_fetch_posting (fetches and trims postings on your computer to save tokens, with their ATS keywords), freeapply_claim_job (claim or
skip a job, with the duplicate, job-site and pay-floor checks), freeapply_check_text (truthfulness check; saves a passing cover letter as a PDF),
freeapply_manage_answers (get a job's answers or save a reusable one), freeapply_find_site_account,
freeapply_clear_to_submit (clearance before each submit, and the unattended run's budgets), freeapply_update_job (your
side: found to applied), freeapply_report_site_problem, freeapply_manage_autorun (start or finish unattended runs),
freeapply_list_jobs, freeapply_get_stats, freeapply_check_replies (frames an email reply check; with an app password saved in Settings it reads, stars and labels the replies itself),
freeapply_record_outcome (what an employer did, from an email or the user), freeapply_share_data (preview or send
shared data). Removing a job is a dashboard action only (Applications → Remove); the agent has no tool for it.
Every call is checked against the tool's parameters first: a missing, unknown or wrongly typed parameter returns one
error naming each problem, and nothing changes.
Skills for Claude Code: freeapply-setup, freeapply-apply, freeapply-replies. Each points to its signed procedure.
Check a download
Every package comes with a .sig.json file holding its SHA-256, signed with an Ed25519 key whose private half never
leaves our offline machine. The public keys are in agent/keys/. Compare the checksum with the one in
latest.json:
Get-FileHash .\freeapply.mcpb -Algorithm SHA256 # Windows
shasum -a 256 freeapply.mcpb # macOS, LinuxThe installer and the app's own update check do this and the signature check for you; a download that doesn't match is refused.
This repository
Path | What |
| The app: an MCP server in Node.js with no dependencies, the dashboard ( |
| Claude Code skills that point to the signed procedures |
| Claude Code plugin and marketplace files |
| What changed in each version |
| MIT License for the source code |
License
The source code is released under the MIT License. The FreeApply name and logo are not covered by it; use of FreeApply and of the services we host is governed by the Terms of Service.
Contact
MyBotsAI · mybotsai@gmail.com.
Available Tools
18 toolsfreeapply_check_repliesRun a reply check: plan, read, mark, finishAIdempotent
Runs one email reply check (the freeapply-replies procedure), always beginning with action start, and, when the user saved an email login in Settings, reads and marks their mailbox itself. Each email found is recorded with freeapply_record_outcome. Use: start first; then read (start's mail.reader freeapply) or the Gmail connector (connector); mark after recording each email read returned; finish once everything found is recorded. Behavior: start: read-only, repeatable. read: signs in with the app password kept on this computer (you never see it), returns matching emails, changes nothing. mark: stars and/or labels one email as the user chose in Settings. finish: sets the last check to now, so the next check reads only newer email: only after recording everything found. Returns: start (the plan) {since, gmail (the user's mail settings: action none|star|label|star_and_label, label_name, ...), mail {reader: freeapply|connector, address}, applied [{job_id, company, title, submitted_at}], known_message_ids (already recorded)}. read {emails: [{gmail_message_id, gmail_thread_id, sender, subject, received_at, text}] newest first, already-recorded left out, count}. mark {mail_action} (for freeapply_record_outcome). finish {last_check}. Errors: an action other than start, read, mark or finish; read or mark without a saved email login; the mail server refusing the login.
Inputs: action (required), kind, gmail_message_id.
freeapply_check_textCheck text and save the cover letterAIdempotent
Checks a cover letter or free-text answer against what the user really has; saves a passing cover letter as a PDF to upload. Every piece of prose is checked here before you type or attach it (freeapply_update_job only records). Use: before typing any written answer or attaching any letter, and after each fix. Not for short fields straight from settings (name, date, yes/no). Behavior: flags every skill, tool, number or claim the résumé, settings, highlights and saved answers don't support. Without save, changes nothing. With save, a passing letter becomes a PDF in the documents folder, kept with the job; a failing one is never saved; saving again replaces the file; refused once the job is applied. Until setup has stored the résumé's text, most claims are reported unsupported. Returns: {ok, problems} (plain sentences: fix, remove or ask the user). With job_id also keywords {used, unused}: the posting's supported skills this text uses / could still use. With save also file {path, name, bytes}, or note (why not saved). Errors: save without kind cover_letter and job_id; unknown job_id.
Inputs: text (required), kind, save, job_id, +1 more.
freeapply_claim_jobClaim or skip a jobA
Claims a job before you work on it: duplicate check, the user's rules, starts tracking, returns the job_id every later call needs. Makes the job's first record (listing: freeapply_list_jobs; changing: freeapply_update_job). Use: before opening any application form; also to record a reviewed job you won't pursue (status skipped + status_note) so it isn't reviewed again. Not for a job already claimed. Behavior, first match wins: posting id already tracked: returns that job (existing true, nothing added); job site the user didn't choose, or signed out or paused: refused (refused says why, sites lists ready ones); same company and title as an applied job: refused as a repost; posted pay below the user's minimum: saved as skipped (rule pay_floor). Otherwise the job is added. A refused or existing claim changes nothing, so repeating the call is safe. Returns: {job_id, existing, status, rule, earlier}. earlier: up to 20 other jobs at the company [{id, title, company, status, same_title}]; if an applied one is clearly the same role under another title, mark this one skipped (freeapply_update_job). restart true (auto-run): the user saved new settings and wants them used now: don't work this job; the run finishes and starts again. Errors: a missing title or company.
Inputs: title (required), company (required), url, source, +12 more.
freeapply_clear_to_submitGet clearance to submitA
Go-ahead for one submit after checking the pace, the user's limits and, in auto-run, the Stop button. Comes right before the submit; freeapply_update_job refuses applied without its clearance. Use: right before every submit, with job_id. Not early, not for a job you won't submit now: each clearance counts toward the per-minute pace at once. Behavior: at most 3 submits a minute (or the user's slower setting) and the user's daily cap. A clearance: one job, 15 minutes, used up when applied is recorded; asking again for the same job issues a new one; kept only while FreeApply runs. Parameters: job_id ties the clearance to that one job (without it you only see the pace). method: external (employer or ATS form, the default), easy_apply or email; the pace and daily cap count submits by that method, and easy_apply also needs one-click apply allowed in Settings. run_id, only in auto-run (from freeapply_manage_autorun start), adds the user's Stop and limits, and counts as the run checking in. Returns: {clear, advice, last_minute, limit_per_minute, today, daily_cap}, plus clearance {job_id, expires_at} when clear. clear false: don't submit; prepare the next job, call again later. refused: one-click apply is off; apply on the employer's site or skip the job. stop_run true (with reason): the run must end now: freeapply_manage_autorun action finish. restart true: the user saved new settings and wants them used now: submit and record this job, start no other, finish the run; the next begins at once.
Inputs: job_id, method, run_id.
freeapply_fetch_postingFetch a job postingARead-onlyIdempotent
Fetches one job posting from the user's computer, trimmed: description, form questions, suggested answers, skills asked. Costs few tokens next to the browser, which you still use to fill and submit the form. Use: read each posting you found before scoring or applying. FreeApply has no job search of its own: search the user's job sites in the browser. Not for search-result or sign-in pages: read those in the browser. Behavior: read-only; one web request. Greenhouse, Lever, Ashby via their public APIs, other sites as page text. Public http(s) only: an address on this computer or a local network, or a redirect to one, is refused. Remembered this session, so freeapply_claim_job keeps its keywords. Parameters: url, the posting or its application form; max_chars caps only the description (default 6000, at least 500; description_chars tells you when it was cut); source, the job site where you found it (e.g. linkedin), picks the saved answers meant for that site. Returns: ats, title, company, location, work_mode, pay, description, description_chars (full length), questions [{label, required, type, options}], suggested_answers (from settings and saved answers; answer anything else only from the résumé or the user), keywords {matched, missing, coverage}: use matched in the posting's words, never claim missing; coverage = matched share in %, null if the posting names none. Errors: a bad or local address, or an unfetchable page, with the reason: read it in the browser. Next: freeapply_claim_job.
Inputs: url (required), source, max_chars.
freeapply_find_site_accountFind the user's employer-site accountARead-onlyIdempotent
Whether the user already made an account on an employer's careers site, and with which email. Employer sites only (job boards such as LinkedIn that signed the user out: freeapply_report_site_problem). Use: when an application form asks you to sign in or create an account. Not for signing in or up: FreeApply stores no passwords and you never type one. Behavior: read-only. The user records the accounts they make on the dashboard's Needs you tab. Parameters: site, the host the sign-in form is on, or any URL there. It is reduced to the domain without www. and matched exactly, so careers.example.com and example.com are different sites: pass the one the form is on. Returns: known account {domain, email_used, created_at, job_id, note}: ask the user to sign in in the browser, then continue in their session. None {domain, account: null}: freeapply_update_job status needs_account, account_url = the sign-up page. Errors: a site that isn't a domain or web address.
Inputs: site (required).
freeapply_get_settingsRead the user's settingsARead-onlyIdempotent
Reads the user's settings: who they are, what they seek and how FreeApply should work. Single form answers: freeapply_manage_answers; whether FreeApply can run: freeapply_get_status. Use: once per session or helper, and again after each auto-run go, before scoring jobs or filling a form. With the résumé text and the user's own words, the only source of facts about the user: never invent beyond it. To change: freeapply_update_settings. Behavior: read-only; never includes installation secrets. Parameters: sections, the sections to return (default all, named under Returns): ask only for what the step needs, e.g. ["profile", "eligibility"] for a form, and leave out resume, the largest, unless you need its text. Returns: {settings, missing}. Sections: profile, targets, eligibility, resume (file paths, text, profile; the user adds and replaces résumé files in the dashboard), cover_letter, automation, autorun, gmail, custom_answers, models, model_choices, sharing (choices only). missing: required fields still empty [{key, label}]; while non-empty, apply nowhere: open the settings tab (freeapply_open_dashboard) and ask the user to fill them. Errors: an unknown section; the message lists valid ones.
Inputs: sections.
freeapply_get_statsGet job-search statisticsARead-onlyIdempotent
The user's job search in numbers: applications, replies, interviews, offers, rates (individual jobs: freeapply_list_jobs; whether FreeApply can run: freeapply_get_status). Use: to report progress, e.g. when wrapping up a session. Not for finding a particular job. Behavior: read-only, cheap: counted fresh from the local database each call, nothing cached. No parameters. Returns: tracked, applied, applied_today, queued, needs_you (jobs waiting on the user), interviews, offers, rejections, acknowledged, response_rate (% of applications with a real reply; automatic acknowledgements not counted), avg_fit, last_reply_check (when the last Gmail reply check finished), counts by_status, by_outcome, by_method, daily (applications per day), top_companies, top_titles, top_jobs.
Inputs: no named parameters.
freeapply_get_statusCheck FreeApply and get a procedureARead-onlyIdempotent
Whether FreeApply can work now, plus the signed step-by-step procedure for a task. About FreeApply itself (user details: freeapply_get_settings; job search: freeapply_get_stats). Use: first in every session and before each task; with wait after asking the user to accept the Terms or finish setup in the dashboard. Works while locked or the Terms are unaccepted, so it can say why. Behavior: read-only: reports what FreeApply set up when it started (data folder, database, dashboard, the résumé copy to upload). wait holds the call up to 10 minutes until the Terms are accepted and setup is complete, and returns within seconds of that. Parameters: none for status only; procedure adds that task's signed steps; lane (with procedure freeapply-apply) is for a helper: only the hard rules and that lane's steps, with a short status; wait as above, with or without procedure. Returns: workflow {ok, problem}, terms {ok}, setup_complete, missing, sites [{id, name, ready}] (chosen job sites), autorun, update, dashboard (URL), data_dir, documents {dir, resume, cover_letters}, stats, procedures, models {can_delegate, rescan, levels, lanes, unfilled} (each level and lane {model, effort, source}; model current = your own model does it). With procedure also procedure {name, description, text, workflow_version, workflow_hash}, null while locked. wait_again true: a wait ran out first; call again. Next: workflow.ok false: tell the user why, stop. terms.ok or setup_complete false: follow freeapply-setup. models.rescan true: do its AI models step first.
Inputs: lane, wait, procedure.
freeapply_list_jobsList tracked jobsARead-onlyIdempotent
Lists the user's tracked jobs, most recent activity first (submitted, else updated, else found): the jobs themselves (totals and rates: freeapply_get_stats). Use: to find a job_id, look up one job by job_id, or answer questions about particular jobs. Not for adding or changing jobs (freeapply_claim_job, freeapply_update_job). Removing a job is the user's, in the dashboard. Behavior: read-only. Filters combine: a job must match all given. limit and offset page through the same order (default 200 from 0); a page shorter than limit is the last. Parameters: job_id returns just that job (empty if unknown); status and outcome match exactly; search finds text in the title, company or location, ignoring case. Returns: [{id, title, company, location, work_mode, pay_text, pay_min, pay_max, url, apply_url, fit_score, status, status_note, outcome, outcome_at, source, found_at, updated_at, method, submitted_at, confirmation, resume_path, cover_path, reply_count}]; empty when nothing matched.
Inputs: limit, job_id, offset, search, +2 more.
freeapply_manage_answersGet or save the user's answersADestructiveIdempotent
Gets or saves the user's own answers to specific form questions, so you never guess one (general details: freeapply_get_settings). A new question for the user goes through freeapply_update_job status needs_info instead. Use: get before retrying a job the user re-queued from the Needs you tab; save when the user answers a question in this conversation, for later forms. Save only the user's own words: saved answers count as facts in freeapply_check_text. Behavior: get is read-only. save replaces the answer saved under the same question; an empty answer removes it. Returns: get {job_id, answers: [{label, answer}] the user gave for this job, saved_answers: {question: reusable answer}, cover_letter: the job's saved letter {path, text} (text: for a text-box letter field) or null}. save {label, saved, removed, saved_answers}. Errors: get without job_id or with an unknown one; save without label; an action other than get or save.
Inputs: action (required), label, answer, job_id.
freeapply_manage_autorunStart or finish an auto-runA
Keeps FreeApply applying on its own from this session, with no scheduled task: start waits until something is due, finish ends a run (freeapply_get_status only shows the run state). Use: auto-run mode of freeapply-apply, which setup's last step enters: start with wait (takeover on the first call), finish after each run, then start again. Not in a session the user runs by hand. Behavior: start with wait holds the call up to 10 minutes while nothing is due (auto-run stopped by the user's Stop or a limit in Settings, the rest after a search found nothing new, the daily cap) and returns as soon as something is, within seconds of the user pressing Start. One session runs it at a time. A run checks in with each job-work tool call and freeapply_clear_to_submit (15 minutes without one counts as ended); freeapply_clear_to_submit with the run_id ends it at a hard stop. finish releases the run and starts the rest (autorun.every_hours), or none when the user asked for a restart with new settings; harmless on a run that already ended. Parameters: action start or finish. wait (start): hold as above; without it start answers at once. takeover (start with wait): only on the call right after the user asked for setup or to keep applying: it presses Start (clears a Stop, a reached limit and the rest) and makes this session the runner; the session it replaced gets replaced at its next start. run_id (finish): the run start returned. summary (finish): one line shown in the dashboard's run history. Returns: start {go: true, run_id, minutes (left before the time limit, null: none), max_applications, sites}; {go: false, replies_due: true}: do freeapply-replies, then start again; {go: false, needs_user: terms|setup}: ask the user (freeapply_open_dashboard), freeapply_get_status with wait, then start again; {go: false, wait_again: true}: start again; {go: false, replaced: true} or any other go false: end quietly. finish {finished, applied_this_run}, null for a run no longer active. Errors: finish without run_id; an action other than start or finish.
Inputs: action (required), wait, run_id, summary, +1 more.
freeapply_open_dashboardOpen the dashboard in the browserARead-onlyIdempotent
Opens the local FreeApply dashboard in the user's browser, one tab (freeapply_get_status only reports its URL). Use: when the user must act there: accept the Terms, fill settings, answer questions waiting on them, review applications and replies. Not for reading data: other tools return it. Behavior: changes no data. Starts the dashboard if needed at http://127.0.0.1:7878 or the next free port; reachable only from this computer. Parameters: tab, the page to open: overview (default; shows the Terms until they're accepted), settings (setup fields), issues (Needs you: questions, sign-ups), applications or replies. Returns: {url, opened}. url null: it couldn't start (no free port); tell the user. opened false with a url: no browser launched; give the user the url.
Inputs: tab.
freeapply_record_outcomeRecord what an employer didAIdempotent
Records what an employer did with an application (your side, e.g. applied or skipped: freeapply_update_job). Use: for each employer email found in a reply check, between freeapply_check_replies start and finish, and when the user tells you about a call or corrects an outcome. Not for your own steps. Behavior: with an email (gmail_message_id): stores it; raises the job's outcome only if this email ranks higher than the current one (an interview outranks an acknowledgement); the same gmail_message_id again stores nothing new. Without an email: sets the outcome exactly, whatever its rank. The email fields fill the dashboard's Replies tab. Returns: with an email {recorded (false: recorded before), kind, job_id, outcome (the job's, afterwards)}, job_id and outcome null without job_id; without one {job_id, outcome}. Errors: an unknown job_id; no job_id and no email; an empty outcome with an email.
Inputs: outcome (required), job_id, sender, company, +6 more.
freeapply_report_site_problemReport a job site signed out or limitedADestructiveIdempotent
Marks a job site the user chose in Settings (e.g. LinkedIn, Indeed) unusable for now: it signed the user out or showed its own daily limit (an employer's own careers site: freeapply_find_site_account). Use: as soon as a chosen site shows a sign-in page or a daily limit; then keep applying on the ready sites or company career sites. Never type a password. Behavior: signed_out: unavailable until the user signs in again and confirms it in the dashboard; limit_reached: paused until midnight. Meanwhile freeapply_claim_job refuses new jobs from it. Reporting again changes nothing; only the user can mark a site ready. Returns: {site, status, sites} (each chosen site with ready). Errors: a site the user didn't choose.
Inputs: site (required), status (required).
freeapply_update_jobUpdate a job's application statusADestructiveIdempotent
Sets a claimed job's status: your side of the application (employer's response: freeapply_record_outcome; adding a job: freeapply_claim_job). Use: after a submit (applied); giving up (skipped, failed); when the user must act: needs_info with the form's questions, needs_account with the sign-up page, blocked by a check you can't pass. Behavior: replaces the status. Enforced: applied needs a fresh freeapply_clear_to_submit clearance for this job; cover_text must pass the truthfulness check; an applied job only the user can change. needs_info questions go to the Needs you tab and re-queue the job once answered; if the user already answered them all, refused with the answers to use. A field marked for one status is refused with any other. Returns: {job_id, status} and when relevant: already_waiting; questions (each added, duplicate, grouped or already_answered, with its answer), questions_added; same_account (needs_account: jobs sharing one sign-up card); same_site (blocked: jobs blocked on the same site). Errors: an unknown job_id or a broken rule, saying what is missing.
Inputs: job_id (required), status (required), note, method, +7 more.
freeapply_update_settingsSave settings and résuméADestructiveIdempotent
Changes the user's settings: facts and preferences the user states, the résumé's text and profile (setup), and the AI models scan. Reading: freeapply_get_settings; single form answers: freeapply_manage_answers. Use: when the user states a fact or preference, in setup's résumé step, in the AI models step. Never fill a field the user didn't give you. Behavior: overwrites the sent fields, no undo. Deep merge: only sent fields change, nested objects merge, lists are replaced whole. User-only sections (legal, sharing, automation, autorun, onboarding, integrity, model_choices) are skipped and listed in ignored. All or nothing: one wrong field saves nothing. Parameters: patch, nested by section with the names freeapply_get_settings returns, e.g. {"targets": {"min_pay": 60000}}. Writable: profile, targets, eligibility, cover_letter, custom_answers (one at a time: freeapply_manage_answers), gmail (not last_check or manual_logins); resume only text and profile {headline, skills, titles, education, certifications}, taken from the résumé text alone; models only the scan {app, current, can_delegate, available, efforts}, read from your own tools, which replaces the last one. Returns: {changed, ignored, setup_complete, missing}; after a scan also models (model and effort chosen per level). Errors: nothing writable, unknown section or field, wrong type, value outside its choices (e.g. cover_letter.length short|standard|long), résumé files (the user adds them in the dashboard), malformed scan; the message names every problem.
Inputs: patch (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 18 tools
Each tool targets a distinct slice of the workflow (claim, update, list, stats, settings, replies, autorun, sharing), and descriptions carry explicit 'not for X, use Y' routing that preempts most confusion. The job lifecycle is deliberately split across claim_job/update_job/record_outcome/clear_to_submit, which an agent must learn, and several tools bundle multi-action parameters (get/save, start/read/mark/finish, preview/sync) that add internal selection burden.
All 18 names are uniformly snake_case with a consistent freeapply_ prefix, so the set is easy to scan and group. A few verbs are weaker than others (manage_autorun, manage_answers are generic; clear_to_submit is not a clean verb_noun phrase), but no convention mixing.
18 tools is slightly above the comfortable band, but the domain is genuinely broad (job lifecycle, settings, autorun sessions, email replies, site accounts, data sharing). Each tool maps to a real distinct operation, though a couple of the multi-action tools could be consolidated.
Coverage is strong: claim, update, list, stats, settings read/write, posting fetch, text verification, saved answers, submit clearance, site-signin handling, reply checking, outcome recording, and sharing are all present. Remaining gaps (deleting/untracking a job, résumé management, job search) are explicit and deliberately delegated to the dashboard or the browser, so agents can work around them.
Maintenance
Related MCP Connectors
searchnapply connects your AI agent to 800K+ open jobs taken straight from company career sites, kept up to date as companies add and close them. Search in your own words with the site's filters (role, location, remote, salary, experience, department), read postings in full, and tailor a resume or cover letter from your searchnapply profile. Save a search as a monitor to collect new postings and track what you applied to or skipped. It never invents a job or a salary, and it does not apply for you: you apply on the company's own page. Free plan included, within a daily call limit.
Job application tracker for developers - AI agents write over MCP, you review in a dashboard.
Your own job search in any AI: next steps, matches, résumés, applications, reminders. Free.
Run your tech job search from your AI agent: matches, job unlocks, applications and follow-ups.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables users to search for jobs, prefill applications using AI, and automate submissions across major platforms like Lever and Ashby directly from Claude or Cursor. It provides a full suite of tools for managing job queues, profile data, and resumes within a chat interface.37MIT
- FlicenseNot gradedqualityDmaintenanceEnables Claude to parse CVs, search job boards (Remotive, Arbeitnow, Adzuna, Greenhouse/Lever), tailor resumes and cover letters, and prepare application packages with direct apply links—without ever auto-submitting. It runs 100% locally and free, storing jobs and applications as JSON files.-
- FlicenseAqualityDmaintenanceEnables an LLM client to read a structured CV resource and send tailored application emails to recruiters via SMTP.1-
- FlicenseNot gradedqualityBmaintenanceEnables automated job searching from multiple boards, filtering matches against saved criteria, deduplicating seen postings, and tracking application statuses. Runs locally and integrates with Claude Desktop for natural-language queries and updates.-