tw-jobs-mcp
Related Servers
Alternatives to tw-jobs-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables natural-language search and retrieval of Taiwan 104 job bank listings, including job details and company-specific openings, with filters for location, salary, experience, and remote work through an MCP interface.535 npm8MIT
- AlicenseNot gradedqualityDmaintenanceSearches job listings from Taiwanese job boards (104 and Yourator) and returns normalized results.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to pull live job listings from major ATS platforms (Greenhouse, Lever, Ashby, Workable), Hacker News hiring threads, and detect hiring signals on company career pages.-
- FlicenseAqualityBmaintenanceThis MCP server lets AI assistants search job listings on Taiwan's 104 Job Bank, read full job details, and prepare applications with human-in-the-loop confirmation before final submission.33-
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to search and explore remote job listings, salary stats, and popular roles, and supports token-authenticated actions like job alerts and apply redirects.MIT
- AlicenseAqualityBmaintenanceEnables querying open job postings directly from company applicant-tracking systems (Greenhouse, Ashby, Lever), finding a company's job board, listing and comparing roles, and accessing salary data, all without scraping or API keys.333 PyPI1MIT
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: search_jobs lists listings, get_job/get_company fetch single-entity details, salary_overview aggregates statistics, sources checks connectivity, and lookup_code resolves codes. Although salary_overview shares parameters with search_jobs, its statistical output (quartiles/median) versus listing output makes the boundary obvious.
All names use snake_case, with a consistent get_ prefix for the two detail fetchers (get_job, get_company) and verb_noun elsewhere (search_jobs, lookup_code). Minor deviation: salary_overview and sources are noun-only rather than verb-led, but still readable and predictable.
Six tools is tightly scoped for a job-search server: search, job detail, company detail, salary statistics, source health, and code lookup each earn their place with no redundancy.
The surface covers the full read workflow: discovery (search_jobs), drill-down (get_job, get_company), analysis (salary_overview), and supporting utilities (sources, lookup_code). Only minor gaps exist, such as no fetching of multiple jobs by ID in one call, but agents can easily work around this.