job-tracker-mcp
Related Servers
Alternatives to job-tracker-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to manage job applications and companies in a local SQLite-backed tracker, including searching, creating, updating, and deleting postings and companies, plus reading and updating shared job-search context.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to query, filter, and update job application records, and to analyze skill demand across postings.MIT
- AlicenseAqualityCmaintenanceEnables AI clients to read and query a daily job-scan dataset via four read-only tools, including searching job postings, viewing the latest report, and checking market statistics.451 PyPIMIT

LAYIQ Jobsofficial
AlicenseNot gradedqualityCmaintenanceEnables users to search public job listings and retrieve details for individual postings from inside AI assistants, including ranked results, filters, and pagination. It is read-only and requires no account, authentication, or API key.MIT- FlicenseAqualityDmaintenanceEnables tracking job applications through a pipeline, scheduling follow-ups, and summarizing job search progress via natural language.7-
- AlicenseNot gradedqualityCmaintenanceEnables LLM agents to search jobs, retrieve individual job details, access statistics, and mark application statuses by querying a SQLite-backed job database.MIT
TDQS
Scored across 3 tools
list_roles (filtered by status), due_this_week (filtered by date), and get_role (single company lookup) each have distinct retrieval semantics. There is minor overlap since list_roles and due_this_week both enumerate roles, but the filter dimension and output shape differ enough to guide selection.
list_roles and get_role follow a clean verb_noun pattern, but due_this_week breaks it as an adjectival/noun phrase with no verb. The set remains readable, but conventions are mixed.
Three tools is on the thin side for a job tracker, though each has a clear purpose and none is redundant. The surface feels like a partial slice rather than a fully scoped tool set.
The domain is job tracking, yet the server only provides read operations — no create_role, update_status, or delete/archive tools. Agents cannot actually track anything, only inspect existing records, which is a significant lifecycle gap.