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
- AlicenseBqualityDmaintenanceA 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
- AlicenseAqualityCmaintenanceMCP 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.20MIT
- 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
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol (MCP) server that connects AI coding assistants and agentic workflows to the Upwork freelance marketplace. Enables AI-powered job discovery, proposal generation, and contract management through a structured tool interface.MIT
TDQS
Scored across 2 tools
get_jobs retrieves job listings while get_taxonomies retrieves filter metadata, so the two tools have clearly distinct purposes. There is no overlap or ambiguity between them.
Both tools follow the same get_ noun pattern with snake_case naming. The names are predictable and clearly indicate that these are read-only retrieval operations.
Two tools is minimal, but it is not unreasonable for a narrow remote job lookup server. The count feels slightly thin rather than bloated or excessive.
The server covers the core read-only workflow: discovering valid taxonomy slugs and fetching paginated job listings with full descriptions. There could be additional conveniences like job detail lookup, but the primary use case is fully supported.