Indeed

Search Indeed's job marketplace.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Indeed connector does

The Indeed MCP server connects Indeed's job marketplace to Claude. It searches listings by title, location and employment type, pulls full job descriptions, and returns application links. Anthropic lists two tools; Indeed's own documentation describes four. Sign-in is OAuth, and every scope the server requests is read-only.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Indeed tools (2)

  • search_jobs
  • get_job_details

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Anthropic's listing is short by two tools. The directory names search_jobs and get_job_details; Indeed documents four, and the server's own scope list corroborates the two extras. Both missing tools read data about the user rather than public listings.
  • The job_seeker scope family is undocumented. Indeed's OAuth reference publishes an application scopes table listing only email, employer_access and offline_access. None of the four scopes this server actually requests appears there, and we found no occurrence of job_seeker anywhere in Indeed's OAuth reference, glossary or three-legged OAuth guide. The wire metadata is the only enumeration of them that exists. The likeliest explanation is that Indeed treats this server as a consumer surface rather than a partner API: the MCP page is the one documentation page we saw that cites Indeed's consumer Terms of Service instead of the Additional API Terms and Guidelines notice every partner API guide carries, and its support link routes to the consumer help centre.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail is published here. Indeed publishes no parameter list either, beyond naming the search criteria in prose.
  • The connector is Claude-only by Indeed's own statement, despite using a standard transport.
  • The server is in beta. Indeed's documentation carries a legal notice describing the MCP server as offered in beta and subject to Indeed's Terms of Service and Privacy Policy, plus third-party AI model terms. Beta surfaces change without notice.
  • No published rate limits. We found no quota, throttle or rate-limit documentation for the MCP server. Absence of a published limit is not absence of a limit.
  • Whether a search writes anything to your account is unresolved. No tool or scope suggests a write, but we found no documentation stating whether searches create recent-search history on the Indeed account. We did not test it.
  • service_documentation in the authorization server metadata points at a redirect. The metadata names https://docs.indeed.com/authorization/, which 301s to https://docs.indeed.com/authentication. The page resolves, but the URL Indeed advertises is not the canonical one.
  • No machine-readable documentation index. llms.txt, llms-full.txt and the .md suffix route all returned 404 on docs.indeed.com, and the site's sitemap contains exactly one MCP URL. The nominated documentation page is the whole corpus for this connector.
  • The documentation host throttles automated readers. docs.indeed.com returned HTTP 429 after a modest number of requests during this check, refuses a plain non-browser user agent with 403, and 403s its own site search. This is rate limiting rather than a robots.txt restriction — robots.txt is Allow: /. Every URL cited below was confirmed 200 with no redirect.

Frequently asked questions

Can the Indeed connector apply to a job for me?

No. Nothing in the surface submits an application. All four OAuth scopes the server requests end in search or read, and Indeed's separate application product uses a different credential type entirely — its glossary lists Indeed Apply as generating an Indeed Apply API token rather than OAuth credentials. The connector returns application URLs for you to open yourself.

Does the Indeed MCP server read my resume?

Yes, if you grant it. Indeed's MCP documentation lists a Get Resume tool that retrieves the account holder's experience to personalise results, and the server requests a job_seeker.profile.read scope. Indeed's privacy policy defines an Indeed Profile as all application and contact information on the account, including resume information and screener answers.

How many tools does the Indeed MCP server have?

Anthropic's directory lists two and Indeed's documentation describes four. The directory names search_jobs and get_job_details only. Indeed's MCP page adds Get Resume and Get Company Data, and both are corroborated by scopes the server advertises over the wire. Treat two as an under-listing, not as the real surface.

What OAuth permissions does the Indeed MCP server request?

Four named scopes, and all of them are read. The server's RFC 9728 descriptor advertised job_seeker.jobs.search, job_seeker.profile.read, job_seeker.company.details.read and offline_access on 2026-08-22. No scope carries a write, apply or delete verb, and the same four appear on Indeed's authorization server.

Can I grant job search without granting resume access?

Indeed does not publish the connector's consent screen, so we cannot confirm whether the four scopes are offered separately. Indeed's OAuth reference does document incremental authorization, where an app requests only the scopes it needs, and a Third-party applications with account access page where the user can revoke a grant at any time. Revocation is the control we can confirm.

Is the Indeed MCP server free to use?

Indeed publishes no price or quota for it, and the documentation carries no plan gate. The page does state the server is offered in beta and subject to Indeed's Terms of Service and Privacy Policy, plus any third-party terms covering the AI model that talks to it. We found no published rate limit for the MCP server specifically.

Why can I not add the Indeed connector in my MCP client?

Because Indeed restricts it. Indeed's documentation states the server follows the MCP standard protocol but is available only for the Claude connector, so a generic client may be refused even though the transport is ordinary streamable HTTP. The connect instructions Indeed publishes cover claude.ai and Claude Desktop only.

What personal data leaves my Indeed account through this connector?

Your profile and resume content, if the Get Resume tool is present in your session. Indeed defines that data as including resume information, contact details and screener question answers. Job and company results are public marketplace data. Indeed publishes no field-by-field schema for what the profile read returns, so the exact extent is unconfirmed.

Sources

More Productivity connectors

  • 6sense

    Ask an AI agent about 6sense account insights, buying signals and keyword trends.

  • Adobe Workfront

    Find, create, update and delete Workfront work items from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Indeed to work.

Connect Indeed once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio
Call (650) 285-1019Our AI receptionist answers.