DrawOffer MCP Server
Related Servers
Alternatives to DrawOffer MCP Server
No user-submitted related servers found.
Related Servers
AlicenseAqualityBmaintenanceEnables AI clients to browse public job listings, save and rank roles into a pipeline, tailor resumes and cover letters, submit applications, and track replies, interviews, and escalations over time. Works anonymously for job browsing or with a scoped API key for full account, apply, and recruiter-outreach capabilities.7415MIT- FlicenseNot gradedqualityBmaintenanceEnables Claude Web users to manage their job application workflow by storing profile and resume data, analyzing job descriptions, preparing applications, and tracking progress — all with manual submission and no platform automation.1-
- AlicenseAqualityCmaintenanceEnables parsing a master resume, analyzing job descriptions for ATS/match scores, generating truthful tailored resumes, tracking applications, and producing PDF reports through Claude Desktop.17MIT

hirly MCP serverofficial
AlicenseNot gradedqualityCmaintenanceConnects an AI assistant to a job-matching account so it can read roles matched to your resume, pull full job details and hiring contacts, and save tailored resume versions. With explicit opt-in and per-job confirmation in the chat, it can also start applications, relay questions only you can answer, and report each application's status.MIT- AlicenseBqualityBmaintenanceEnables job seekers to search live job listings from public job APIs, store their profile and resume locally, and get help tailoring resumes, generating cover letters, analyzing job match gaps, preparing for interviews, and tracking application status. All of this runs inside Claude without requiring any API key.12MIT
- AlicenseBqualityCmaintenanceEnables Claude Desktop, Cursor, or any MCP client to search six job portals, score CV-to-posting fit with ATS-style gates, tailor resumes and cover letters, export Word documents, and track applications locally.9MIT
TDQS
Scored across 8 tools
The set splits cleanly into three resources (resumes, jobs, applications) each with obvious read tools, so an agent can pick list_/get_ variants confidently. The one soft spot is create_job vs create_application: create_job silently also creates a '待投递' application record, which overlaps with create_application and could make an agent choose the wrong entry point for logging a new opportunity.
Every tool follows the same verb_noun snake_case pattern (list_resumes, get_resume, create_job, create_application). Resource nouns are reused consistently across the set (resume/job/application), so names map predictably to the domain model.
Eight tools is well within the sweet spot and each one maps to a concrete job-seeking step (browse resumes, read JD, save JD, log/track application). No tool looks like filler or a near-duplicate.
Read coverage is solid for all three resources, but the write surface is thin: there is no way to update or delete a job, no way to advance or change an application's stage (the core action in a job tracker, despite get_application exposing 'current stage'), and resumes are read-only with no edit/upload path. Agents can read and create but will hit dead ends for the main lifecycle mutation.