How to find jobs with Claude using the OpenRoles connector

To find jobs with Claude, add OpenRoles from Claude's connector directory, sign in to OpenRoles and allow access, then ask in an ordinary chat: "Find me backend roles in Bengaluru paying at least 30 LPA, posted this week." Claude searches the OpenRoles job timeline, reads your resume, and answers with real, open roles and a link to each one. Setup takes about two minutes.

The rest of this post covers what that connection actually lets Claude do, the exact steps, prompts that work well, and where the limits are.

Why a connector beats asking Claude to search the web

You can already ask Claude to "find product manager jobs in Pune" with web search switched on. What comes back is usually a handful of listing pages, some of them weeks old, some for roles that closed long ago, and almost none with a salary you can filter on. Claude is doing its best with what a search engine returns, and a search engine does not know which roles are still open.

A connector is different. It gives Claude a direct, structured way into one product's data, through the Model Context Protocol (MCP), the open standard Claude uses to talk to outside tools. With OpenRoles connected, Claude is not guessing from search snippets. It is querying a live timeline of open roles and getting back, for each one, the title, company, cities, whether it is remote or hybrid, when it was posted, and the CTC where the company published one.

That difference shows up the moment you add a constraint. "Only roles that publish a salary of 25 LPA or more" is a filter the connector applies exactly. On the open web it is a hope.

What Claude can do once OpenRoles is connected

The connector gives Claude a fixed set of tools, and they are named on the tools reference. In plain terms, Claude can:

• Find open roles. Engineer, product manager and designer jobs in India, filtered by role, city (Bengaluru, NCR, Mumbai, Pune, Hyderabad, Chennai or remote within India), minimum CTC in lakhs, keywords and how recently they were posted.
• Read your resumes. So it can tell you which roles fit what you have actually done, rather than what a job title suggests.
• Score a resume against the same criteria as the free resume score.
• Write a tailored version for one job from your resume and the posting, and save it to your account as a new version tied to that job. Your original is left alone.
• Track applications. Log that you applied, record a recruiter call or an interview, and tell you what is waiting on a follow-up.
• Remember your standard answers to the questions every form asks (notice period, expected CTC, work authorisation) so you write them once.

What it cannot do matters as much. An assistant connected to OpenRoles can't submit an application, edit an existing resume in place, pay for anything or change your plan. The full list is on the permissions page. You stay the one who applies.

How to connect OpenRoles to Claude

Connect with Claude

OpenRoles is listed in Claude's official connector directory, so there is nothing to configure by hand.

1. Press Connect with Claude above, which opens the OpenRoles listing in Claude's connector directory. You can also reach it from inside Claude: open Settings → Connectors, browse the directory and search for OpenRoles.
2. Choose to connect it. Claude opens an OpenRoles page.
3. Sign in to OpenRoles (or create an account), read what Claude will be allowed to do, and choose Allow.
4. Start a new chat, open the tools menu and check that OpenRoles is switched on.
5. Ask something simple to confirm it works: "What resumes do I have in OpenRoles?"

If your Claude workspace does not show the directory, you can add the same server as a custom connector instead: go to Settings → Connectors → Add custom connector, name it OpenRoles, and paste https://openroles.in/mcp as the server URL. The Claude setup page walks through each step, and troubleshooting covers the usual snags.

The connection needs an OpenRoles plan; pricing shows what is included right now.

Prompts that work well

Claude is good at turning a loose request into the right filters, so you can talk to it the way you would to a friend who knows the market. A few that get useful answers:

Find senior frontend roles in Bengaluru or remote in India, posted in the last 14 days, paying 35 LPA or more. Rank them by how well they match my latest resume.

I'm a product designer with four years in fintech. Which open design roles would actually want that background? Skip anything that's mostly visual or brand work.

Pick the three best matches from that list and tell me, for each one, what in my resume is strongest for it and what's missing.

Write a tailored version of my resume for the second one. Don't add anything I haven't done; if the posting asks for something I lack, tell me instead of writing it in.

I applied to the Pune fintech role today and have a recruiter call on Friday. Log both.

What have I applied to in the last month that I haven't heard back from? Draft a short follow-up for anything older than ten days.

The last two are where a chat interface earns its place. Keeping a job search organised is mostly bookkeeping, and saying "log it" is easier than opening a spreadsheet.

Will Claude make things up on my resume?

This is the right worry. Ask any language model for a "stronger" bullet without giving it a number, and it will often supply one. The post on using AI on a resume without lying covers why, and what to check.

The OpenRoles connector is built to push the other way. Its instructions tell Claude that everything in a resume it saves has to come from you, and a tailored resume is saved as a separate version, so your original is never overwritten and you can compare the two. Even so, read the tailored version before you send it. An Indian tech interview is very often a line-by-line walk through your resume, and you need to be able to defend every line.

From a match to an application

Each role Claude finds comes with a link to that job on OpenRoles. Open it and apply from there. If you use the OpenRoles browser extension, it fills the company's application form from your resume and saved answers, and you check every field and press Submit yourself. Nothing is sent on your behalf.

Then tell Claude you applied, or let the extension log it, and the application shows up in your tracker with the resume version you used. That matters the first time a recruiter mentions "the resume you sent" and you have three.

The same connection works in other AI assistants

OpenRoles speaks MCP, so Claude is not the only option. The same account connects to ChatGPT, Claude Code and Cursor, and to other MCP clients. Your resumes, saved answers and tracker are the same wherever you ask. If you would rather browse than chat, the jobs timeline is the same data on a page.