6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Query interview transcripts, scorecards, AI notes and coaching reports.
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
The BrightHire MCP server connects interview intelligence to Claude, ChatGPT and any MCP-compatible agent. Eleven read-only tools reach interview transcripts, AI notes, ATS scorecards, interview guides and coaching reports. Sign-in is OAuth. The data is about job candidates and colleagues, which makes this a connector to decide about rather than click through.
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
.all. There is no way to grant narrower access at the OAuth layer — no split between transcripts, scorecards and coaching. Authorisation is read-everything-you-can-see.get_transcripts returns verbatim text. BrightHire describes the payload as large and advises using it only when exact wording matters. Twenty complete interviews can enter a model's context in one call.readOnlyHint or destructiveHint for any tool. The read-only conclusion rests on the vendor's documentation and the scope, not on annotations.get_coaching_report takes no arguments and infers the caller. BrightHire documents no way to request another person's report through MCP.Yes, and this one holds up under checking. BrightHire's own help centre documents exactly the same eleven tools Anthropic's directory lists, every one of them a retrieval verb, and its OAuth descriptors advertise a single scope named mcp:read.all. We found no vendor page, release note or scope describing an MCP action that changes BrightHire data.
Full verbatim interview transcripts. BrightHire describes the tool as pulling complete transcripts plus user-created call notes for up to twenty interviews at a time, and warns that the payload is large. It recommends reaching for it only when exact wording matters, and suggests get_call_ai_notes as the lighter alternative for question-and-answer summaries.
No. BrightHire states that MCP access follows the same permission model as the rest of the product, and that users can only reach data they already have permission to view. Visibility in BrightHire is scoped by hiring team, which the platform pulls from your ATS per position, and by department-level hiring team groups.
BrightHire publishes an opt-in consent link that candidates verify by email before any recording happens. Where the link is detected on an imported calendar invite, the interview shows as awaiting candidate consent and BrightHire will not record until the candidate agrees. Consent can also be collected through the ATS application flow, and candidates may update their decision at any time.
No. BrightHire states on its responsible-AI page that it does not use customer data to train AI models, and its compliance page repeats the commitment as privacy-safe AI. BrightHire also describes Zero Data Retention arrangements with its AI sub-processors. Those statements cover BrightHire's own pipeline, not what your MCP client does with the answers.
No. BrightHire states plainly in its MCP documentation that the connector does not currently provide access to BrightHire Screen product data. Screen is BrightHire's AI interviewer product, so any AI-conducted screening interview sits outside the eleven tools on this page. Everything the connector reaches comes from human interviews captured in BrightHire.
https://app.brighthire.ai/mcp/v1 and both .well-known descriptor families — 2026-08-19 · retrieved 2026-08-19Connect BrightHire once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.