Claude BrightHire connectorWhat Claude can do in your BrightHire account.
The Claude BrightHire connector exposes 11 tools. All 11 read, 0 write: interviews, transcripts, notes, scorecards, guides. Below: what Claude can look up for a debrief, what it cannot do, and who has to switch it on first.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for recruiters and hiring managers
BrightHire records and summarises interviews. With the connector, the transcripts, scorecards, AI notes and guides it already holds become something you can question in Claude. You ask about a candidate, a role or your own interviews, and Claude pulls the right records itself and answers in the conversation.
Walking into a debrief prepared. search finds the interviews for a candidate, then get_scorecards and get_call_ai_notes line up what each interviewer rated and what the candidate answered, so the panel starts from the same page.
Preparing the next call in minutes. get_scheduled_interviews shows what is coming this week and get_interview_context gathers the guide, the candidate summary and the position details for one of them.
Checking a profile against the role. get_job_description brings back the posting, which Claude can set against the transcripts from get_transcripts when exact wording matters.
What Claude will not do here. By default the sheet only exposes reading: no tool writes a scorecard, moves a candidate or books an interview. It sees only the data you already have permission to view in BrightHire, and it retrieves nothing unless asked. Nothing runs on its own either: no tool fires after an interview ends. Background jobs of that kind belong to an automation tool, a different job, gathered on the Integrations hub. For another HR tool, see the Claude bamboohr connector.
Five words before you plug it in
The vocabulary you will meet while connecting BrightHire.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in that account while it answers you.
- Tool
- One named thing the connector lets Claude do. Claude picks the ones it needs by itself, and the directory sheet lists them by name.
- Authorization
- The service's own sign-in screen, where you hand Claude the access it will use later. Given once per person, and taken back the same way.
- Approval
- The confirmation Claude waits for before it goes through with a change to your account, shown in the chat at the moment it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant such as Claude talk to an outside service like BrightHire.
Connecting BrightHire to Claude in three steps
- 01
Find BrightHire in Claude
In Claude's settings, open Customize, then Connectors, and look for BrightHire in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on before each member can sign in.
- 02
Start the connection
Click Connect on its row, then sign in to BrightHire in the window the service opens itself. If the link breaks later, Disconnect and connect again from the same row.
- 03
Read the authorization screen
Read BrightHire's screen before you accept it. It belongs to the service, not to Claude, and it decides what the access covers. You can also withdraw that access later from your BrightHire account itself.
The 11 tools, sorted by what they do
BrightHire gives Claude 11 tools: 11 that read your account, 0 that change something in it.
One group only: every tool on the sheet reads. Tool names stay as Claude shows them.
- 11 read
What Claude reads (11)
11 toolsEleven tools that look up interviews, notes, scorecards and guides without changing anything.
search
The starting point for almost every question. It looks through interviews by candidate, interviewer, position, department, stage, date range, outcome or call type, and returns the metadata plus the call IDs the other tools need.
get_scheduled_interviews
Looks ahead at interviews on the calendar, the next seven days unless you say otherwise. You can narrow it to a candidate or a job title, and to your own interviews or the whole organisation.
get_interview_context
Gathers the full preparation pack for one upcoming interview: start time, candidate and position details, the interview guide and the candidate summary, in a single answer.
get_interview_summary
Returns the recap of one finished interview: interviewer notes, emoji reactions such as thumbs, stars or flags, and links back to BrightHire, the share page and the ATS scorecard.
get_call_ai_notes
Pulls the question-and-answer pairs BrightHire's AI extracted from transcripts, for up to 20 interviews at once, and can filter by keyword or by who was speaking.
get_transcripts
Brings back full, word-for-word transcripts and the call notes people wrote, for up to 20 interviews. It is the heavy option, meant for when exact wording matters more than a summary.
get_candidate_summary
Returns the most recent summary notes BrightHire holds on one candidate, a quick read on where they stand across their process.
get_scorecards
Reads the ATS scorecards for up to 20 interviews, with the overall recommendation, the attributes rated and the questions. It works from call IDs or from a candidate paired with a position.
get_job_description
Fetches the job description of a position, using the ID that search results return. Claude can then weigh what candidates said against what the role actually requires.
get_interview_guide
Retrieves the interview guides attached to scheduled interviews, up to 20 at a time, with their questions and competencies.
get_coaching_report
Gives your personal AI coaching report as text, summarising trends and feedback from your recent interviews. It needs no input: it works out who you are from the session.
What Claude checks with you before acting
By default, Claude stops and asks for your go-ahead before each action it takes on an account on your behalf. The request shows up in the chat, right when it matters.
On Team and Enterprise, the owners decide whether a member may let some actions through without being asked every time. They can also limit what a connector may do for the whole organisation, keeping reading open and closing writing, for instance. That setting applies to everyone and nobody works around it from their own account. Claude also works with your rights and nothing more: BrightHire states that access follows its own permission model, so you only reach data you can already view.
Which Claude plans include it
Out of the 819 sheets in the official directory, none shows availability by plan. The connector-by-connector answer is not published anywhere: it is a real gap in the catalogue.
The general rule is published: remote connectors are open to every user on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organisation before members can connect. For the current state of this one, check the connector's sheet in the official directory. On BrightHire's side, an administrator still has to enable the server, a separate step from anything in Claude.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when an interview ends, a scorecard is filed or a candidate moves stage.
Everything here comes from BrightHire's help centre: neither Claude's help centre nor Anthropic's developer docs have a page on this connector. The tool list is an observed floor, not a promise, since an admin can open actions no public sheet shows. The directory's partner badge is not a security audit either, and Anthropic writes on every sheet that it does not choose the tools a publisher exposes nor guarantee how they behave. By default the sheet only exposes reading; that is a floor, not a guarantee that nothing could ever write.
Need help connecting BrightHire to Claude?
A person reads every message.
