HasData Indeed

Indeed MCP Server

A hosted Indeed MCP server that gives Claude, Cursor, Windsurf and any other MCP client two read-only Indeed tools. Search job listings by keyword and location, and read a single posting in full, all as structured JSON, with no Indeed developer account and no partner approval.

It reads public job postings that a signed-out visitor can see.

1,000 free credits every month, no card required, which is 100 Indeed calls.

https://mcp.hasdata.com/mcp?apis=indeed

• Prompts and resources

Contents

• What you need
• Quick start
• Example prompts
• Tools
• Errors and failure paths
• Pricing, free tier and limits
• Tool selection
• How it compares
• FAQ
• HasData links
• Development
• Contributing
• License

What you need

An MCP client and a HasData API key from the dashboard, free to create with no card, and the free tier covers about 100 calls a month at the 10-credit rate. This is a remote server, so the simplest path is a URL and an x-api-key header, with no container to run and no Indeed developer account anywhere in the flow. A client that only speaks stdio reaches it through a thin launcher, published as @hasdata/indeed-mcp on npm and hasdata-indeed-mcp on PyPI, shown below.

Quick start

The server URL is the same for every client. We run it hands-on in Claude Code and Claude Desktop. The other blocks follow each client's own documented format for a remote server.

Clients with OAuth support can add the same URL as a connector and sign in without putting a key in a config file.

Claude Code

claude mcp add --transport http indeed "https://mcp.hasdata.com/mcp?apis=indeed" \

--header "x-api-key: HASDATA_API_KEY"

Claude Desktop

Settings, then Connectors, then Add custom connector, then paste https://mcp.hasdata.com/mcp?apis=indeed and sign in.

For the config-file route, Claude Desktop loads only local (stdio) servers, so it reaches a remote server through a stdio launcher. The @hasdata/indeed-mcp package is that launcher, and it reads the key from the environment. Add this to claude_desktop_config.json:

{

"mcpServers": { "indeed": { "command": "npx", "args": ["-y", "@hasdata/indeed-mcp"], "env": { "HASDATA_API_KEY": "YOUR_KEY" } } } }

For Python instead of Node, swap the launcher for the PyPI package, which uvx runs without a manual install:

{

"mcpServers": { "indeed": { "command": "uvx", "args": ["hasdata-indeed-mcp"], "env": { "HASDATA_API_KEY": "YOUR_KEY" } } } }

Cursor

~/.cursor/mcp.json for every project, or .cursor/mcp.json for one:

{

"mcpServers": { "indeed": { "url": "https://mcp.hasdata.com/mcp?apis=indeed", "headers": { "x-api-key": "HASDATA_API_KEY" } } } }

Windsurf

~/.codeium/windsurf/mcp_config.json. Windsurf calls the field serverUrl, not url:

{

"mcpServers": { "indeed": { "serverUrl": "https://mcp.hasdata.com/mcp?apis=indeed", "headers": { "x-api-key": "HASDATA_API_KEY" } } } }

VS Code

.vscode/mcp.json in the workspace:

{

"servers": { "indeed": { "type": "http", "url": "https://mcp.hasdata.com/mcp?apis=indeed", "headers": { "x-api-key": "HASDATA_API_KEY" } } } }

Example prompts

Prompts, not code. Paste one in and the agent picks the tool itself. Each is annotated with the calls it takes, because every successful call costs 10 credits.

Search Indeed for "python developer" jobs in New York sorted by date, and give me the ten most recent with company and salary.

*One call, 10 credits. A listing page carries company, salary and posted date already.*

Take the top posting from that search and pull its full description and requirements.

*One call, 10 credits. The listing carries a job URL, which the details tool takes directly.*

Find "data analyst" jobs in Austin, then pull full details on the three that list a salary.

*Four calls, 40 credits. One listing, then one details call for each of the three.*

Compare the salaries posted for "registered nurse" in Chicago against Houston.

*Two calls, 20 credits, one listing per city.*

Salary is on a listing only when the posting states one, so a "jobs with salary" prompt filters on the field rather than assuming it. Paging costs a call each time, through the start offset.

Tools

Two tools, read-only. Samples below are trimmed from real calls, and the numbers move as Indeed updates. Read them as shapes. Each tool name links to its endpoint reference, which carries the full field list.

The samples are the payload, not the whole response. A tools/call result carries one text block, and that text is itself JSON holding url, status, text and json, with the scraped data under json. From a raw JSON-RPC response the path is result.content[0].text, parsed, then .json. A chat client unwraps that for you and code talking to the endpoint directly does not.

Get Indeed job listings

hasdata_indeed_listing_getJobListings

A page of search results by keyword and location.

Returns searchInformation, a jobs array, peopleAlsoSearchFor, and pagination whose nextPage is the URL of the following page. Each job carries title, company, location, url, a short description, sponsored, the relative date and the absolute isoDate, a details array of labels like Full-time and Hybrid work, a benefits array, and a salary object when the posting states one.

A listing carries details as an array of plain strings. The job-details tool below returns details as an object with jobType and workSetting arrays. Same name, different shape, so read each per its own tool.

{

"title": "Hedge Fund Application Developer", "company": "TBA", "location": "Stamford, CT 06901", "url": "https://www.indeed.com/pagead/clk?...", "sponsored": true, "date": "30+ days ago", "isoDate": "2025-06-03T17:22:54.869Z", "details": ["Full-time", "Hybrid work"], "benefits": ["Health insurance", "401(k)", "401(k) matching"], "salary": { "min": 80000, "max": 150000, "type": "YEARLY" } }

Get Indeed job details

hasdata_indeed_job_getJobDetails

One posting in full, by its job URL.

Returns title, company, location, sponsored, a details object with jobType and workSetting arrays, a salary object when present, and the posting body in both description (plain text) and descriptionHtml (the same content with its list and paragraph markup kept). Use descriptionHtml when you want the structure and description when you want to feed clean text to a model.

{

"title": "Python Developer", "company": "Think IT Technologies", "location": "New York, NY 10114", "sponsored": false, "details": { "jobType": ["Contract"], "workSetting": ["In-person"] }, "salary": { "min": 60.5, "max": 65, "type": "HOURLY" }, "description": "Overview\nWe are seeking a Python Developer...", "descriptionHtml": " Overview We are seeking a Python Developer... " }

Prompts and resources

The server ships one prompt, a ready-made workflow a client can offer instead of making the user compose a tool call.

Alongside them the server exposes 4 resources, one per parameter whose accepted values are a fixed list. Reading one is cheaper than learning the vocabulary from a rejected call, and it costs no credits. Each URI is hasdata://indeed/ .

Both lists are served without an API key, so a client can read them before a user has signed up.

Errors and failure paths

Your client almost never sees an HTTP error code from a tool call. The MCP layer answers 200 and puts the failure inside the result, with isError set to true and the reason as text. The agent reads a message where you might expect a status line.

A wrong key surfaces as tool output, not as a failed connection. tools/list accepts any non-empty key and returns both tools, so the client completes its handshake and shows green. The first tool call then comes back with `isError: tr