Indeed MCP Server
Related Servers
Alternatives to Indeed MCP Server
AlicenseAqualityBmaintenanceDirect access to 40+ scraping and search tools. Extract structured data from Google (Search, Maps, Trends), Amazon, Airbnb, Social Media, and any web page directly into your AI agent.6317MIT- AlicenseAqualityBmaintenanceEnables MCP clients to perform live Google searches and retrieve structured SERP data including organic results, AI Overviews, People Also Ask, AI Mode answers, news, shopping, and short-video results via eight read-only tools.1064 npm14MIT
- AlicenseAqualityBmaintenanceEnables searching Glassdoor job listings by keyword and location, then reading full postings with employer ratings, salary figures, and salary provenance as structured JSON.259 npm7MIT
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables searching Indeed job listings by keyword and location, and fetching full details for a single posting via URL through a local bridge to the hosted HasData Indeed MCP server.MIT
- AlicenseNot gradedqualityCmaintenanceEnables users to search job postings with keyword, location, remote-only, date, and limit filters, and retrieve individual job details via MCP tools.MIT
- AlicenseAqualityBmaintenanceEnables searching and retrieving job listings from multiple platforms through MCP.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to search, count, and read open jobs from employer career sites and hiring platforms, with pay information and links to original postings, including through a no-account public endpoint.MIT
- FlicenseNot gradedqualityBmaintenanceEnables searching real job listings from multiple job boards (Indeed, LinkedIn, Glassdoor, Google Jobs, etc.) through a single MCP tool, designed for use as a custom connector in Claude Cowork.-
- AlicenseNot gradedqualityCmaintenanceEnables aggregated job scraping from LinkedIn, Indeed, Google Jobs, Adzuna, Jooble, Remotive, and Himalayas, with deduplication and retrieval of job postings via MCP tools.1MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct roles: one searches/fetchs the listing index while the other fetches full details for a specific job. There is no meaningful overlap or ambiguity in selecting between them.
Both tool names follow the same hasdata_indeed_<resource>_get<Action> pattern, with consistent snake_case prefixing and camelCase action suffixes. The naming is predictable and coherent across the set.
Two tools is on the low end for an MCP server, though the pair covers the essential list-and-detail retrieval flow for Indeed job data. The server feels minimal but not unreasonable for its focused purpose.
The server provides the core job-search workflow: get listings, then fetch details for a chosen URL. Minor gaps exist, such as no direct fetch by jobKey and no batch/company-level tools, but agents can accomplish the primary intended use case without dead ends.