Indeed MCP Server
Related Servers
Alternatives to Indeed MCP Server
AlicenseAqualityAmaintenanceDirect 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.8636MIT- AlicenseAqualityAmaintenanceEnables 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.210480 npm23MIT
- AlicenseAqualityBmaintenanceEnables searching Glassdoor job listings by keyword and location, then reading full postings with employer ratings, salary figures, and salary provenance as structured JSON.2296 npmMIT
Related Servers
- FlicenseAqualityBmaintenanceEnables searching and retrieving job listings from multiple platforms through MCP.2-
- 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.-
- FlicenseNot gradedqualityBmaintenanceEnables aggregated job scraping from LinkedIn, Indeed, Google Jobs, Adzuna, Jooble, Remotive, and Himalayas, with deduplication and retrieval of job postings via MCP tools.-
- AlicenseNot gradedqualityBmaintenanceLive Indeed job-postings data for AI agents via the RolesAPI REST API: search listings by keyword and location, and fetch role details, salary, description, company, and benefits. Available as drop-in agent skills or a hosted remote MCP server.MIT No Attribution
- FlicenseNot gradedqualityCmaintenanceEnables searching and fetching HiringCafe job listings through MCP, using public HTML pages without authentication or browser automation.67 npm-
- AlicenseNot gradedqualityCmaintenanceAggregates job listings from multiple ATS and job board APIs via MCP, enabling unified search and retrieval in a structured format without HTML parsing.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.