Remote Jobs MCP Server
OfficialRelated Servers
Alternatives to Remote Jobs MCP Server
- FlicenseNot gradedqualityDmaintenanceEnables searching for job opportunities across multiple platforms like Upwork, RemoteOK, and GitHub while automatically generating tailored application proposals based on keyword scoring. It includes tools for scanning all sources simultaneously and managing a professional profile for quick reference during applications.1-
Related Servers
- AlicenseBqualityBmaintenanceA fast, secure, and LLM-friendly Model Context Protocol (MCP) server that scrapes job listings from major platforms (LinkedIn, Indeed, Google) and converts them into structured Markdown format.11MIT
- AlicenseNot gradedqualityCmaintenanceWraps vuejobs.com's public API/RSS into a standard MCP server, letting any agent host search job listings by keyword, location, remote preference and posting date, and fetch full detail for a single posting. It is read-only, offers no apply proxy, and works with Cursor, Claude Desktop/Code, Codex and other MCP hosts.MIT
- AlicenseAqualityDmaintenanceMCP server that scours job openings from public, ToS-clean sources (Greenhouse, Lever, Ashby, HN, RemoteOK, Adzuna, USAJobs) and provides tools for job search, company listings, and salary context.4MIT
- AlicenseNot gradedqualityDmaintenanceRemote jobs MCP server — search 100,000+ remote jobs, post listings, find candidates, and check salary benchmarks from Claude, ChatGPT, Cursor, and any MCP client. Free, no API key required.21MIT
- FlicenseAqualityDmaintenanceA Model Context Protocol server that enables AI agents to search, analyze, and apply for Upwork jobs autonomously. It facilitates specialized job scoring, proposal submission, and integrated client messaging through a combination of browser automation and API access.1112-
- AlicenseNot gradedqualityCmaintenanceMCP server that provides tools to search and retrieve remote jobs from Remotive's public job board, with no API key required.MIT
TDQS
Scored across 12 tools
Most tools target distinct resources and actions, and descriptions explicitly differentiate the legacy tools (get_jobs, get_taxonomies) from their modern counterparts (search_jobs, list_taxonomies). The taxonomy trio (get_taxonomies, list_taxonomies, resolve_taxonomy) and the two job-search tools still require reading the descriptions to distinguish, but the guidance is clear.
All twelve tools follow a consistent verb_noun (or verb_noun_noun) snake_case pattern: get_job, search_jobs, list_taxonomies, resolve_taxonomy, get_company_jobs, etc. No mixed conventions or vague verbs.
Twelve tools is well within the ideal 3-15 range and each maps to a distinct facet of the domain (jobs, companies, roles, taxonomies). No tool feels redundant enough to be padding, aside from the intentional legacy-compatible pair.
The read-only surface covers jobs (search, detail, similar), companies (search, detail, jobs), roles (guide, related), and taxonomy resolution/lookup, giving solid lifecycle coverage for a public jobs API. Minor gap: no bulk/aggregate or saved-search style operations, but these are reasonable omissions for a read-only public feed.