jobsuche
Related Servers
Alternatives to jobsuche
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables an MCP-capable coding agent to run a local-first job search: recording verified opportunities in a private SQLite tracker, tracking follow-ups and outcomes, and preparing evidence-based resumes, application answers, and outreach drafts. It keeps all personal data on the user's machine and stops before submitting applications, uploading documents, or contacting anyone.1MIT
- AlicenseAqualityDmaintenanceA privacy-first MCP server for locally managing job, fellowship, and graduate-school applications. It offers tools for tracking application status, analyzing role fit, generating LaTeX CV/cover letters, interview prep, and discovering public jobs from ATS APIs.81MIT
- AlicenseNot gradedqualityDmaintenanceA local-first MCP server for tracking job applications, companies, and vacancies, storing everything in a single SQLite file and exposing 19 tools for managing the job search from clients like Claude.2MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that aggregates job listings from Remotive and Arbeitnow, with local SQLite caching, application tracking, and saved searches.66 npmMIT
- FlicenseAqualityDmaintenanceEnables searching job listings, tracking applications, managing resumes, and tailoring resumes to job posts, all locally via MCP.20-
- AlicenseNot gradedqualityCmaintenanceSearches LinkedIn, Indeed, USAJobs, and Google Jobs from the command line, deduplicates across sources, and optionally finds hiring manager emails; also runs as an MCP server for AI agents.MIT
TDQS
Scored across 6 tools
Each tool has a distinct role: remote search (search_ausbildung), remote detail fetch (fetch_offer_details), local tracking queries (list_offers), and status mutation (update_offer_status). The main potential confusion is list_offers vs. search_ausbildung, but descriptions clearly signal local SQLite vs. live API, so misselection risk is low.
All tools share the jobsuche_ prefix and mostly follow verb_noun style (fetch_offer_details, list_offers, search_ausbildung, update_offer_status, sync_and_export). auth_status deviates as a noun phrase, and sync_and_export bundles two actions, but the pattern remains readable and predictable.
Six tools cover a focused workflow (auth, search, fetch, sync/export, list, update) without redundancy. It is slightly lean — no removal/pruning operation and no standalone scoring tool — but each tool earns its place for this niche pipeline.
The core lifecycle is covered: session auth, discovery via search, detail retrieval, local tracking, status mutation, and bulk export. Minor gaps exist (no delete/archive of tracked offers, no manual add, no separate rescore), but agents can work around them via update_offer_status (e.g., 'ignored').