Jobgent
Related Servers
Alternatives to Jobgent
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables LLM clients to analyse job postings, tailor resumes from an evidence-labelled profile, validate every claim against that profile, and track applications, all through deterministic MCP tools.7Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to discover postings from watched company boards ranked by keyword fit, tailor and fact-check resumes against a source-cited profile, render ATS-readable PDFs, submit applications through the user's own browser, and track replies and follow-ups. All ranking, claim checking and email classification run as plain code, so LLM tokens are spent only on writing.1Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to run a deterministic job-application pipeline over MCP: scoring fit against a profile's evidence, drafting market-aware CVs and cover letters for 15 country conventions, and shipping documents only after an ATS-style gate checks page count, text layer, raster layout and naming. Writes require explicit confirmation, and every command returns a single JSON envelope with meaningful exit codes.1MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that exposes job-search and application-management capabilities to compatible AI clients, enabling discovery of vacancies, drafting of tailored application materials, and coordinated human-approved submissions.MIT

Civify MCP Serverofficial
AlicenseAqualityBmaintenanceEnables AI agents to parse resumes, tailor CVs, score ATS compatibility, redact PII, scrape job postings, and track applications through a career platform.823 npmAGPL 3.0- AlicenseNot gradedqualityBmaintenanceEnables AI clients to serve as a personal career analyst by searching, matching, and explaining job recommendations, managing job applications, and syncing public job boards through standardized MCP tools.MIT
TDQS
Scored across 33 tools
Several tool clusters overlap in purpose: jobs_fetch vs jobs_search vs agent_run all bring in postings, job_score vs job_evaluate both score a job, and pack_create vs pack_prompt/pack_submit produce application packs. Descriptions do clarify the deterministic-vs-agent-mode split and the step-1/step-2 pairing, but an agent still has to read carefully to pick the right entry point.
Mostly snake_case with noun_verb or verb_noun shapes, but prefixes are inconsistent (job_score vs jobs_fetch vs jobs_list, application_set_status vs applications_list) and some names are nouns rather than actions (agent_queue, cv_outline, stats, learning_gaps, interview_prep, evaluate_prompt vs pack_prompt). Readable, but the convention shifts between singular/plural and verb/noun forms.
33 tools is heavy for this domain, and much of the bulk comes from duplicated paths for the same outcome (job_evaluate/evaluate_prompt/evaluate_submit, pack_create/pack_prompt/pack_submit, jobs_fetch/jobs_search/agent_run). The set would be tighter if the agent-mode pairs were folded into a mode flag on the deterministic tools.
Coverage is broad across the lifecycle: profile read/write/add/remove/import, CV outline and PDF export, job ingestion, search, evaluation, pack generation, application status tracking, stats, learning gaps and interview prep. Minor gaps exist (no explicit job removal from the feed, no listing of generated pack documents beyond pack_get), but agents can work around them via application_set_status.